| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Zoltan Boszormenyi <zboszor(at)dunaweb(dot)hu> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: Three weeks left until feature freeze |
| Date: | 2006-07-14 20:41:25 |
| Message-ID: | 4842.1152909685@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Zoltan Boszormenyi <zboszor(at)dunaweb(dot)hu> writes:
> I am working on adding a new column contraint,
> namely the GENERATED [ALWAYS | BY DEFAULT ] AS
> [ IDENTITY ( sequence_options ) | ( expression )]
Doesn't this still have the issue that we're taking over spec-defined
syntax to represent behavior that does not quite match the spec-defined
semantics? It's not clear to me how closely tied this syntax is to
NEXT VALUE FOR, but if it's got any of the latter's action-at-a-distance
subtleties then I think we ought to leave well enough alone till we have
a solution for that.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-07-14 20:50:09 | Re: src/tools/pginclude considered harmful (was Re: [PATCHES] |
| Previous Message | Martijn van Oosterhout | 2006-07-14 20:38:56 | Re: src/tools/pginclude considered harmful (was Re: [PATCHES] |