From: Kirill Shcherbatov <kshcherbatov@tarantool.org>
To: tarantool-patches@freelists.org
Cc: "v.shpilevoy@tarantool.org" <v.shpilevoy@tarantool.org>
Subject: [tarantool-patches] Re: [PATCH v2 2/2] Fixed lost format on update and upsert operations.
Date: Sat, 28 Apr 2018 09:56:51 +0300 [thread overview]
Message-ID: <0b6a2780-3eef-2da4-d68d-ff4c4870bf13@tarantool.org> (raw)
In-Reply-To: <d142deb8-b182-3706-96c9-338d1fe2085b@tarantool.org>
> Please, describe why we need inlined update here. 'Vlad insisted' is not a reason.
Unlike update and upsert, transform creates a new tuple with runtime format;
Moreover, the function inlining allowed to make allocations in the region, what is preferable.
> Vova means, that if tuple:transform would use non-default tuple format,
> the tests will pass anyway. Please, add a test on transform, that would not
> pass, if tuple uses non-default format.
> This test will pass even if we would use non-default tuple format
diff --git a/test/engine/update.result b/test/engine/update.result
index b73037e..6ab4436 100644
--- a/test/engine/update.result
+++ b/test/engine/update.result
@@ -728,11 +728,7 @@ aa:update({{'=',2, 666}})
aa:transform(-1, 1)
---
- [1, 'ssss', '3', '4', '5', '6']
-...
-aa:transform(1, 6)
---
-- ['7']
-...
aa = nil
---
...
diff --git a/test/engine/update.test.lua b/test/engine/update.test.lua
index e2a2265..3ff7e62 100644
--- a/test/engine/update.test.lua
+++ b/test/engine/update.test.lua
@@ -112,7 +112,6 @@ aa.VAL
aa:update({{'=',2, 666}})
-- test transform integrity
aa:transform(-1, 1)
-aa:transform(1, 6)
aa = nil
s:upsert({2, 'wwwww'}, {{'=', 2, 'wwwww'}})
next prev parent reply other threads:[~2018-04-28 6:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-06 16:24 [tarantool-patches] [PATCH v2 0/2] Fix lost format on update operation Kirill Shcherbatov
2018-04-06 16:24 ` [tarantool-patches] [PATCH v2 1/2] Fixed invalid check in lbox_tuple_transform Kirill Shcherbatov
2018-04-06 16:24 ` [tarantool-patches] [PATCH v2 2/2] Fixed lost format on update and upsert operations Kirill Shcherbatov
2018-04-08 13:56 ` [tarantool-patches] " Vladislav Shpilevoy
2018-04-10 10:23 ` Kirill Shcherbatov
2018-04-10 10:44 ` Vladislav Shpilevoy
2018-04-15 10:03 ` Kirill Shcherbatov
2018-04-15 13:18 ` Vladislav Shpilevoy
2018-04-16 7:47 ` Kirill Shcherbatov
2018-04-16 10:07 ` Vladislav Shpilevoy
2018-04-16 16:51 ` Kirill Shcherbatov
2018-04-16 17:14 ` Vladislav Shpilevoy
2018-04-18 12:28 ` Vladimir Davydov
2018-04-18 12:55 ` Kirill Shcherbatov
2018-04-22 15:15 ` Vladislav Shpilevoy
2018-04-28 6:56 ` Kirill Shcherbatov [this message]
2018-04-28 9:29 ` [tarantool-patches] Re: [PATCH v2 0/2] Fix lost format on update operation 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=0b6a2780-3eef-2da4-d68d-ff4c4870bf13@tarantool.org \
--to=kshcherbatov@tarantool.org \
--cc=tarantool-patches@freelists.org \
--cc=v.shpilevoy@tarantool.org \
--subject='[tarantool-patches] Re: [PATCH v2 2/2] Fixed lost format on update and upsert operations.' \
/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