Re: A few questions about ltree

From: Alban Hertroys <alban(at)magproductions(dot)nl>
To: Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>
Cc: Teodor Sigaev <teodor(at)sigaev(dot)ru>, Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: A few questions about ltree
Date: 2006-04-21 16:12:42
Message-ID: 4449047A.9080106@magproductions.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Stephan Szabo wrote:
>>SQL> CREATE TABLE ltree_test (path ltree PRIMARY KEY REFERENCES
>>ltree_test(path));
>>NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index
>>"ltree_test_pkey" for table "ltree_test"
>>CREATE TABLE
>>SQL> INSERT INTO ltree_test VALUES ('a'::ltree);
>>INSERT 84117368 1
>>SQL> INSERT INTO ltree_test VALUES ('a.b'::ltree);
>>INSERT 84117369 1
>>SQL> INSERT INTO ltree_test VALUES ('a.b.c'::ltree);
>>INSERT 84117370 1
>>SQL> DELETE FROM ltree_test WHERE path = 'a.b'::ltree;
>>DELETE 1
>
> I'm not sure why you expect this to error. Any row that would reference
> a.b would be removed by the delete AFAICS.

Nope, there's no ON DELETE CASCADE on the FK, and RESTRICT is the
default (thankfully).

But the FK constraint apparently doesn't get triggered by the delete, so
neither case matters much here.

--
Alban Hertroys
alban(at)magproductions(dot)nl

magproductions b.v.

T: ++31(0)534346874
F: ++31(0)534346876
M:
I: www.magproductions.nl
A: Postbus 416
7500 AK Enschede

// Integrate Your World //

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Teodor Sigaev 2006-04-21 16:25:08 Re: A few questions about ltree
Previous Message Stephan Szabo 2006-04-21 16:04:21 Re: A few questions about ltree