From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <kostja@tarantool.org>
Date: Mon, 8 Jul 2019 12:25:06 +0300
From: Konstantin Osipov <kostja@tarantool.org>
Subject: Re: [PATCH 5/5] Allow to execute non-yielding DDL statements in
 transactions
Message-ID: <20190708092506.GA8512@atlas>
References: <cover.1562357452.git.vdavydov.dev@gmail.com>
 <2f4db121e3afe9599172b9a3abf8a48ab47e524b.1562357452.git.vdavydov.dev@gmail.com>
 <20190705225635.GB30966@atlas>
 <20190708080934.hp3zgk6ppw5mu2ww@esperanza>
 <20190708082116.GB21719@atlas>
 <20190708084330.dkh5zj4v67unt46o@esperanza>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20190708084330.dkh5zj4v67unt46o@esperanza>
To: Vladimir Davydov <vdavydov.dev@gmail.com>
Cc: tarantool-patches@freelists.org
List-ID: <tarantool-patches.dev.tarantool.org>

* Vladimir Davydov <vdavydov.dev@gmail.com> [19/07/08 11:45]:
> > In any case you test a fixed number of combinations, and should
> > come up with a randomized test. This feature encompasses all DDL
> > operators, including:
> > 
> > - roles
> > - users
> > - functions
> > - SQL triggers
> > - SQL foreign key constraints
> > - SQL views
> > - SQL check constraints
> > 
> > Every object should be involved in the test, and the generated
> > transactions should be random.
> 
> Sounds tricky :-/ May be, hand this over to Q&A?

Nobody is going to write the test better than you. You may even
hand this over to mermaids or some other mythical creature, if you
don't want this to happen.

-- 
Konstantin Osipov, Moscow, Russia