This has been addressed. The main fix was that postgres will not accept UUIDs as Strings in queries via JDBC/JPA. They have to be passed as UUID objects. This is different than SQL Server which casts strings to UUIDs in queries. There may still be issues in some JPA queries that using IN (list of UUIDS) like finding concurrent annotations. I'll need to add these to the integration tests. Leaving this issue open until those are completed.
This has been addressed. The main fix was that postgres will not accept UUIDs as Strings in queries via JDBC/JPA. They have to be passed as UUID objects. This is different than SQL Server which casts strings to UUIDs in queries. There may still be issues in some JPA queries that using
IN (list of UUIDS)like finding concurrent annotations. I'll need to add these to the integration tests. Leaving this issue open until those are completed.