From: jdassen@cistron.nl
To: pgsql-sql@postgresql.org
Subject: Re: Truncation of char, varchar, bit, varbit types (fwd)
Date: Wed, 23 May 2001 13:04:36 +0000 (UTC)
Message-ID: <slrn9gndb4.oth.jdassen@odin.cistron-office.nl> (raw)
References: <Pine.LNX.4.30.0105200234090.758-100000@peter.localdomain>
Peter Eisentraut <peter_e@gmx.net> wrote:
> SQL and Postgres differ in behaviour if the value of a char or varchar
> type exceeds the declared length. Postgres cuts off the value, SQL
> requires to raise an error.
>
> In particular, the compliant behaviour is:
> I think this behaviour is desirable over the old one because it makes the
> char and varchar types useful in the first place.
AOL! (Although to ease migration, it would be nice if one could switch
between treating it as an error or a warning for the next few releases).
Ray
--
USDoJ/Judge Jackson: "Microsoft has performed an illegal operation and will
be shut down."
James Turinsky in alt.sysadmin.recovery
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: jdassen@cistron.nl
Subject: Re: Truncation of char, varchar, bit, varbit types (fwd)
In-Reply-To: <slrn9gndb4.oth.jdassen@odin.cistron-office.nl>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox