Tarantool development patches archive
 help / color / mirror / Atom feed
From: Imeev Mergen <imeevma@tarantool.org>
To: "n.pettik" <korablev@tarantool.org>, tarantool-patches@freelists.org
Subject: [tarantool-patches] Re: [PATCH v1 3/3] sql: make SQL_TARANTOOL_ERROR the only errcode of OP_Halt
Date: Sun, 5 May 2019 15:16:32 +0300	[thread overview]
Message-ID: <91100cee-d622-9e53-bb09-60c4d62f762e@tarantool.org> (raw)
In-Reply-To: <0CEB3ED4-A19F-49FE-A074-5BD174D7FCF4@tarantool.org>

[-- Attachment #1: Type: text/plain, Size: 1497 bytes --]


On 4/29/19 2:35 AM, n.pettik wrote:
>
>
>> On 26 Apr 2019, at 10:37, Mergen Imeev <imeevma@tarantool.org 
>> <mailto:imeevma@tarantool.org>> wrote:
>>
>> On Mon, Apr 15, 2019 at 06:19:34PM +0300, n.pettik wrote:
>>> 'make ... the only errcode of OP_Halt’ ->
>>> make … be the only ...
>>>
>>>> On 12 Apr 2019, at 15:34,imeevma@tarantool.org 
>>>> <mailto:imeevma@tarantool.org>wrote:
>>>>
>>>> After this patch, the only error code that the OP_Halt opcode
>>>> will work with is SQL_TARANTOOL_ERROR.
>>>
>>> So, why do we need it at all now? Let’s use simple flag
>>> is_aborted like in parser.
>>>
>> I could not do it now.
>> I think we will do this when rc is one of
>> SQL_OK, SQL_ROW, SQL_DONE or SQL_TARANTOOL_ERROR. This will be in
>> the next patch-set.
>
> That’s OK, but still don’t understand what prevents you from
> doing it right now..BTW, I don’t see corresponding patch in the
> patch-set you’ve already sent (next one).
The rc field is used to return some information from functions
that return an error code in case something went wrong. In this
regard, I think that we can completely remove this field instead
of replacing it with is_aborted. However, after I tried to do
this, I found that at the moment it had too many connections with
the code. I'm not quite sure that it will be safe to remove the rc
field right now. I would suggest removing some unused modules and
reworking the memory system into SQL before we remove the rc field
from the Vdbe structure.

[-- Attachment #2: Type: text/html, Size: 7397 bytes --]

      reply	other threads:[~2019-05-05 12:16 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] " 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
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 [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=91100cee-d622-9e53-bb09-60c4d62f762e@tarantool.org \
    --to=imeevma@tarantool.org \
    --cc=korablev@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --subject='[tarantool-patches] Re: [PATCH v1 3/3] sql: make SQL_TARANTOOL_ERROR the only errcode of 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