| From: | Rod Taylor <rbt(at)rbt(dot)ca> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCHES] ALTER SEQUENCE |
| Date: | 2003-03-07 16:35:23 |
| Message-ID: | 1047054923.28251.51.camel@jester |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers pgsql-patches |
On Fri, 2003-03-07 at 11:27, Bruce Momjian wrote:
> Does it make sense to avoid sequence name collisions if applications
> have to refer to sequence names directly? I mean, I can imagine a case
Not at all. Hence the thought that we might create syntax to allow
applications to refer to the table / column that the sequence (SERIAL)
is on. This would hide the internal representation of a SERIAL...
--
Rod Taylor <rbt(at)rbt(dot)ca>
PGP Key: http://www.rbt.ca/rbtpub.asc
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2003-03-07 16:40:07 | Re: PgHosts |
| Previous Message | Jean-Christian Imbeault | 2003-03-07 16:33:10 | Unexpected parse behaviour for date to timestamp conversion |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vince Vielhaber | 2003-03-07 17:03:00 | DBTools' DBManager Information Leak Vulnerability (fwd) |
| Previous Message | Bruce Momjian | 2003-03-07 16:27:13 | Re: [PATCHES] ALTER SEQUENCE |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2003-03-07 16:35:51 | Re: new format for describe (repost #2) |
| Previous Message | Bruce Momjian | 2003-03-07 16:34:15 | Re: new format for describe (repost #2) |