| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruno Wolff III <bruno(at)wolff(dot)to> |
| Cc: | Sean Chittenden <sean(at)chittenden(dot)org>, Shridhar Daithankar <shridhar_daithankar(at)persistent(dot)co(dot)in>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Resetting a sequence's last value... |
| Date: | 2003-04-27 20:54:03 |
| Message-ID: | 7281.1051476843@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Bruno Wolff III <bruno(at)wolff(dot)to> writes:
> Sean Chittenden <sean(at)chittenden(dot)org> wrote:
>> Thoughts? I got a post offlist suggesting writing a C function, but
>> that's pretty dependent on the backend and would have to be recompiled
>> from version to version, something I'm not too wild about. -sc
> What would seem logical to me is using the iscalled parameter to setval
> to determine this. If you call setval('seq', 1, false), I think it
> would be reasonable for the currval('seq') to be undefined until
> nextval('seq') or setval with iscalled=true is called.
I don't believe he wants to do a setval, as the effects of that are
global.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sean Chittenden | 2003-04-27 21:00:53 | Re: Resetting a sequence's last value... |
| Previous Message | Bruno Wolff III | 2003-04-27 20:52:16 | Re: Resetting a sequence's last value... |