Re: varchar truncation from 7.1 to 7.2 - Mailing list pgsql-general

From ljb
Subject Re: varchar truncation from 7.1 to 7.2
Date
Msg-id aif8mf$25a0$1@news.hub.org
Whole thread Raw
In response to Re: varchar truncation from 7.1 to 7.2  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: varchar truncation from 7.1 to 7.2  (terry@greatgulfhomes.com)
Re: varchar truncation from 7.1 to 7.2  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
pgman@candle.pha.pa.us wrote:
>
> The SQL standard required the change.

Can you be more specific? Are we talking about SQL-99 or something beyond
SQL-92? Of course PostgreSQL doesn't fully comply with that standard
(whichever standard it is), so what criteria are used to determine what
parts to comply with? Of course I would prefer selective compliance to pick
features rather than restrictions.

Sorry for the attitude here, but this change did cost me some time to fix
applications which broke at 7.2 because of this, and I didn't enjoy that.
I don't have access to a lot of different databases, but two I tried do
silent truncation into CHAR and VARCHAR. I wonder what Oracle does.

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: saving a view with pg_dump
Next
From: Bruce Momjian
Date:
Subject: Re: Questions regarding contrib/tsearch