I agree, I had the same last minute scramble to make apps work with the no
longer silent truncation.
Is it possible to have a flag in the config file to make the silent
truncation enabled?
Or how about someone writing a sample trigger that would chop fields before
the insert/update so as to truncate the data before the actual insert aborts
it?
Terry Fielder
Network Engineer
Great Gulf Homes / Ashton Woods Homes
terry@greatgulfhomes.com
> -----Original Message-----
> From: pgsql-general-owner@postgresql.org
> [mailto:pgsql-general-owner@postgresql.org]On Behalf Of ljb
> Sent: Friday, August 02, 2002 8:39 PM
> To: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] varchar truncation from 7.1 to 7.2
>
>
> 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.
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>