| From: | Neil Conway <neilc(at)samurai(dot)com> |
|---|---|
| To: | Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org> |
| Cc: | pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: lastval() |
| Date: | 2005-06-06 02:18:22 |
| Message-ID: | 42A3B26E.20709@samurai.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
If you're busy, I can clean this up and apply it.
I wonder if it would be better to have lastval() return the last value
returned by nextval() or setval() for the current session, regardless of
any intervening DROP SEQUENCE commands. This would simplify the
implementation (we can just store the int8 value produced by the last
nextval() / setval() rather than a pointer to the sequence object
itself), although it is debatable whether this behavior is more logical
or not. Comments?
-Neil
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-06-06 02:32:17 | Re: refactoring planner data structures |
| Previous Message | Jeff Davis | 2005-06-06 01:35:33 | Re: Google's Summer of Code ... |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Abhijit Menon-Sen | 2005-06-06 03:35:58 | Re: lastval() |
| Previous Message | Qingqing Zhou | 2005-06-06 01:57:33 | Re: Simplify Win32 Signaling code |