[tarantool-patches] Re: [PATCH v1 0/9] schema: rework _trigger space
Konstantin Osipov
kostja.osipov at gmail.com
Wed Oct 16 08:58:11 MSK 2019
* Konstantin Osipov <kostja.osipov at gmail.com> [19/10/16 08:57]:
> * Nikita Pettik <korablev at tarantool.org> [19/10/16 08:45]:
> > Personally I've already said (see [dev] [rfc] Persistent triggers in Tarantool
> > thread) that I do not support idea of storing both Lua and SQL trigger's
> > metadata in one space.
>
> Well, we can not reach the point not only because we have
> different opinions, but because the discussion is so slow.
>
> The reason to store all persistent objects of the same type in the
> same space is that Tarantool is designed as a multiple frontend
> system. I.e. tomorrow there may be another front end, not just Lua
> or SQL, and one doesn't want to have a separate table for each
> front end.
>
> If the trigger timing, action type, definer, setuid and other
> semantics is the same, and only the language is different, then
> why duplicate the space? Whenever we add a new property common to
> all triggers (e.g. persist enabled/disabled), we'll have to do
> extra work.
Having said that, I should note that I mentioned earlier that I
don't think this feature is a high priority work.
--
Konstantin Osipov, Moscow, Russia
More information about the Tarantool-patches
mailing list