Re: Duplicate Key Values - Mailing list pgsql-general

From Adrian Klaver
Subject Re: Duplicate Key Values
Date
Msg-id e781008b-5733-4298-aa57-90580f486eb4@aklaver.com
Whole thread Raw
In response to Re: Duplicate Key Values  (mark bradley <markbradyju@outlook.com>)
Responses Re: Duplicate Key Values
List pgsql-general
On 3/13/25 09:25, mark bradley wrote:
> 
>  > I'm assuming that by 'simple version' you mean no inheritance.
> 
> Inheritance was not specified by me in either case.  By simple, I mean 

Unless someone else is working on this code, it was done by you.

Pretty sure it had to do with from this message:

https://www.postgresql.org/message-id/SJ2PR22MB4328CEB1B47FC1AC4A996CB3BAD12%40SJ2PR22MB4328.namprd22.prod.outlook.com

"Although I did not explicitly use Postgres to declare inheritance, 
logically speaking table dataset and processing _node inherit or are 
subclasses of node because they are subclasses of node in a dataflow 
diagram."

I'm guessing you actually did do the subclassing(inheritance) as it was 
an option presented in the pgAdmin4 CREATE TABLE screen.

Anyway at this point the problem has been identified and a solution devised.



> that I used fewer columns in the test version, like so:
> 
> 
> 
> Where *node_id* is a foreign key in dataset, and *node_type* is not.
> 
> Best regards,
> Mark Brady


-- 
Adrian Klaver
adrian.klaver@aklaver.com




pgsql-general by date:

Previous
From: mark bradley
Date:
Subject: Re: Duplicate Key Values
Next
From: Jehan-Guillaume de Rorthais
Date:
Subject: Re: hide data from admins