Tarantool development patches archive
 help / color / mirror / Atom feed
From: Konstantin Osipov <kostja@tarantool.org>
To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Cc: tarantool-patches@freelists.org, korablev@tarantool.org
Subject: [tarantool-patches] Re: [PATCH 2/2] sql: transactional DDL
Date: Sat, 20 Jul 2019 18:16:53 +0300	[thread overview]
Message-ID: <20190720151653.GA4063@atlas> (raw)
In-Reply-To: <4a273360-5db0-7b3a-1094-d28e18688139@tarantool.org>

* Vladislav Shpilevoy <v.shpilevoy@tarantool.org> [19/07/20 17:02]:
> Firstly, Lua tests still are easier to copy paste into console
> as is. Secondly, I just used to write Lua tests. Thirdly, I
> don't like tap tests, because you need compare results
> manually instead of just printing them.

SQL is not tap and there is SQL console you can use.

So it seems only a habit, inertia.

Lua + SQL tests are harder to maintain that plain SQL. If there is
no limitation of SLQ testsing system that you have hit, please use
SQL tests for all new SQL test files.

-- 
Konstantin Osipov, Moscow, Russia

  reply	other threads:[~2019-07-20 15:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-19 22:49 [tarantool-patches] [PATCH 0/2] SQL TXN DDL Vladislav Shpilevoy
2019-07-19 22:49 ` [tarantool-patches] [PATCH 1/2] alter: do not access space in drop ck commit trigger Vladislav Shpilevoy
2019-07-19 22:49 ` [tarantool-patches] [PATCH 2/2] sql: transactional DDL Vladislav Shpilevoy
2019-07-20  7:42   ` [tarantool-patches] " Konstantin Osipov
2019-07-20 14:02     ` Vladislav Shpilevoy
2019-07-20 15:16       ` Konstantin Osipov [this message]
2019-07-22 13:59   ` n.pettik
2019-07-22 21:35     ` Vladislav Shpilevoy
2019-07-24 13:23       ` n.pettik
2019-07-24 20:58         ` Vladislav Shpilevoy
2019-07-25 12:04           ` n.pettik
2019-07-31 13:19 ` [tarantool-patches] Re: [PATCH 0/2] SQL TXN DDL 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=20190720151653.GA4063@atlas \
    --to=kostja@tarantool.org \
    --cc=korablev@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --cc=v.shpilevoy@tarantool.org \
    --subject='[tarantool-patches] Re: [PATCH 2/2] sql: transactional DDL' \
    /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