From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
---|---|
To: | "'Peter Eisentraut'" <peter_e(at)gmx(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | AW: Truncation of char, varchar types |
Date: | 2001-04-10 10:46:55 |
Message-ID: | 11C1E6749A55D411A9670001FA68796336827F@sdexcsrv1.f000.d0188.sd.spardat.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Excessively long values are currently silently truncated when they are
> inserted into char or varchar fields. This makes the entire notion of
> specifying a length limit for these types kind of useless, IMO. Needless
> to say, it's also not in compliance with SQL.
To quote Tom "paragraph and verse please" :-)
> How do people feel about changing this to raise an error in this
> situation?
Can't do.
> Does anybody rely on silent truncation?
Yes, iirc the only thing you are allowed to do is issue a warning,
but the truncation is allowed and must succeed.
(checked in Informix and Oracle)
The appropriate SQLSTATE is: "01004" String data, right truncation
note that class 01 is a "success with warning".
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Alessio Bragadini | 2001-04-10 11:44:34 | Re: Truncation of char, varchar types |
Previous Message | Alvar Freude | 2001-04-10 10:37:20 | Indexes not used in 7.1RC4: Bug? |