| From: | Sherrylyn Branchaw <sbranchaw(at)gmail(dot)com> | 
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> | 
| Cc: | pgsql-hackers(at)postgresql(dot)org | 
| Subject: | Re: Change error code for hstore syntax error | 
| Date: | 2016-05-09 17:42:48 | 
| Message-ID: | CAB_myF5F3eyNr0q6_hYTTvnKbSmE24_Ot5fCcKrtEoZYf0jWzg@mail.gmail.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
Finally returning to this...
> Hm, class 42 is generally meant for SQL-level syntax errors.  Are these
> errors not coming from subroutines of hstore_in()?  I think our usual
> convention is to use ERRCODE_INVALID_TEXT_REPRESENTATION for complaints
> that a data value does not meet its type's conventions.  In any case
> it seems closer to class 22 than 42.
>
I see, thanks for pointing that out. That seems like a useful distinction
to preserve. I've updated it to ERRCODE_INVALID_TEXT_REPRESENTATION
accordingly.
These seem to have multiple problems, starting with incorrect
> capitalization and extending to failure to quote the whole string
> being complained of.
I've modified the messages to comply with the guidelines, with a little
help from a colleague who actually knows C.
I'm attaching a revised patch; please let me know if there are any other
issues before I submit to the commitfest.
Best,
Sherrylyn
| Attachment | Content-Type | Size | 
|---|---|---|
| hstore_syntax_errcode_V2.patch | text/x-patch | 4.3 KB | 
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2016-05-09 18:33:37 | Re: asynchronous and vectorized execution | 
| Previous Message | Robert Haas | 2016-05-09 17:33:55 | asynchronous and vectorized execution |