| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Andreas Hinz <news3(at)acci(dot)dk>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: ALTER SCHEMA problem |
| Date: | 2003-08-17 05:44:31 |
| Message-ID: | 9363.1061099071@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Can someone comment on this?
This is unfixable as long as nextval() and friends depend on string
parameters to represent table references. There are suggestions in
our archives about how we might move to a more Oracle-like syntax
(ie, table.nextval), which would expose the table reference in a way
that could track renamings. But no one seems to have gotten really
excited about making it happen.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gaetano Mendola | 2003-08-17 08:17:44 | Re: small bug in op + between datetime and integer |
| Previous Message | Dennis Björklund | 2003-08-17 05:30:21 | Re: small bug in op + between datetime and integer |