From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lj1-f195.google.com (mail-lj1-f195.google.com [209.85.208.195]) (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 963134429A8 for ; Thu, 17 Oct 2019 10:35:34 +0300 (MSK) Received: by mail-lj1-f195.google.com with SMTP id v24so1436954ljj.3 for ; Thu, 17 Oct 2019 00:35:34 -0700 (PDT) Date: Thu, 17 Oct 2019 10:35:32 +0300 From: Konstantin Osipov Message-ID: <20191017073532.GB17235@atlas> References: <440986cab2ecc229ff8cb5bc89486737ea44d93a.1571068485.git.kshcherbatov@tarantool.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <440986cab2ecc229ff8cb5bc89486737ea44d93a.1571068485.git.kshcherbatov@tarantool.org> Subject: Re: [Tarantool-patches] [PATCH v1 3/9] box: introduce trigger_event_manipulation enum List-Id: Tarantool development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Kirill Shcherbatov Cc: tarantool-patches@freelists.org, tarantool-patches@dev.tarantool.org * Kirill Shcherbatov [19/10/14 19:06]: > This patch introduces a new trigger_event_manipulation enum > that describes a trigger event. This is the type of operation on > the associated space for which the trigger activates. > The value could be `INSERT` (a row was inserted), `DELETE` > (a row was deleted), or `UPDATE` (a row was modified). This is sql_trigger_event if we talk about SQL triggers only, or box_trigger_event if we talk about any kind of database trigger. Similarly, if we talk about sql_triggers only, it's sql_trigger_def. If you wish to define a general-purpose trigger object, for SQL and Lua, it's box_trigger_def. -- Konstantin Osipov, Moscow, Russia