From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
---|---|
To: | Brian Hirt <bhirt(at)mobygames(dot)com> |
Cc: | <pgsql-general(at)postgresql(dot)org>, Brian A Hirt <bhirt(at)berkhirt(dot)com> |
Subject: | Re: request for advise |
Date: | 2001-11-05 17:26:44 |
Message-ID: | 20011105092518.D40831-100000@megazone23.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, 5 Nov 2001, Brian Hirt wrote:
> Stephan,
>
> Thanks for the reply. The ON DELETE CASCADE does the opposite of what i
> want. ie, you delete a primary key, and the foriegn key is deleted. In my
> sample, you are deleting the foriegn key, not the primary key.
>
> The function i included in the original message does select into a variable
> and it does delete the list row, but if the list has a next_id and the
> function is called recursively, that's when i get a stmt_execsql error.
I meant that I think this line:
SELECT delete_list_item(del_next_id);
needs to be something like
SELECT INTO foo delete_list_item(del_next_id);
or maybe
EXECUTE ''select delete_list_item(del_next_id)'';
From | Date | Subject | |
---|---|---|---|
Next Message | john | 2001-11-05 17:28:15 | Equate for "describe table" ? |
Previous Message | Jeff Lu | 2001-11-05 17:23:59 | Re: Got error on CREATE TABLE AS (+Bug?) |