| From: | "Michael Paesold" <mpaesold(at)gmx(dot)at> |
|---|---|
| To: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "PostgreSQL-development" <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [PATCHES] Proposed patch for sequence-renaming problems |
| Date: | 2005-09-28 16:57:00 |
| Message-ID: | 020401c5c44d$a5527e60$6f01a8c0@zaphod |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Tom Lane wrote:
> However, we could certainly add the NEXT VALUE FOR syntax if that will
> satisfy your concern about syntax.
Since the NEXT VALUE FOR syntax has a special meaning, would it be better to
support the oracle-style syntax sequence.nextval for now (and use the
::regclass for this)? I am not sure how easy that is considering
schema.sequence.nextval.
Just a thought.
Best Regards,
Michael Paesold
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-09-28 16:58:01 | Re: [PATCHES] Proposed patch for sequence-renaming problems |
| Previous Message | Andrew Dunstan | 2005-09-28 16:47:41 | Re: Proposed patch for sequence-renaming problems |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-09-28 16:58:01 | Re: [PATCHES] Proposed patch for sequence-renaming problems |
| Previous Message | Andrew Dunstan | 2005-09-28 16:47:41 | Re: Proposed patch for sequence-renaming problems |