Tarantool development patches archive
 help / color / mirror / Atom feed
From: Nikita Pettik <korablev@tarantool.org>
To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Cc: tarantool-patches@freelists.org, tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH 0/3] Booleans and lower vs upper
Date: Thu, 31 Oct 2019 02:28:32 +0300	[thread overview]
Message-ID: <20191030232832.GA77516@tarantool.org> (raw)
In-Reply-To: <cover.1572211914.git.v.shpilevoy@tarantool.org>

On 27 Oct 22:35, Vladislav Shpilevoy wrote:
> The patchset contains 3 independent commits fixing some minor
> things in SQL.
> 
> The commit messages below speak for themselves, everything is
> trivial.

Pushed first and second patches. I will push the last one at the end of
week if Kirill doesn't look at it earlier.
 
> This patchset is mostly about problems mentioned in #4462, but
> does not close it. Because I don't know to fix the last problem
> yet, and don't know whether I will do it.
> 
> Branch: http://github.com/tarantool/tarantool/tree/gerold103/gh-4462-sql-boolean-bugs
> Issue: https://github.com/tarantool/tarantool/issues/4462
> 

      parent reply	other threads:[~2019-10-30 23:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-27 21:35 Vladislav Shpilevoy
2019-10-27 21:35 ` [Tarantool-patches] [PATCH 1/3] sql: LENGTH function accepts boolean Vladislav Shpilevoy
2019-10-27 21:35 ` [Tarantool-patches] [PATCH 2/3] sql: CAST(<boolean> AS TEXT) returns lowercase Vladislav Shpilevoy
2019-10-28 14:08   ` Nikita Pettik
2019-10-28 21:48     ` Vladislav Shpilevoy
2019-10-27 21:35 ` [Tarantool-patches] [PATCH 3/3] sql: make type string case lower everywhere Vladislav Shpilevoy
2019-10-28 14:23   ` Nikita Pettik
2019-10-28 21:45     ` Vladislav Shpilevoy
2019-11-07 12:40       ` Nikita Pettik
2019-10-30 23:28 ` Nikita Pettik [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=20191030232832.GA77516@tarantool.org \
    --to=korablev@tarantool.org \
    --cc=tarantool-patches@dev.tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --cc=v.shpilevoy@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH 0/3] Booleans and lower vs upper' \
    /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