-
Notifications
You must be signed in to change notification settings - Fork 675
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
Schema Diff issue (RM #7424) #5101
Comments
Comment migrated from Redmine: https://redmine.postgresql.org/issues/7424#note-1 Redmine ticket header update:
|
Comment migrated from Redmine: https://redmine.postgresql.org/issues/7424#note-2 Redmine ticket header update:
|
Comment migrated from Redmine: https://redmine.postgresql.org/issues/7424#note-3 Redmine ticket header update:
|
Comment migrated from Redmine: https://redmine.postgresql.org/issues/7424#note-4 Redmine ticket header update:
|
Comment migrated from Redmine: https://redmine.postgresql.org/issues/7424#note-5 Redmine ticket header update:
|
Comment migrated from Redmine: https://redmine.postgresql.org/issues/7424#note-6 Redmine ticket header update:
|
This is resolved in the snapshot build: |
Issue migrated from Redmine: https://redmine.postgresql.org/issues/7424
Originally created by Mark Pare at 2022-05-26 20:23:14 UTC.
Hi, when running a schema diff, because the permissions of a table are displayed in a different order, it is considered a difference when it shouldn't be. Example:
DEV database
GRANT SELECT, INSERT, UPDATE, DELETE ON TABLE . TO
UAT database
GRANT INSERT, SELECT, UPDATE, DELETE ON TABLE . TO
This will generate a difference but it shouldn't the SQL tab displays permissions in a random order in some cases, even if they are always created as SELECT, INSERT, UPDATE, DELETE
Thanks
The text was updated successfully, but these errors were encountered: