New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature]: Fix ordering of schema export #3611
Comments
This has sort of been raised before. If table A has foreign keys to table B, then when the SQL is run it fails as table B doesn't exist yet, so your ordering request makes sense. However, for some users, understanding and processing this could be quite a task. Programmatically it could be even worse. |
If the issue has been raised before it should have been addressed. Look at this diff and quickly tell me what has changed. Then justify the rest of the changes:
|
Addressing an issue requires code. Without code to address the issue, how do you propose the issue should be addressed? I have tried to wave my magic wand, but unfortunately it appears it's out of fairy dust. Sorry. Proper answer...
We await a PR to address the issue. This is an open-source project, so anyone can contribute. |
Describe the new feature
Tables, Foreign keys, etc., but obviously not columns, should be sorted on export.
When exporting the DB schema as an SQL file the order of the exported items varies from one export to the next if something has been changed in the DB. This makes it hard to detect meaningful changes amongst the noise. For example foreign keys can be in random order, even if their table has not been changed.
Does this feature exist in another product or project? Please provide a link
HediSQL sorts exported tables, views, etc. But doesn't work properly with SQLite.
Do you have a screenshot? Please add screenshots to help explain your idea.
No response
The text was updated successfully, but these errors were encountered: