[GH-ISSUE #95] Incorrect compare columns with DEFAULT #64

New issue

Open

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

kerem commented

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

Owner

Originally created by @obbana2 on GitHub (Nov 18, 2019).
Original GitHub issue: https://github.com/DBDiff/DBDiff/issues/95

Hello.
I compare two databases, synchronized through my own script.
I get a lot of "ALTER TABLE...CHANGE ... DEFAULT ..."

I execute SQL on the second database. And with repeated DBDiff, the differences are again visible.
Perhaps the DBDiff algorithm is not entirely correct.
Since I compare myself and see no differences.

Also, DbDiff does not distinguish between renaming tables / columns, but I really want to see it.

Originally created by @obbana2 on GitHub (Nov 18, 2019). Original GitHub issue: https://github.com/DBDiff/DBDiff/issues/95 Hello. I compare two databases, synchronized through my own script. I get a lot of "ALTER TABLE` ... `CHANGE ... DEFAULT ..." I execute SQL on the second database. And with repeated DBDiff, the differences are again visible. Perhaps the DBDiff algorithm is not entirely correct. Since I compare myself and see no differences. Also, DbDiff does not distinguish between renaming tables / columns, but I really want to see it.

kerem commented

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

Author

Owner

@obbana2 commented on GitHub (Nov 18, 2019):

I understand why this happens, in one database DEFAULT is specified as '0', in another as 0 for Integer.
But SQL doesn’t change anything (mysql sees this as the same thing)

@obbana2 commented on GitHub (Nov 18, 2019): I understand why this happens, in one database DEFAULT is specified as '0', in another as 0 for Integer. But SQL doesn’t change anything (mysql sees this as the same thing)