From: "n.pettik" <korablev@tarantool.org>
To: tarantool-patches@freelists.org
Cc: Imeev Mergen <imeevma@tarantool.org>
Subject: [tarantool-patches] Re: [PATCH v1 2/3] sql: rework diag_set() in OP_Halt
Date: Wed, 24 Apr 2019 15:19:30 +0300 [thread overview]
Message-ID: <4E612CAF-555E-4D2E-A8AF-DC6378E8468A@tarantool.org> (raw)
In-Reply-To: <5d156e98-7b9c-09ec-b14f-3150a6e515c8@tarantool.org>
> On 22 Apr 2019, at 11:24, Imeev Mergen <imeevma@tarantool.org> wrote:
>
>
> On 4/15/19 6:21 PM, 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)?
>
> Here it is:
>
> tarantool> box.execute("CREATE TABLE t(a INT PRIMARY KEY, b INT);")
> ---
> - row_count: 1
> ...
>
> tarantool> box.execute("INSERT INTO t VALUES (1,2), (3,4);")
> ---
> - row_count: 2
> ...
>
> tarantool> box.execute("SELECT b FROM t WHERE a = (SELECT a FROM t);")
> ---
> - error: 'SQL error: Expression subquery returned more than 1 row'
> ...
>
> tarantool> box.error.last().code
> ---
> - 159
> ...
>
>
> From the error message, we can say that this is an ER_SQL(160)
> error. But this is wrong, as this is an ER_SQL_EXECUTE(159) error.
I mean add this explanation to the commit message. Also, what is the
difference between ER_SQL and ER_SQL_EXECUTE? Their descriptions
look almost identical.
next prev parent reply other threads:[~2019-04-24 12:19 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 [this message]
2019-04-26 7:48 ` Mergen Imeev
2019-04-28 23:35 ` n.pettik
2019-04-29 15:05 ` Imeev Mergen
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=4E612CAF-555E-4D2E-A8AF-DC6378E8468A@tarantool.org \
--to=korablev@tarantool.org \
--cc=imeevma@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