Re: lastval() - Mailing list pgsql-patches

From John Hansen
Subject Re: lastval()
Date
Msg-id 5066E5A966339E42AA04BA10BA706AE50A931E@rodrick.geeknet.com.au
Whole thread Raw
In response to lastval()  (Dennis Bjorklund <db@zigo.dhs.org>)
List pgsql-patches
Neil Conway wrote:
> Sent: Wednesday, May 11, 2005 2:13 PM
> To: John Hansen
> Cc: Dennis Bjorklund; pgsql-patches@postgresql.org
> Subject: Re: [PATCHES] lastval()
>
> John Hansen wrote:
> > Even more so if the 'currval(void) called before nextval(seq_name)'
> > error message could be supressed by a GUC variable and return 0
> > instead.
>
> I don't think that's a good idea at all. It seems
> unnecessary, it complicates the definition of the operation,
> and worse, "0" is a valid return value for currval(), so it
> would also be ambiguous.

K, No mysql-ism for postgresql then :)
(pardon my french)

> -Neil
>
>

... John


pgsql-patches by date:

Previous
From: Neil Conway
Date:
Subject: Re: lastval()
Next
From: Tom Lane
Date:
Subject: Re: refactor index build