Date: Thu, 7 Jul 2005 21:28:39 -0600
From: Michael Fuhr <mike@fuhr.org>
To: PFC <lists@boutiquenumerique.com>
Cc: lmeadors@apache.org, pgsql-sql@postgresql.org
Subject: Re: getting back autonumber just inserted
Message-ID: <20050708032839.GA53708@winnie.fuhr.org>
References: <42CD6B58.6060508@techevolution.be>
	<20050707201433.94901.qmail@web41013.mail.yahoo.com>
	<20050707203715.GA26528@winnie.fuhr.org>
	<a10a823c05070713473add03d7@mail.gmail.com>
	<20050707205725.GA28200@winnie.fuhr.org>
	<op.stkdygr8th1vuj@localhost>
	<20050707224452.GA50696@winnie.fuhr.org>
	<op.stkh4cegth1vuj@localhost>
	<20050708014950.GA3339@winnie.fuhr.org>
	<op.stkqsbzith1vuj@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <op.stkqsbzith1vuj@localhost>

On Fri, Jul 08, 2005 at 05:03:37AM +0200, PFC wrote:
> >On Fri, Jul 08, 2005 at 01:56:26AM +0200, PFC wrote:
> >>Hm, interesting, you mean the return value of lastval() also depends
> >>if  you set your constraints  to deferred or immediate ?
> >
> >My mind's ablank trying to contrive a situation where that would
> >matter.  Can you provide an example?
> 
> It's rather perverse and farfetched, but what would stop one from 
> putting  some insert statements in a function that happens to be called 
> somewhere  inside of a check constraint... although one could agree that 
> it's a bit  shooting oneself in the foot...

PostgreSQL doesn't support deferral of check constraints, only
foreign key constraints.  But yeah, if you could do that then
presumably lastval() might return a different sequence's value
depending on whether the constraints were deferred or immediate.

-- 
Michael Fuhr
http://www.fuhr.org/~mfuhr/