'How to avoid id conflicts (uniqueconstraint violation) when using PanacheEntity together with Quarkus "import.sql"
I am using quarkus "import.sql" to add initial data to my application. This data is accessed by classes extending PanacheEntity.
When inserting new data via rest webservice (with id == null) the first inserts run into this error:
FEHLER: doppelter Schlüsselwert verletzt Unique-Constraint »task_pkey«
Detail: Schlüssel »(id)=(1)« existiert bereits.
How can I tell panache to start using Ids starting above the data inserted by import.sql?
Solution 1:[1]
You can use nextval('hibernate_sequence') as in:
INSERT INTO ticket(id, name,seat) VALUES (nextval('hibernate_sequence'), 'Phantom of the Opera','11A')
It will increment the DB sequence when inserting rows.
Source: http://www.mastertheboss.com/soa-cloud/quarkus/managing-data-persistence-with-quarkus/
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|---|
| Solution 1 | JiBz |