Hi,

I see what you're saying. I guess all I'm offering is another way to package
the Java code that H2 already supports. You can add it to the classpath,
like you do now, or you can put it inside the database. The functionality is
essentially identical. All it really gives you is another deployment option.

Creating a whole new programming language is a little outside of the scope
of my suggestion, but as Thomas likes to say "patches are welcome" :-)

Cheers
Kerry

On Thu, Jun 24, 2010 at 6:20 PM, Brish <[email protected]> wrote:

> On Jun 23, 10:41 pm, Kerry Sainsbury <[email protected]> wrote:
> > I certainly cannot see an example of it in those links -- am I missing
> > something?
>
> No, you're not missing something.
>
> I prefer the way HSQLDB 2.0 does triggers over your suggestion of
> adding java into the database.
>
> The built in procedural language in HSQLDB 2.0 can do what your
> example does but it's simpler.
>
> For more complex scenarios both H2, and HSQLDB can use classes in .jar
> files in the classpath for the trigger. Some of the advantages of
> doing it this way are: the JIT compiler applies to the trigger code
> (performance advantage), debuggable in an IDE, can use other libraries
> in the classpath instead of being limited to H2 and java classes,
> etc..
>
> I don't think that adding a .jar file into the classpath is a big
> deal.
>
> Brish
>
> --
> You received this message because you are subscribed to the Google Groups
> "H2 Database" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<h2-database%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/h2-database?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups "H2 
Database" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/h2-database?hl=en.

Reply via email to