From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <korablev@tarantool.org>
Received: from smtpng3.m.smailru.net (smtpng3.m.smailru.net [94.100.177.149])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256
 bits)) (No client certificate requested)
 by dev.tarantool.org (Postfix) with ESMTPS id 8D6D541D0BD
 for <tarantool-patches@dev.tarantool.org>;
 Wed, 16 Oct 2019 16:13:16 +0300 (MSK)
Date: Wed, 16 Oct 2019 16:13:15 +0300
From: Nikita Pettik <korablev@tarantool.org>
Message-ID: <20191016131315.GC12432@tarantool.org>
References: <cover.1571068485.git.kshcherbatov@tarantool.org>
 <20191015213405.GB898@tarantool.org> <20191016055725.GB16587@atlas>
 <20191016110739.GB11847@tarantool.org>
 <20191016111142.GA16144@atlas>
 <20191016121811.GA12432@tarantool.org>
 <20191016123257.GA20923@atlas>
 <20191016124738.GB12432@tarantool.org>
 <20191016125316.GA23564@atlas>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20191016125316.GA23564@atlas>
Subject: Re: [Tarantool-patches] [tarantool-patches] [PATCH v1 0/9] schema:
	rework _trigger space
List-Id: Tarantool development <tarantool-patches.dev.tarantool.org>
List-Unsubscribe: <https://lists.tarantool.org/mailman/options/tarantool-patches>, 
 <mailto:tarantool-patches-request@dev.tarantool.org?subject=unsubscribe>
List-Archive: <https://lists.tarantool.org/pipermail/tarantool-patches/>
List-Post: <mailto:tarantool-patches@dev.tarantool.org>
List-Help: <mailto:tarantool-patches-request@dev.tarantool.org?subject=help>
List-Subscribe: <https://lists.tarantool.org/mailman/listinfo/tarantool-patches>, 
 <mailto:tarantool-patches-request@dev.tarantool.org?subject=subscribe>
To: Konstantin Osipov <kostja.osipov@gmail.com>
Cc: tarantool-patches@freelists.org, tarantool-patches@dev.tarantool.org

On 16 Oct 15:53, Konstantin Osipov wrote:
> * Nikita Pettik <korablev@tarantool.org> [19/10/16 15:48]:
> > > > Okay, let's enumerate all possible properties of _trigger space (I've taken
> > > > version from the last RFC):
> > > > 
> > > > - name (both have)
> > > 
> > > If there will be persistent lua triggers, would it be possible to
> > > drop them from SQL? With what construct? What will be their name
> > > space (same name space as SQL triggers, or a distinct names space)?
> > > Case sensitivity? 
> > 
> > IMHO there should be no opportunity to drop Lua NoSQL triggers from SQL;
> > they should share different namespaces (as it happens now). The reason
> > is that SQL triggers will be implemented as NoSQL on_replace triggers
> > under the hood.
> 
> This is true for non-persistent triggers. What if we ever decide
> to persist Lua triggers?

Why there should be any difference between them? Persisted Lua triggers
have nothing in common with SQL triggers. They are just parsed and re-created
after restart. Then they behave as normal (in-memory) NoSQL triggers.
 
> -- 
> Konstantin Osipov, Moscow, Russia