It turns out the issue was related to JSON and the UUID. I had a single row of
data being inserted from the "source" side, but there were two rows contained
in JSON within one of the fields. My extract pattern denormalized the JSON
content and caused two records to be insert... with the same UUI
On 2021-10-14 03:02:08 +, Eric Tobias wrote:
> I have a table with a UUID as the primary key field. I am using a procedure to
> insert a parent and child record and using a UUID generated by an external
> system (webhook). The UUID insert is generating a “duplicate key” error on
> insert, but w
I have a table with a UUID as the primary key field. I am using a procedure to
insert a parent and child record and using a UUID generated by an external
system (webhook). The UUID insert is generating a "duplicate key" error on
insert, but when I SELECT the uuid, nothing is returned. I've even
