| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | Sebastien Flaesch <sebastien(dot)flaesch(at)4js(dot)com> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Kirk Wolak <wolakk(at)gmail(dot)com>, Geoff Winkless <pgsqladmin(at)geoff(dot)dj>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Using CTID system column as a "temporary" primary key |
| Date: | 2023-03-29 19:18:30 |
| Message-ID: | E7B36E22-D882-44E6-8995-3B50908333F6@thebuild.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On Mar 29, 2023, at 12:11, Sebastien Flaesch <sebastien(dot)flaesch(at)4js(dot)com> wrote:
> But to make PostgreSQL more Informix-compatible, zero should have been considered as well.
There is an infinite family of strange features that various databases have (DUAL from Oracle, anyone?); PostgreSQL will rapidly become unusable if it tried to adopt them all. This one in particular seems particularly hacky and misguided (as well as non-standard-compliant).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2023-03-29 19:23:32 | Re: Using CTID system column as a "temporary" primary key |
| Previous Message | Adrian Klaver | 2023-03-29 19:15:09 | Re: Using CTID system column as a "temporary" primary key |