On 1/31/24 00:51, Rick Hillegas wrote:
On 1/30/24 12:52 PM, jazz wrote:
Hi,
It would be great if this issue could be implemented, I have a use
case for testing. How do I get access to JIRA to update the ticket?
(to include the sql files for testing).
You can request a JIRA account here:
https://selfserve.apache.org/jira-account.html
Thanks, much appreciated. I added two SQL files in the JIRA ticket for
testing.
When importing data into the database (which has foreign keys and
unique constraints) this is useful. Import fails due to a deferred
constraint violation due to the unique index
(SQL0000000140-0fe82566-018d-4f9a-090e-0000170eba31):
ERROR 23516: The transaction was aborted because of a deferred
constraint violation: Foreign key
'FOREIGN_KEY_director_talent_id_talent_talent_id' defined on
"APP"."DIRECTOR" referencing constraint
'SQL0000000140-0fe82566-018d-4f9a-090e-0000170eba31' defined on
"APP"."TALENT", key ''.
Import flow is (in ij):
autocommit off;
run('movies_insert.sql');
commit;
Foreign keys are created with deferred constraints (deferrable
initially deferred).
Any help for a workaround or fix is highly appreciated.
The only workaround which occurs to me is to replace your unique
indexes with unique constraints.
Thanks for the advice. This is what I did. Still no luck. Maybe I am
doing something wrong here. I guess the question is how to insert data
when foreign keys are already created.
Tried to workaround this issue by creating the unique constraints (they
should be primary keys). Does it have to do something with the created
backing indexes which are not deferrable?
Best regards, Bart
-Rick
Best regards,
Bart
