[PR #54] Foreign key change tries to drop empty named constraint #114

New issue

Closed

opened 2026-02-25 21:33:21 +03:00 by kerem · 0 comments

kerem commented

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

Owner

Original Pull Request: https://github.com/DBDiff/DBDiff/pull/54

State: closed
Merged: No

When DBDiff finds it needs to change a foreign key, it will create two statements, a drop and a add. The add is fine, but the drop is created without a name.

It will show up as ALTER TABLE `sometable` DROP CONSTRAINT ``;. This patch should fix the problem;

**Original Pull Request:** https://github.com/DBDiff/DBDiff/pull/54 **State:** closed **Merged:** No --- When DBDiff finds it needs to change a foreign key, it will create two statements, a drop and a add. The add is fine, but the drop is created without a name. It will show up as ```ALTER TABLE `sometable` DROP CONSTRAINT ``;```. This patch should fix the problem;

kerem

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

closed this issue
added the
pull-request
label

kerem changed title from ~~[PR #54] [CLOSED] Foreign key change tries to drop empty named constraint~~ to [PR #54] Foreign key change tries to drop empty named constraint

2026-02-27 12:37:59 +03:00

kerem referenced this issue

2026-03-07 20:42:11 +03:00

[GH-ISSUE #114] Column VARCHAR with pipe "|" don't appear in migration file. #219