From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lj1-f194.google.com (mail-lj1-f194.google.com [209.85.208.194]) (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 933AA43D678 for ; Wed, 16 Oct 2019 15:53:18 +0300 (MSK) Received: by mail-lj1-f194.google.com with SMTP id q64so23873701ljb.12 for ; Wed, 16 Oct 2019 05:53:18 -0700 (PDT) Date: Wed, 16 Oct 2019 15:53:16 +0300 From: Konstantin Osipov Message-ID: <20191016125316.GA23564@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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191016124738.GB12432@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 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? -- Konstantin Osipov, Moscow, Russia