2011/6/2 Robert Haas robertmh...@gmail.com:
It's a fairly unusual case to have two inheritance children one of
which has a foreign key referencing the other, and to then try to
BTW, when the both tables refer to tr_test1 directly the same thing
happens on truncating:
create table
The following bug has been logged online:
Bug reference: 6048
Logged by: Artiom Makarov
Email address: artiom.maka...@gmail.com
PostgreSQL version: 9.04
Operating system: 2.6.32-30-server #59-Ubuntu SMP Tue Mar 1 22:46:09 UTC
2011 x86_64 GNU/Linux
Description:
On Jun 2, 2011, at 2:23 PM, Artiom Makarov wrote:
The following bug has been logged online:
Bug reference: 6048
Logged by: Artiom Makarov
Email address: artiom.maka...@gmail.com
PostgreSQL version: 9.04
Operating system: 2.6.32-30-server #59-Ubuntu SMP Tue Mar 1
2011/6/2 Alexey Klyukin al...@commandprompt.com:
What would you expect to happen for TRUNCATE .. CASCADE?
One thing I find potentially surprising is that TRUNCATE CASCADE doesn't
follow the semantics of 'ON DELETE' clause for the foreign key, i.e. it would
truncate the dependent table even
On Jun 2, 2011, at 6:21 PM, Artiom Makarov wrote:
2011/6/2 Alexey Klyukin al...@commandprompt.com:
What would you expect to happen for TRUNCATE .. CASCADE?
One thing I find potentially surprising is that TRUNCATE CASCADE doesn't
follow the semantics of 'ON DELETE' clause for the foreign
On Thu, Jun 2, 2011 at 11:21 AM, Artiom Makarov
artiom.maka...@gmail.com wrote:
2011/6/2 Alexey Klyukin al...@commandprompt.com:
What would you expect to happen for TRUNCATE .. CASCADE?
One thing I find potentially surprising is that TRUNCATE CASCADE doesn't
follow the semantics of 'ON
