> On Mar 29, 2023, at 12:11, Sebastien Flaesch <sebastien.flae...@4js.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).
- Re: Using CTID system column as a "temporary"... Kirk Wolak
- Re: Using CTID system column as a "temporary&... Laurenz Albe
- Re: Using CTID system column as a "tempor... Sebastien Flaesch
- Re: Using CTID system column as a "te... Laurenz Albe
- Re: Using CTID system column as a &quo... Sebastien Flaesch
- Re: Using CTID system column as a "temporary&... Sebastien Flaesch
- Re: Using CTID system column as a "tempor... Adrian Klaver
- Re: Using CTID system column as a "te... Peter J. Holzer
- Re: Using CTID system column as a &quo... Adrian Klaver
- Re: Using CTID system column as a "te... Sebastien Flaesch
- Re: Using CTID system column as a &quo... Christophe Pettus
- Re: Using CTID system column as a &quo... Adrian Klaver
- Re: Using CTID system column as a &quo... Dominique Devienne
- Re: Using CTID system column as a &quo... Francisco Olarte
- Re: Using CTID system column as a &quo... Dominique Devienne
- Re: Using CTID system column as a &quo... Laurenz Albe
- Re: Using CTID system column as a &quo... Alban Hertroys
- Re: Using CTID system column as a &quo... Sebastien Flaesch
- Re: Using CTID system column as a &quo... Francisco Olarte