Re: lastval()
This is a discussion on Re: lastval() within the Pgsql Patches forums, part of the PostgreSQL category; --> Neil Conway wrote: > Sent: Wednesday, May 11, 2005 2:13 PM > To: John Hansen > Cc: Dennis Bjorklund; ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
04-18-2008, 12:19 AM
| ||||
| ||||
 Re: lastval() 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 ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster      |
Linear Mode
