From: | "Denis" <sqllist(at)coralindia(dot)com> |
---|---|
To: | <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: Initially Deffered - FK |
Date: | 2004-01-19 12:11:20 |
Message-ID: | 002c01c3de85$59fbd9c0$0f32a8c0@denisnew |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Hi Stephan,
Thanks for your reply.
Will have to work on its workaround...
Denis
----- Original Message -----
From: "Stephan Szabo" <sszabo(at)megazone(dot)bigpanda(dot)com>
To: <denis(at)coralindia(dot)com>
Cc: <pgsql-sql(at)postgresql(dot)org>
Sent: Monday, January 19, 2004 4:03 PM
Subject: Re: [SQL] Initially Deffered - FK
>
> On Fri, 16 Jan 2004 denis(at)coralindia(dot)com wrote:
>
> > Thanks for your reply.
> >
> > But, you will agree that result should be same JUST BEFORE and JUST
AFTER
> > commit ( assuming no one is working on the database and i am the only
user
> > connected.)
>
> If you use the definition we're using now, then no, the above is not true.
> The row would still exist just before commit because the on delete action
> has not happened. The row would not exist just after commit because the
> on delete action now has. Whether this definition is correct per spec is
> hard to say, but there've been arguments on the subject in the past that
> have generally ended without a firm understanding of the specs intention.
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-01-19 15:07:54 | Re: name of a column returned from a table function |
Previous Message | Iain | 2004-01-19 11:35:25 | name of a column returned from a table function |