feat(dump): add includeGeneratedColumns config option and docs" -m "Add CLI flag and config/docs support for including generated/default columns in dumps.

- Add `--include-generated-columns` flag and pass through to dump
- Document and example configuration
- Adjust table column filtering to include generated columns when enabled
- Remove temporary changelog file

Signed-off-by: chenen <itfunx@hotmail.com>

Author: n2em

CHANGES_GENERATED_COLUMNS.md

@@ -73,6 +73,7 @@ The following are the environment variables, CLI flags and configuration file op
 | names of databases to exclude from the dump | B | `exclude` | `DB_DUMP_EXCLUDE` | `dump.exclude` |  |
 | do not include `USE <database>;` statement in the dump | B | `no-database-name` | `DB_DUMP_NO_DATABASE_NAME` | `dump.noDatabaseName` | `false` |
 | Replace single long INSERT statement per table with one INSERT statement per line | B | `skip-extended-insert` | `DB_DUMP_SKIP_EXTENDED_INSERT` | `dump.skipExtendedInsert` | `false` |
+| Include generated columns in dump (not virtual columns) | B | `include-generated-columns` | `DB_DUMP_INCLUDE_GENERATED_COLUMNS` | `dump.includeGeneratedColumns` | `false` |
 | restore to a specific database | R | `restore --database` | `RESTORE_DATABASE` | `restore.database` |  |
 | how often to do a dump or prune, in minutes | BP | `dump --frequency` | `DB_DUMP_FREQUENCY` | `dump.schedule.frequency` | `1440` (in minutes), i.e. once per day |
 | what time to do the first dump or prune | BP | `dump --begin` | `DB_DUMP_BEGIN` | `dump.schedule.begin` | `0`, i.e. immediately |
@@ -139,8 +140,29 @@ for details of each.
     * `once`: boolean, run once and exit
   * `compression`: string, the compression to use
   * `compact`: boolean, compact the dump
+  * `includeGeneratedColumns`: boolean, include columns marked as `GENERATED` in the dump (does not include `VIRTUAL` columns)
   * `triggersAndFunctions`: boolean, include triggers and functions and procedures in the dump
   * `maxAllowedPacket`: int, max packet size
+
+When `includeGeneratedColumns` is enabled, columns that are defined with a `GENERATED` attribute or have a default expression
+will be included in the row data that is emitted as `INSERT` statements in the dump. Note that `VIRTUAL` columns remain excluded
+because they are computed and cannot be restored from dumped values.
+
+Usage example:
+
+Suppose a table has a column defined as:
+
+```sql
+`create_time` TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP
+```
+
+When `includeGeneratedColumns` is turned on, rows for this table will contain the `create_time` value in the `INSERT` statements, e.g.:
+
+```sql
+INSERT INTO `mytable` (`id`, `name`, `create_time`) VALUES (1, 'alice', '2025-11-14 09:30:00');
+```
+
+This makes the dump include the generated/default timestamp values instead of relying on the default expressions when restoring.
   * `filenamePattern`: string, the filename pattern
   * `scripts`:
     * `preBackup`: string, path to directory with pre-backup scripts

docs/configuration.md

@@ -21,6 +21,11 @@ spec:
     safechars: true # defaults to false
     noDatabaseName: false # remove the `USE <database>` statement from backup files, defaults to false
     skipExtendedInsert: false # replace single long INSERT statement per table with one INSERT statement per line, defaults to false
+    includeGeneratedColumns: false # include columns marked as GENERATED; VIRTUAL columns remain excluded. Defaults to false
+    # When enabled, columns with defaults or generated values (for example
+    # `create_time TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP`) will be
+    # dumped as part of the INSERT rows. Example:
+    # INSERT INTO `mytable` (`id`, `name`, `create_time`) VALUES (1, 'alice', '2025-11-14 09:30:00');
     # schedule to dump, can use one of: cron, frequency, once. If frequency is set, begin will be checked
     schedule:
       once: true # run only once and exit; ignores all other scheduling. Defaults to false