From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lj1-f196.google.com (mail-lj1-f196.google.com [209.85.208.196]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id 4590843D678 for ; Wed, 16 Oct 2019 17:18:59 +0300 (MSK) Received: by mail-lj1-f196.google.com with SMTP id a22so24233281ljd.0 for ; Wed, 16 Oct 2019 07:18:59 -0700 (PDT) Date: Wed, 16 Oct 2019 17:18:57 +0300 From: Konstantin Osipov Message-ID: <20191016141857.GA28254@atlas> References: <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> <20191016131315.GC12432@tarantool.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191016131315.GC12432@tarantool.org> Subject: Re: [Tarantool-patches] [tarantool-patches] [PATCH v1 0/9] schema: rework _trigger space List-Id: Tarantool development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Nikita Pettik Cc: tarantool-patches@freelists.org, tarantool-patches@dev.tarantool.org * Nikita Pettik [19/10/16 16:14]: > > > > > 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. Should they be "visible" to SQL? They certainly have effect on SQL tables. If they are visible, should it be possible to enable, disable, drop or modify them? If yes, what SQL syntax do you suggest? If you suggest to use the same syntax as for SQL triggers, the issue of trigger namespace arises. -- Konstantin Osipov, Moscow, Russia