From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
To: Imeev Mergen <imeevma@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH v2 1/1] sql: do not change order of inserted values
Date: Sun, 12 Apr 2020 16:02:51 +0200 [thread overview]
Message-ID: <d3cd0b73-d7f7-e6ff-d648-bce82964059a@tarantool.org> (raw)
In-Reply-To: <19a63a12-1ef9-5e9c-21b7-5dc4c7b83584@tarantool.org>
>>> --- a/src/box/sql/vdbe.c
>>> +++ b/src/box/sql/vdbe.c
>>> @@ -2694,23 +2694,10 @@ case OP_Column: {
>>> pC->cacheStatus = p->cacheCtr;
>>> }
>>> enum field_type field_type = field_type_MAX;
>>> - if (pC->eCurType == CURTYPE_TARANTOOL) {
>>> - /*
>>> - * Ephemeral spaces feature only one index
>>> - * covering all fields, but ephemeral spaces
>>> - * lack format. So, we can fetch type from
>>> - * key parts.
>>> - */
>>> - if (pC->uc.pCursor->curFlags & BTCF_TEphemCursor) {
>>> - field_type = pC->uc.pCursor->index->def->
>>> - key_def->parts[p2].type;
>>> - } else if (pC->uc.pCursor->curFlags & BTCF_TaCursor) {
>>> - field_type = pC->uc.pCursor->space->def->
>>> - fields[p2].type;
>>> - }
>>> - } else if (pC->eCurType == CURTYPE_SORTER) {
>>> + if (pC->eCurType == CURTYPE_TARANTOOL)
>>> + field_type = pC->uc.pCursor->space->def->fields[p2].type;
>>> + else if (pC->eCurType == CURTYPE_SORTER)
>>> field_type = vdbe_sorter_get_field_type(pC->uc.pSorter, p2);
>>> - }
>>> struct Mem *default_val_mem =
>>> pOp->p4type == P4_MEM ? pOp->p4.pMem : NULL;
>>> if (vdbe_field_ref_fetch(&pC->field_ref, p2, pDest) != 0)
>> Shouldn't this be a part of the previous commit, which
>> introduces the ephemeral space format?
> They should, along with 3962. But, they have different milistones,
> I wasn't sure that it is right to put all three tickets in one
> patch-set.
But they already depend on each other. So what is a problem?
next prev parent reply other threads:[~2020-04-12 14:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 10:45 imeevma
2020-04-06 21:42 ` Vladislav Shpilevoy
2020-04-10 9:49 ` Mergen Imeev
2020-04-11 14:34 ` Vladislav Shpilevoy
2020-04-12 10:21 ` Imeev Mergen
2020-04-12 14:02 ` Vladislav Shpilevoy [this message]
2020-04-12 15:21 ` Imeev Mergen
2020-04-12 16:00 ` Vladislav Shpilevoy
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=d3cd0b73-d7f7-e6ff-d648-bce82964059a@tarantool.org \
--to=v.shpilevoy@tarantool.org \
--cc=imeevma@tarantool.org \
--cc=tarantool-patches@dev.tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH v2 1/1] sql: do not change order of inserted values' \
/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