Tom Lane writes:
> >> Well, beside the referential constraint issue ( that can be solved by
> >> hand ), the most frustrating is that queries like
> >> DELETE FROM table* where key = some_value
> >> Fails ( parser error ). ( UPDATE either )
>
> Not as of 7.1.
>
> re
>> Well, beside the referential constraint issue ( that can be solved by
>> hand ), the most frustrating is that queries like
>> DELETE FROM table* where key = some_value
>> Fails ( parser error ). ( UPDATE either )
Not as of 7.1.
regards, tom lane
-
>
> Hi, i've posted various problems regarding inheritance in postgres,
> Never see a reply :(
>
> Well, beside the referential constraint issue ( that can be solved by
> hand ), the most frustrating is that queries like
>
> DELETE FROM table* where key = some_value
>
> Fails ( parser error )
Hi, i've posted various problems regarding inheritance in postgres,
Never see a reply :(
Well, beside the referential constraint issue ( that can be solved by
hand ), the most frustrating is that queries like
DELETE FROM table* where key = some_value
Fails ( parser error ). ( UPDATE either )
Inheritance is one of the most useful and 'marketed' features in PostgreSQL.
However its behavior is not what one expected it to be. Inherited tables do
not inherit some constraints, including primary and foreing keys.
This information is very important, specially for newbies, who can get very
f
