Using postgresSQL and data sync - already exists issue

Support
#1

While i am trying to run my application after adding a new table, I am getting the following error:

Caused by: liquibase.exception.DatabaseException: ERROR: column "dps_early_settle_app_id" of relation "dps_dps_final_settlement" already exists [Failed SQL: (0) ALTER TABLE public.DPS_DPS_FINAL_SETTLEMENT ADD DPS_EARLY_SETTLE_APP_ID UUID]
	at liquibase.executor.jvm.JdbcExecutor$ExecuteStatementCallback.doInStatement(JdbcExecutor.java:470) ~[liquibase-core-4.25.0.jar:na]
Caused by: liquibase.exception.DatabaseException: ERROR: column "dps_early_settle_app_id" of relation "dps_dps_final_settlement" already exists [Failed SQL: (0) ALTER TABLE public.DPS_DPS_FINAL_SETTLEMENT ADD DPS_EARLY_SETTLE_APP_ID UUID]

	at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:77) ~[liquibase-core-4.25.0.jar:na]
	at liquibase.executor.jvm.JdbcExecutor.execute(JdbcExecutor.java:179) ~[liquibase-core-4.25.0.jar:na]
	at liquibase.database.AbstractJdbcDatabase.execute(AbstractJdbcDatabase.java:1291) ~[liquibase-core-4.25.0.jar:na]
	at liquibase.database.AbstractJdbcDatabase.executeStatements(AbstractJdbcDatabase.java:1273) ~[liquibase-core-4.25.0.jar:na]
	at liquibase.changelog.ChangeSet.execute(ChangeSet.java:755) ~[liquibase-core-4.25.0.jar:na]
	... 58 common frames omitted

I would expect, when running the liquibase, the IDE is checking if the relation is already existing. But if it is already existing, why the liquibase is creating script to create it again? Any suggestions to overcome this issue? This is happening only when I am connecting to my PostgreSQL database, not happens when connected to SQL server.

#4

Hi

If Studio generates invalid changeset - adds column that already exists in DB, you can ignore generated changeset, that causes the problem. Here is a “minus” button in the changelogs preview dialog.

But please note, that when executing Liquibase, Studio does not check if the relation already exists. It just executes existing non-executed changelog that was generated before.
For example if you generate changelog creating column for some database and then execute this changelog for another database that already contains the column, you will get such exception.
It is your responsibility to handle such cases.

#5

Thanks for your explanation. If an option to hard-regenerate the changelog that could be very useful.