[GH-ISSUE #33] option to split output into multiple dumps, one for each table #163

Closed
opened 2026-03-07 20:41:43 +03:00 by kerem · 1 comment
Owner

Originally created by @vesper8 on GitHub (Dec 28, 2016).
Original GitHub issue: https://github.com/DBDiff/DBDiff/issues/33

I would find it helpful and useful if the sql dump output could be automatically separated into multiple dumps, one for each table.

i know you're trying to keep the cli lean but this would just be an additional optional value

Originally created by @vesper8 on GitHub (Dec 28, 2016). Original GitHub issue: https://github.com/DBDiff/DBDiff/issues/33 I would find it helpful and useful if the sql dump output could be automatically separated into multiple dumps, one for each table. i know you're trying to keep the cli lean but this would just be an additional optional value
kerem 2026-03-07 20:41:43 +03:00
Author
Owner

@jasdeepkhalsa commented on GitHub (Nov 24, 2017):

This may be something we consider as a feature in the future

In the meantime though, the way to achieve this would be to run multiple DBDiff commands against each table, along with specifying a specific output name for each table e.g.

./dbdiff server1.development.table1:server2.production.table1 --output=./output-dir/table-1.sql
./dbdiff server1.development.table2:server2.production.table2 --output=./output-dir/table-2.sql
<!-- gh-comment-id:346870693 --> @jasdeepkhalsa commented on GitHub (Nov 24, 2017): This may be something we consider as a feature in the future In the meantime though, the way to achieve this would be to run multiple DBDiff commands against each table, along with specifying a specific output name for each table e.g. ```bash ./dbdiff server1.development.table1:server2.production.table1 --output=./output-dir/table-1.sql ./dbdiff server1.development.table2:server2.production.table2 --output=./output-dir/table-2.sql ```
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/DBDiff#163
No description provided.