From: Imeev Mergen <imeevma@tarantool.org> To: "n.pettik" <korablev@tarantool.org>, tarantool-patches@freelists.org Subject: [tarantool-patches] Re: [PATCH v1 2/3] sql: rework diag_set() in OP_Halt Date: Mon, 29 Apr 2019 18:05:17 +0300 [thread overview] Message-ID: <912f6a63-c955-f58b-22d6-f0128e05163a@tarantool.org> (raw) In-Reply-To: <353E4E8B-DA71-4F64-8A61-4E89151E7B5B@tarantool.org> Hi! Thank you for review. Next time I will send this patch as part of "diag_set() in vdbe" patch-set. On 4/29/19 2:35 AM, n.pettik wrote: > >> On 26 Apr 2019, at 10:48, Mergen Imeev <imeevma@tarantool.org> wrote: >> >> On Mon, Apr 15, 2019 at 06:21:55PM +0300, n.pettik wrote: >>> >>>> On 12 Apr 2019, at 15:34, imeevma@tarantool.org wrote: >>>> >>>> Before this patch it was possible to have an error code with wrong >>>> error description. This patch fixes it. >>> Could you please supply this statement with an example(s)? >>> >> I changed the commit message. In fact, I found an error that had >> no error code at all: > Could you fix that? Already done in this commit. > >> ... >> >> tarantool> box.execute('select 1 limit true') >> --- >> - error: Only positive integers are allowed in the LIMIT clause >> ... >> >> tarantool> box.error.last().code >> --- >> - 0 >> ... >> >> >> I still think it would be better to use P3 instead of P5. > Does it matter? This will allow using only one statement instead of two. The error described above was caused by the lack of the second statement. After this patch, this case is less likely, because if there is no second operator, an “unknown error” will be shown.
next prev parent reply other threads:[~2019-04-29 15:05 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-04-12 12:34 [tarantool-patches] [PATCH v1 0/3] sql: make SQL_TARANTOOL_ERROR the only errcode of OP_Halt imeevma 2019-04-12 12:34 ` [tarantool-patches] [PATCH v1 1/3] sql: remove mayAbort field from struct Parse imeevma 2019-04-15 14:06 ` [tarantool-patches] " n.pettik 2019-04-22 7:49 ` Imeev Mergen 2019-04-26 7:25 ` Mergen Imeev 2019-04-28 23:35 ` n.pettik 2019-04-12 12:34 ` [tarantool-patches] [PATCH v1 2/3] sql: rework diag_set() in OP_Halt imeevma 2019-04-15 15:21 ` [tarantool-patches] " n.pettik 2019-04-22 8:24 ` Imeev Mergen 2019-04-24 12:19 ` n.pettik 2019-04-26 7:48 ` Mergen Imeev 2019-04-28 23:35 ` n.pettik 2019-04-29 15:05 ` Imeev Mergen [this message] 2019-05-05 11:31 ` Imeev Mergen 2019-04-12 12:34 ` [tarantool-patches] [PATCH v1 3/3] sql: make SQL_TARANTOOL_ERROR the only errcode of OP_Halt imeevma 2019-04-15 15:19 ` [tarantool-patches] " n.pettik 2019-04-22 8:47 ` Imeev Mergen 2019-04-22 9:53 ` Imeev Mergen 2019-04-26 7:37 ` Mergen Imeev 2019-04-28 23:35 ` n.pettik 2019-05-05 12:16 ` Imeev Mergen
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=912f6a63-c955-f58b-22d6-f0128e05163a@tarantool.org \ --to=imeevma@tarantool.org \ --cc=korablev@tarantool.org \ --cc=tarantool-patches@freelists.org \ --subject='[tarantool-patches] Re: [PATCH v1 2/3] sql: rework diag_set() in OP_Halt' \ /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