On Thu, Jan 22, 2015 at 5:16 PM, ILM <[email protected]> wrote:
>
> 1/ Not having to have the Trigger class on the server classpath
That doesn't make any sense - the function you call and the object it
returns still needs to be on the server classpath.
>
> 2/ Allowing to pass parameters, e.g. you create once a trigger class to
> update a last modified field and each table can have a different name for
> this field
> AS $$ org.h2.api.Trigger create(){ return new
> LastModifiedTrigger("MODIFICATION_DATE"); } $$
> for one table and
> AS $$ org.h2.api.Trigger create(){ return new
> LastModifiedTrigger("LAST_MOD_TIME"); } $$
> for another
>
OK, I can see the benefit of this.
Perhaps we make it even more convenient and make the construction look like:
AS $$ myclass.CreateLastModifiedTrigger("MODIFICATION_DATE"); $$
where H2 will assume that the code is a call to a method that returns
an org.h2.api.Trigger object.
Regards, Noel
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.
