Re: Automatic value truncation during update - Mailing list pgsql-general

From Doug Fields
Subject Re: Automatic value truncation during update
Date
Msg-id 5.1.0.14.2.20020603160555.029c3ff8@mail.pexicom.com
Whole thread Raw
In response to Automatic value truncation during update  ("Glen Parker" <glenebob@nwlink.com>)
List pgsql-general
At 02:36 PM 6/3/2002, Glen Parker wrote:
>Postgres 7.1.* and before I believe would silently truncate values to
>fit into their destination fields during insert/update, but 7.2.* gives
>an error when values are too long.  I realize the new behavior is
>probably more correct, but I grew accustom to the old behavior and now
>have queries that rely on that behavior, for better or worse.  I don't
>see a way to get pgsql to use the old behavior.  Am I missing it or is
>it really not there?

Having just gone through this: It's really not there.

Check the archives for the last month or two for all the work-arounds
suggested. The easy way out is to use TEXT fields.

Cheers,

Doug



pgsql-general by date:

Previous
From: Jan Wieck
Date:
Subject: Re: ctid & updates
Next
From: "Johnson, Shaunn"
Date:
Subject: Re: SOLVED: invalid type error