From: "n.pettik" <korablev@tarantool.org> To: tarantool-patches@freelists.org Cc: Imeev Mergen <imeevma@tarantool.org> Subject: [tarantool-patches] Re: [PATCH v1 1/1] sql: rework five syntax errors Date: Thu, 21 Feb 2019 22:01:22 +0300 [thread overview] Message-ID: <2B41863C-0BA8-4D93-A296-9F5523D59714@tarantool.org> (raw) In-Reply-To: <ce92027aadf2864da791ff55285122d7fab96fcf.1550763542.git.imeevma@gmail.com> > On 21 Feb 2019, at 18:40, imeevma@tarantool.org wrote: > > This patch reworks five syntax errors. Why only five? There are 10 errors at all, so lets finish this part adding all syntax errors. > These SQL errors were > converted into Tarantool errors. > > Part of #3965 > --- > https://github.com/tarantool/tarantool/issues/3965 > https://github.com/tarantool/tarantool/tree/imeevma/gh-3965-use-diag_set-to-describe-error > > diff --git a/src/box/errcode.h b/src/box/errcode.h > index 1523b19..1807151 100644 > --- a/src/box/errcode.h > +++ b/src/box/errcode.h > @@ -230,6 +230,11 @@ struct errcode_record { > /*175 */_(ER_SQL_NO_SUCH_PRAGMA, "Pragma '%s' does not exist") \ > /*176 */_(ER_SQL_CANT_RESOLVE_FIELD, "Can’t resolve field '%s'") \ > /*177 */_(ER_INDEX_EXISTS_IN_SPACE, "Index '%s' already exists in space '%s'") \ > + /*178 */_(ER_SQL_SYNTAX, "Syntax error in %s: %s") \ > + /*179 */_(ER_SQL_STACK_OVERFLOW, "Failed to parse SQL statement: parser stack limit reached") \ > + /*180 */_(ER_SQL_SELECT_WILDCARD, "Failed to expand '*' in SELECT statement without FROM clause") \ > + /*181 */_(ER_SQL_STATEMENT_EMPTY, "Failed to execute an empty SQL statement") \ I’ve already said that: why do we consider empty query as an error? Don’t understand. The rest is ok as obvious.
prev parent reply other threads:[~2019-02-21 19:01 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-02-21 15:40 [tarantool-patches] " imeevma 2019-02-21 19:01 ` n.pettik [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=2B41863C-0BA8-4D93-A296-9F5523D59714@tarantool.org \ --to=korablev@tarantool.org \ --cc=imeevma@tarantool.org \ --cc=tarantool-patches@freelists.org \ --subject='[tarantool-patches] Re: [PATCH v1 1/1] sql: rework five syntax errors' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox