Compare structure tool for all schemas
Answered
Hi,
I would like to compare structure of two postgresql databases (PROD and DEV) with multiple schemas.
It is possible to compare all schemas at the same time? I'm almost sure that some time ago that was possible. I just selected two database objects and click compare. Now that only works for single schema (have to click one schema in DEV and PROD db).
Thanks for advice
Please sign in to leave a comment.
Does it work if you select two databases in Database Explorer and perform Ctrl + D shortcut? Please see https://www.jetbrains.com/help/datagrip/differences-viewer-for-database-objects.html for more information
No, it doesn't work.
When I click DB names and click CMD+D then diff tool opens however don't show any differences.
When I click specific same schemas on both DB then diff tool show differences.
I'm not sure if this is connected with some Diff Tool config or DB config but I'm sure that some time ago that feature used to work.
Hi rk ,
We never had more than two database objects for comparison in show diff. This is also mentioned in our guide as per the link provided above.
If you don't see any changes when comparing two databases, please activate database.legacy.schema.diff in Help - Find Action and type Registry. Once activated, save the changes and compare two databases.
Let me know if this works for you.
Hi Aleksandr Molchanov
I don't won't compare more that two databases however I want to compare all schemas at the same time.
I think that was possible when I clicked database name and CTRL+D. Now it's working only if I click specific schema and CTRL+D.
When I enabled database.legacy.schema.diff then CTRL+D open some other diff tool however I can see all differences across all schemas.
I'm not sure if that legacy tool can generate SQL script for syncing diffs.
Correct, that's the previous version. Unfortunately, it doesn't generate the query distinguishing the differences between two db objects. As we are currently working on optimizing the new diff tool, we'd recommend using it alternatively while we improve the current one.