| From: | "John Hansen" <john(at)geeknet(dot)com(dot)au> |
|---|---|
| To: | "Neil Conway" <neilc(at)samurai(dot)com> |
| Cc: | "Dennis Bjorklund" <db(at)zigo(dot)dhs(dot)org>, <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: lastval() |
| Date: | 2005-05-11 04:22:17 |
| Message-ID: | 5066E5A966339E42AA04BA10BA706AE50A931E@rodrick.geeknet.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Neil Conway wrote:
> Sent: Wednesday, May 11, 2005 2:13 PM
> To: John Hansen
> Cc: Dennis Bjorklund; pgsql-patches(at)postgresql(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-05-11 05:23:06 | Re: refactor index build |
| Previous Message | Neil Conway | 2005-05-11 04:12:37 | Re: lastval() |