Done
Details
Assignee
Julian LadischJulian LadischReporter
Julian LadischJulian LadischTester Assignee
Adam DickmeissAdam DickmeissLabels
Priority
P3Story Points
3Sprint
NoneDevelopment Team
Core: PlatformFix versions
TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Julian Ladisch
Julian LadischReporter
Julian Ladisch
Julian LadischTester Assignee
Adam Dickmeiss
Adam DickmeissLabels
Priority
Story Points
3
Sprint
None
Development Team
Core: Platform
Fix versions
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created June 20, 2019 at 9:08 AM
Updated June 26, 2019 at 1:39 PM
Resolved June 26, 2019 at 1:39 PM
In https://folio-org.atlassian.net/browse/RMB-346#icft=RMB-346 and https://folio-org.atlassian.net/browse/RMB-347#icft=RMB-347 we removed the database trigger that inserts a random UUID into the id field if the id field is empty. The client, not the database server, needs to create the UUID to prevent different database nodes (pg-pool replication environment) from having different UUIDs for the same record.
PgUtil.post already creates the random UUID.
For PostgresClient.save this feature needs to be added.
This is a new feature, not a regression, because "populateJsonWithId: true" was required in schema.json to enable the database trigger that creates the UUID.