PLAT-82: Add PostgreSQL support to reference application modules

[wikumChamith]

Fixes PostgreSQL compatibility issues in the liquibase.xml

https://openmrs.atlassian.net/browse/PLAT-82

[CLAassistant]

All committers have signed the CLA.

[wikumChamith]

@angshu can you take a look at this?

[rahu1ramesh]

Thank you for the update! I would recommend reconsidering the use of ANY in this changeset. I checked the checksum of the below changeSet, and got entirely different ones (screenshot attached below).

My understanding is that if raw SQL (...) is used instead of structured XML (), Liquibase does not normalize it across different databases and the database might generate different checksums. I recommend avoiding ANY as this will prevent detection of future accidental changes to the changeset.

Let me know your thoughts, and thanks for your effort on this!

cc: @angshu, @mohan-13

[wikumChamith]

I couldn't find any use of ANY. Could you point out where it's being used? Thanks!

[mherman22]

Hey @wikumChamith , so with these changes the Initializer complains with the following error: Caused by: org.postgresql.util.PSQLException: ERROR: relation "speciality_id_seq" does not exist

The error i believe occurred because the Hibernate mapping explicitly referenced a sequence named speciality_id_seq, but PostgreSQL did not have such a sequence. In PostgreSQL, when a column is defined using autoIncrement="true" in Liquibase, it translates to GENERATED BY DEFAULT AS IDENTITY, which creates a sequence with an auto-generated name (e.g., appointment_speciality_speciality_id_seq). Since no sequence named speciality_id_seq existed, PostgreSQL threw a relation "speciality_id_seq" does not exist error during entity persistence.

The fix was to remove the explicit sequence name from the Hibernate mapping and rely on the native ID generation strategy by changing:

<generator class="native">
    <param name="sequence">speciality_id_seq</param>
</generator>

to simply:

<generator class="native"/>

Also did the above step for

openmrs-module-appointments/api/src/main/resources/AppointmentServiceDefinition.hbm.xml

Lines 8 to 10 in e689087

	<generator class="native">
	<param name="sequence">appointment_service_id_seq</param>
	</generator>

in order to fix Caused by: org.postgresql.util.PSQLException: ERROR: relation "appointment_service_id_seq" does not exist

Here are the logs just incase you need to look them over: https://paste.ubuntu.com/p/RYWwsD3ktS/

cc: @dkayiwa

[angshu]

Just following up on this. @wikumChamith @mherman22 any resolution to this?