Re: [HACKERS] Table inheritance, unique constraints and foreign key problem

Tom Lane [EMAIL PROTECTED] writes: Gregory Stark [EMAIL PROTECTED] writes: I'm a bit puzzled myself why this affects SELECT FOR UPDATE/SHARE but not straight UPDATES and DELETES. In straight UPDATE/DELETE we have enough structure in the query to know how to associate each tuple returned to

[HACKERS] Table inheritance, unique constraints and foreign key problem

Hello, this issue has been requested and its on the TODO-list. Since I really need foreign key constraints on inherited tables, I have two solutions: Adding some hackish RULES/TRIGGERS to my tables or implementing it myself. It think the latter is better. However, I have no experience in

Re: [HACKERS] Table inheritance, unique constraints and foreign key problem

Jacob Rief [EMAIL PROTECTED] writes: this issue has been requested and its on the TODO-list. Since I really need foreign key constraints on inherited tables, I have two solutions: Adding some hackish RULES/TRIGGERS to my tables or implementing it myself. It think the latter is better.

Re: [HACKERS] Table inheritance, unique constraints and foreign key problem

Gregory Stark [EMAIL PROTECTED] writes: I'm a bit puzzled myself why this affects SELECT FOR UPDATE/SHARE but not straight UPDATES and DELETES. In straight UPDATE/DELETE we have enough structure in the query to know how to associate each tuple returned to the executor top level with exactly one