Have model reflect changes to db

[sggreener]

For a variety of reasons I needed to make direct changes to my database data model independently of pgModeler.

Mainly:

1. Changed some attributes within existing tables in my model
2. Added new attributes to existing tables in my model
3. Programmatically added a lot of new indexes
4. Programmatically added a lot of missing foreign keys
5. Programmatically changed the names of all existing foreign key relationships in the database by dropping all foreign keys in the database and recreating them.

I don't want to create a new model as I have put a lot of effort into laying out the previous database tables.

I want to know which of the above can be discovered by pgModeler and merged with existing objects.

For 5 and 6 can I select and delete all foreign keys in my existing model then just import the new foreign keys and have pgModeler attach them to existing object?

regards
Simon

[sggreener]

Yeah, ignore this discussion item. By experimentation the import does a good job of synchronising the model with the changes to the database.

[sggreener]

I added an attribute is_default to 83 lookup tables in my database.
I tried to Import the database back into my model to pick up the changes and it failed to do so.
How can I make my model pick up the changes?
@rkhaotix ?
Simon

[rkhaotix]

@sggreener currently pgModeler doesn't support database -> model synchronization, only model -> database.

About the issue you're having, unfortunately, the "Import to working model" option in Import is failing to create columns in existing tables, I'm aware of that problem.

Maybe a workaround for your case can be this:
https://pgmodeler.io/support/docs/612-objects-metadata-handling?v=1.1.0

[sggreener]

Yes, that workaround fixed my model. (Though more checking is needed.)