Re: Idea of using hsql as cache, how do you think about that?

Well... not much, just usually we will extract SQL, especialy DDL, to
separate db script file. I feel a bit of confusion about where to put
the HSQL trigger is call Java method, just minor source code
organization concern.


On 12/5/07, Simpson, Blaine A (Contractor)
<blaine_a_simpson@xxxxxxxxxxxxx> wrote:
> And the advantage you anticipate from using the HSQLDB API instead of coding 
> some simple JDBC to accomplish the same exact thing at the same exact code 
> location is... ?
>
>
> -----Original Message-----
> From: hsqldb-user-bounces@xxxxxxxxxxxxxxxxxxxxx on behalf of Carfield Yim
> Sent: Tue 2007-12-04 13:33
> To: HSQLdb user discussions
> Subject: Re: [Hsqldb-user] Idea of using hsql as cache,how do you think about 
> that?
>
> > As you saw in chapter 9, the trigger is created with SQL.  You'll have to 
> > decide where you want to put your SQL and when you want it to execute.  If 
> > you don't know how to embed SQL in Java, I think you should stick to non-DB 
> > solution until you get more experience with JDBC.
> >
>
> I know how to run SQL in Java... but what I wondering is can I add
> trigger using API call instead...
>
> -------------------------------------------------------------------------
> SF.Net email is sponsored by: The Future of Linux Business White Paper
> from Novell.  From the desktop to the data center, Linux is going
> mainstream.  Let it simplify your IT future.
> http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
> _______________________________________________
> Hsqldb-user mailing list
> Hsqldb-user@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/hsqldb-user
>
>
>

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4