Re: [HACKERS] Change error code for hstore syntax error

2016-09-28 Thread Sherrylyn Branchaw
Since no revised patch has been forthcoming and the CommitFest is due to end shortly, I've marked this "Returned with Feedback". Sherrylyn, please feel free to update the patch and resubmit to the next CommitFest. Will do, Robert, and many thanks to Marko for the feedback. I apologize for the

Re: [HACKERS] Change error code for hstore syntax error

2016-05-12 Thread Sherrylyn Branchaw
wrote: > On Mon, May 9, 2016 at 1:42 PM, Sherrylyn Branchaw <sbranc...@gmail.com> > wrote: > > I'm attaching a revised patch; please let me know if there are any other > > issues before I submit to the commitfest. > > Submitting to the CommitFest is how you make sure that

Re: [HACKERS] Change error code for hstore syntax error

2016-05-09 Thread Sherrylyn Branchaw
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

[HACKERS] Change error code for hstore syntax error

2016-03-11 Thread Sherrylyn Branchaw
The hstore module uses elog() to default to ERRCODE_INTERNAL_ERROR (SQLSTATE XX000) when the error message reads "Syntax error near '%c' at position %d". I propose to switch to ereport() to return ERRCODE_SYNTAX_ERROR (SQLSTATE 42601), on the grounds that it's more transparent. It took me longer