From: | Vik Fearing <vik(at)postgresfriends(dot)org> |
---|---|
To: | nozdrum(at)gmx(dot)de, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #16726: Invalid input syntax is not a useful error message |
Date: | 2020-11-19 00:15:09 |
Message-ID: | 1113de7f-65e1-2c2b-2bbf-31b4a5733f2c@postgresfriends.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 11/19/20 12:55 AM, PG Bug reporting form wrote:
> The following bug has been logged on the website:
>
> Example-query i tried:
> update users set
> some_uuid_field = 'dec3d6c4-c32e-45c6-1eae3df44fbf'
> where
> id = 5
>
> What I want:
> a) That your documentation tells me the syntax for this
> b) That your error messages FOR ONCE are not useless and tell me the
> expected syntax, you are wasting millions of hours of developer time and
> human life, because you can not be asked to make useful error messages.
The documentation tells you exactly what the syntax should be, and the
error message couldn't be clearer. It says "specifically a group of 8
digits followed by three groups of 4 digits followed by a group of 12
digits" but you've only supplied two groups of 4 digits in the middle.
--
Vik Fearing
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2020-11-19 00:19:28 | Re: BUG #16726: Invalid input syntax is not a useful error message |
Previous Message | Andres Freund | 2020-11-19 00:06:56 | Re: BUG #16714: INSERT ON CONFLICT DO UPDATE fails to infer constraint if it's not at top-level partition |