[Tarantool-patches] [tarantool-patches] [PATCH v1 0/9] schema: rework _trigger space

[Nikita Pettik]

On 16 Oct 15:53, Konstantin Osipov wrote:
> * Nikita Pettik <korablev at 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