mirror of
https://github.com/DBDiff/DBDiff.git
synced 2026-04-25 13:25:49 +03:00
[GH-ISSUE #100] DBDiff doesn't write migration.sql if no differences was found in database structure #67
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#67
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?
Originally created by @llagerlof on GitHub (Aug 26, 2020).
Original GitHub issue: https://github.com/DBDiff/DBDiff/issues/100
Environment:
Windows 10 WSL 1 (Ubuntu)
How to reproduce:
php dbdiff server1.database1:server2.database2If
migration.sqlexists, it doesn't change. Ifmigration.sqldoesn't exists, it isn't created.This is bad because can lead to wrong conclusions. e.g.: What if I ran
dbdiffinto databases with differences and apply the update. When I rundbdiffagainst the same databases it will look like I didn't applied the update because the previousmigration.sqlis still there..dbdiffcontents:custom-db-migrate.tmplcontents:Suggestion to solve this issue:
Write the
migration.sqleven if there isn't any differences.