| From: | dmigowski(at)ikoffice(dot)de |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | BUG #14179: Not enough info in error message |
| Date: | 2016-06-07 07:50:36 |
| Message-ID: | 20160607075036.1379.75605@wrigleys.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 14179
Logged by: Daniel Migowski
Email address: dmigowski(at)ikoffice(dot)de
PostgreSQL version: 9.5.2
Operating system: all
Description:
Hello,
I often get some error like: value too long for type character varying(160).
Not it is hard for me to check which column contained the constraint.
I would love to see something like: "value too long for type character
varying(160) in column mytable.mycolumn"
This would have safed me at least 20 hours during the last years!
If you fix this, please backport to 9.5, and I would immediately upgrade all
our servers. Thanks a lot in advance.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2016-06-07 07:55:10 | Re: BUG #14178: output of jsonb_object and json_object doesn't match textually |
| Previous Message | Michael Paquier | 2016-06-07 06:54:54 | Re: BUG #14178: output of jsonb_object and json_object doesn't match textually |