From: | Daniel Migowski <dmigowski(at)ikoffice(dot)de> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #14179: Not enough info in error message |
Date: | 2016-06-07 13:39:10 |
Message-ID: | 41ED3F5450C90F4D8381BC4D8DF6BBDCAF46A92D@EXCHANGESERVER.ikoffice.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hello David,
thanks for you detailed answer. Maybe I check the lists when the feature becomes so urgent that I need to fix it myself.
Regards,
Daniel Migowski
On Tue, Jun 7, 2016 at 3:50 AM, <dmigowski(at)ikoffice(dot)de<mailto:dmigowski(at)ikoffice(dot)de>> wrote:
The following bug has been logged on the website:
Bug reference: 14179
Logged by: Daniel Migowski
Email address: dmigowski(at)ikoffice(dot)de<mailto: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.
This is a frequent complaint with no easy, and in some queries no possible, solution.
I would love to see something like: "value too long for type character
varying(160) in column mytable.mycolumn"
CREATE TABLE sample (col text CHECK (length(col) <= 160));
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.
Even if this was improved upon it would never be back-ported. It is not a bug.
There is more in-depth discussion out there on these lists but I do not have the time at the moment to search around for it.
I did check the FAQ and this topic does not appear there :( Maybe it will in the future...
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-06-07 16:23:35 | Re: [BUGS] BUG #14155: bloom index error with unlogged table |
Previous Message | David G. Johnston | 2016-06-07 13:38:46 | Re: Case in Order By Ignored without warning or error |