| From: | tgl(at)svr1(dot)postgresql(dot)org (Tom Lane) |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql-server: While perusing SQL92 I realized that we are delivering the |
| Date: | 2004-08-02 16:51:17 |
| Message-ID: | 20040802165117.DA7CAD1B1FD@svr1.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Log Message:
-----------
While perusing SQL92 I realized that we are delivering the wrong SQLSTATE
error code for string-too-long errors. It should be STRING_DATA_RIGHT_TRUNCATION
not STRING_DATA_LENGTH_MISMATCH. The latter probably should only be
applied to cases where a string must be exactly so many bits --- there are
no cases at all where it applies to character strings, only bit strings.
Modified Files:
--------------
pgsql-server/src/backend/utils/adt:
varbit.c (r1.39 -> r1.40)
(http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/backend/utils/adt/varbit.c.diff?r1=1.39&r2=1.40)
varchar.c (r1.104 -> r1.105)
(http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/backend/utils/adt/varchar.c.diff?r1=1.104&r2=1.105)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-08-02 17:03:55 | pgsql-server: Actually, there's no need to use pg_strcasecmp for |
| Previous Message | Peter Eisentraut | 2004-08-02 15:17:22 | pgsql-server: Translation updates |