mirror of
https://github.com/DBDiff/DBDiff.git
synced 2026-04-25 13:25:49 +03:00
[PR #54] [CLOSED] Foreign key change tries to drop empty named constraint #246
Labels
No labels
bug
enhancement
good first issue
help wanted
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/DBDiff#246
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/DBDiff/DBDiff/pull/54
Author: @berlinger-peussen
Created: 6/14/2017
Status: ❌ Closed
Base:
master← Head:bugfix/change_constraint_renders_empty_name📝 Commits (1)
67ab3d1When a foreign key constraint has to be changed, the old one is dropped, but without a name📊 Changes
1 file changed (+2 additions, -2 deletions)
View changed files
📝
src/SQLGen/DiffToSQL/AlterTableChangeConstraintSQL.php(+2 -2)📄 Description
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;🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.