You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 30, 2024. It is now read-only.
Currently, there is no fixed order for foreign keys and indexes. When adding or removing objects in the database, the order in which the foreign keys and indexes are returned from the queries foreignKeysRead and indexesRead is not determined. As a consequence, the scripts generated for a table may change, as the indexes and foreign keys might be declared randomly in a different order.
Describe the Feature
Currently, there is no fixed order for foreign keys and indexes. When adding or removing objects in the database, the order in which the foreign keys and indexes are returned from the queries
foreignKeysReadandindexesReadis not determined. As a consequence, the scripts generated for a table may change, as the indexes and foreign keys might be declared randomly in a different order.Suggested Solution
Add an
order byclause in the two queries.