Re: Truncation of char, varchar, bit, varbit types (fwd)

From: jdassen(at)cistron(dot)nl (J(dot)H(dot)M(dot) Dassen (Ray))
To: pgsql-sql(at)postgresql(dot)org
Subject: Re: Truncation of char, varchar, bit, varbit types (fwd)
Date: 2001-05-23 13:04:36
Message-ID: slrn9gndb4.oth.jdassen@odin.cistron-office.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Peter Eisentraut <peter_e(at)gmx(dot)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

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Chris Ruprecht 2001-05-23 13:23:39 Select question
Previous Message Martin Smetak 2001-05-23 09:07:56 Recursive select