Tarantool development patches archive
 help / color / mirror / Atom feed
From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
To: "n.pettik" <korablev@tarantool.org>, tarantool-patches@freelists.org
Subject: [tarantool-patches] Re: [PATCH 8/9] sql: make LIKE predicate return boolean result
Date: Mon, 22 Apr 2019 21:02:17 +0300	[thread overview]
Message-ID: <ff2e93a7-dc61-290f-fee1-d62a941b83f3@tarantool.org> (raw)
In-Reply-To: <BB69349E-1E1C-4CA0-94CA-2BB066A9E4AF@tarantool.org>

Thanks for the fixes!

> diff --git a/src/box/sql/vdbemem.c b/src/box/sql/vdbemem.c
> index 1590a3550..69aea5ef5 100644
> --- a/src/box/sql/vdbemem.c
> +++ b/src/box/sql/vdbemem.c
> @@ -803,7 +803,7 @@ sqlVdbeMemSetInt64(Mem * pMem, i64 val)
>  }
>  
>  void
> -vdbe_mem_set_boolean(struct Mem *mem, bool value)
> +vdbe_mem_set_bool(struct Mem *mem, bool value)
>  {
> 

1. We now have mem_value_bool(), and so as to be consistent
it would be better to name this function mem_set_bool(), not
vdbe_mem_set_bool(). It does not take struct Vdbe pointer
anyway.

2. Is there any concrete reason why vdbe_mem_set_bool() is
not used now in the following places?

vdbe.c:1101
	pOut = out2Prerelease(p, pOp);
	assert(pOp->p1 == 1 || pOp->p1 == 0);
	pOut->flags = MEM_Bool;
	pOut->u.b = pOp->p1;
	break;

vdbe.c:2275
	memAboutToChange(p, pOut);
	MemSetTypeFlag(pOut, MEM_Bool);
	pOut->u.b = res2;
	REGISTER_TRACE(pOp->p2, pOut);

vdbe.c:2471
	pOut->u.b = v1;
	MemSetTypeFlag(pOut, MEM_Bool);

vdbe.c:2495
	pOut->flags = MEM_Bool;
	pOut->u.b = ! pIn1->u.b;

If it works for them, then I propose to move vdbe_mem_set_bool()
to the patch 'sql: introduce type boolean', and use it.

Also, please, consider this minor review fix, on the branch:

==================================================================
diff --git a/src/box/sql/sqlInt.h b/src/box/sql/sqlInt.h
index 8426f9b5f..07c887bb4 100644
--- a/src/box/sql/sqlInt.h
+++ b/src/box/sql/sqlInt.h
@@ -499,7 +499,7 @@ void
 sql_result_int(sql_context *, int);
 
 void
-sql_result_bool(sql_context *ctx, bool value);
+sql_result_bool(struct sql_context *ctx, bool value);
 
 void
 sql_result_int64(sql_context *, sql_int64);
diff --git a/src/box/sql/vdbeapi.c b/src/box/sql/vdbeapi.c
index c2a319dbd..9a405c8ee 100644
--- a/src/box/sql/vdbeapi.c
+++ b/src/box/sql/vdbeapi.c
@@ -387,7 +387,7 @@ sql_result_int(sql_context * pCtx, int iVal)
 }
 
 void
-sql_result_bool(sql_context *ctx, bool value)
+sql_result_bool(struct sql_context *ctx, bool value)
 {
 	vdbe_mem_set_bool(ctx->pOut, value);
 }

  reply	other threads:[~2019-04-22 18:02 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-14 15:03 [tarantool-patches] [PATCH 0/9] Introduce type BOOLEAN in SQL Nikita Pettik
2019-04-14 15:03 ` [tarantool-patches] [PATCH 1/9] sql: refactor mem_apply_numeric_type() Nikita Pettik
2019-04-14 15:04 ` [tarantool-patches] [PATCH 2/9] sql: disallow text values participate in sum() aggregate Nikita Pettik
2019-04-16 14:12   ` [tarantool-patches] " Vladislav Shpilevoy
2019-04-18 17:54     ` n.pettik
2019-04-22 18:02       ` Vladislav Shpilevoy
2019-04-23 19:58         ` n.pettik
2019-04-14 15:04 ` [tarantool-patches] [PATCH 3/9] sql: use msgpack types instead of custom ones Nikita Pettik
2019-04-16 14:12   ` [tarantool-patches] " Vladislav Shpilevoy
2019-04-18 17:54     ` n.pettik
2019-04-22 18:02       ` Vladislav Shpilevoy
2019-04-23 19:58         ` n.pettik
2019-04-14 15:04 ` [tarantool-patches] [PATCH 4/9] sql: introduce type boolean Nikita Pettik
2019-04-16 14:12   ` [tarantool-patches] " Vladislav Shpilevoy
2019-04-18 17:54     ` n.pettik
2019-04-22 18:02       ` Vladislav Shpilevoy
2019-04-23 19:58         ` n.pettik
2019-04-23 21:06           ` Vladislav Shpilevoy
2019-04-14 15:04 ` [tarantool-patches] [PATCH 5/9] sql: improve type determination for column meta Nikita Pettik
2019-04-16 14:12   ` [tarantool-patches] " Vladislav Shpilevoy
2019-04-18 17:54     ` n.pettik
2019-04-22 18:02       ` Vladislav Shpilevoy
2019-04-23 19:58         ` n.pettik
2019-04-14 15:04 ` [tarantool-patches] [PATCH 6/9] sql: make comparison predicate return boolean Nikita Pettik
2019-04-16 14:12   ` [tarantool-patches] " Vladislav Shpilevoy
2019-04-18 17:54     ` n.pettik
2019-04-14 15:04 ` [tarantool-patches] [PATCH 7/9] sql: make predicates accept and " Nikita Pettik
2019-04-16 14:12   ` [tarantool-patches] " Vladislav Shpilevoy
2019-04-18 17:55     ` n.pettik
2019-04-14 15:04 ` [tarantool-patches] [PATCH 9/9] sql: make <search condition> accept only boolean Nikita Pettik
2019-04-16 14:12   ` [tarantool-patches] " Vladislav Shpilevoy
2019-04-18 17:55     ` n.pettik
2019-04-22 18:02       ` Vladislav Shpilevoy
2019-04-23 19:59         ` n.pettik
2019-04-23 21:06           ` Vladislav Shpilevoy
2019-04-23 22:01             ` n.pettik
     [not found] ` <b2a84f129c2343d3da3311469cbb7b20488a21c2.1555252410.git.korablev@tarantool.org>
2019-04-16 14:12   ` [tarantool-patches] Re: [PATCH 8/9] sql: make LIKE predicate return boolean result Vladislav Shpilevoy
2019-04-18 17:55     ` n.pettik
2019-04-22 18:02       ` Vladislav Shpilevoy [this message]
2019-04-23 19:58         ` n.pettik
2019-04-24 10:28 ` [tarantool-patches] Re: [PATCH 0/9] Introduce type BOOLEAN in SQL Vladislav Shpilevoy
2019-04-25  8:46 ` Kirill Yukhin

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=ff2e93a7-dc61-290f-fee1-d62a941b83f3@tarantool.org \
    --to=v.shpilevoy@tarantool.org \
    --cc=korablev@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --subject='[tarantool-patches] Re: [PATCH 8/9] sql: make LIKE predicate return boolean result' \
    /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