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: Mon, 29 Apr 2019 02:35:29 +0300 [thread overview]
Message-ID: <353E4E8B-DA71-4F64-8A61-4E89151E7B5B@tarantool.org> (raw)
In-Reply-To: <20190426074808.GC23413@tarantool.org>
> 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?
> ...
>
> 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?
>
>
> New patch:
>
> From 4c1ad4e67773232168f13b0d501f4476673b57c6 Mon Sep 17 00:00:00 2001
> Date: Fri, 12 Apr 2019 14:16:18 +0300
> Subject: [PATCH] sql: rework diag_set() in OP_Halt
>
> Prior to this patch, the way to set Tarantool error in OP_Halt was
> too universal. It was possible to set a description of the error
> that does not match its errcode. This change will also make it
> easier to work with an error in OP_Halt, since you no longer need
> to create a complete error message.
Please, inline exactly the same example as you shown
in previous mail.
next prev parent reply other threads:[~2019-04-28 23:35 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 [this message]
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=353E4E8B-DA71-4F64-8A61-4E89151E7B5B@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