[GH-ISSUE #13] How to compare database dump FILES? #4

New issue

Closed

opened 2026-02-25 21:33:00 +03:00 by kerem · 1 comment

kerem commented

2026-02-25 21:33:00 +03:00

Owner

Originally created by @COLABORATI on GitHub (Jun 15, 2016).
Original GitHub issue: https://github.com/DBDiff/DBDiff/issues/13

From what I undertstand reading the description this interesting tool can compare database schemas ony in live databases. I would like to compare schemas from database dumps that were generated with mysqldump - is this possible?

Thanks for your attention!

Originally created by @COLABORATI on GitHub (Jun 15, 2016). Original GitHub issue: https://github.com/DBDiff/DBDiff/issues/13 From what I undertstand reading the description this interesting tool can compare database schemas ony in live databases. I would like to compare schemas from database dumps that were generated with `mysqldump` - is this possible? Thanks for your attention!

kerem closed this issue

2026-02-25 21:33:00 +03:00

kerem commented

2026-02-25 21:33:01 +03:00

Author

Owner

@jasdeepkhalsa commented on GitHub (Jun 16, 2016):

Hi @COLABORATI.

We had a similar question asked here: https://github.com/DBDiff/DBDiff/issues/3

Currently the only solution is to you get your SQL file added back into a temporary MySQL database on your laptop / machine in order to produce your migrations. You can always destroy that temporary database later :) The reason being that we can only connect to a MySQL database (at the moment) to produce migrations, and if we put in work to add this feature, behind the scenes we'd have to use a temporary database ourselves to do the migrations anyway since a file does not contain any structured data we can use to identity schema / data.

@jasdeepkhalsa commented on GitHub (Jun 16, 2016): Hi @COLABORATI. We had a similar question asked here: https://github.com/DBDiff/DBDiff/issues/3 Currently the only solution is to you get your SQL file added back into a temporary MySQL database on your laptop / machine in order to produce your migrations. You can always destroy that temporary database later :) The reason being that we can only connect to a MySQL database (at the moment) to produce migrations, and if we put in work to add this feature, behind the scenes we'd have to use a temporary database ourselves to do the migrations anyway since a file does not contain any structured data we can use to identity schema / data.

kerem referenced this issue

2026-02-25 21:33:03 +03:00

[GH-ISSUE #32] Fail to find table #20

kerem referenced this issue

2026-02-25 21:33:10 +03:00

[GH-ISSUE #89] Can't Connect to target database #62

kerem referenced this issue

2026-02-25 21:33:18 +03:00

[PR #4] On unexpected error log exception message #100

kerem referenced this issue

2026-03-07 20:41:41 +03:00

[GH-ISSUE #32] Fail to find table #158