| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Michael Paesold <mpaesold(at)gmx(dot)at> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [PATCHES] Proposed patch for sequence-renaming problems |
| Date: | 2005-09-28 16:58:01 |
| Message-ID: | 200509281658.j8SGw1h16388@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Michael Paesold wrote:
> 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.
Yes, that is the direction I thought we were going.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-09-28 17:25:23 | Re: [PATCHES] Proposed patch for sequence-renaming problems |
| Previous Message | Michael Paesold | 2005-09-28 16:57:00 | Re: [PATCHES] Proposed patch for sequence-renaming problems |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-09-28 17:25:23 | Re: [PATCHES] Proposed patch for sequence-renaming problems |
| Previous Message | Michael Paesold | 2005-09-28 16:57:00 | Re: [PATCHES] Proposed patch for sequence-renaming problems |