Re: Initially Deffered - FK - Mailing list pgsql-sql

From Denis
Subject Re: Initially Deffered - FK
Date
Msg-id 002c01c3de85$59fbd9c0$0f32a8c0@denisnew
Whole thread Raw
In response to Initially Deffered - FK  ("Denis" <sqllist@coralindia.com>)
List pgsql-sql
Hi Stephan,

Thanks for your reply.

Will have to work on its workaround...

Denis


----- Original Message -----
From: "Stephan Szabo" <sszabo@megazone.bigpanda.com>
To: <denis@coralindia.com>
Cc: <pgsql-sql@postgresql.org>
Sent: Monday, January 19, 2004 4:03 PM
Subject: Re: [SQL] Initially Deffered - FK


>
> On Fri, 16 Jan 2004 denis@coralindia.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



pgsql-sql by date:

Previous
From: "Iain"
Date:
Subject: name of a column returned from a table function
Next
From: Tom Lane
Date:
Subject: Re: name of a column returned from a table function