Re: [Exist-development] Prepared Statements in the SQL Module

[Walpole, R. <rob...@me...>]

Adam,

Nice work! I also wrote a function for executing prepared statements a
while ago, however I never commited it to the eXist codebase as my
requirment was to get the ResultSet from an OracleType.CURSOR. In order
to do this I had to import oracle.jdbc.OracleTypes and this obviously
has licening issues which would appear to complicate things. Is this a
no-no as far as eXist is concerned? I would be interested to know your
thoughts on this.

Cheers
Rob

Rob Walpole
Email: rob...@me...
Website: www.metoffice.gov.uk 

> -----Original Message-----
> From: Adam Retter [mailto:ad...@ex...] 
> Sent: 19 March 2010 11:34
> To: eXist development
> Cc: tin...@gm...
> Subject: [Exist-development] Prepared Statements in the SQL Module
> 
> Upon request I have added support for Prepared Statements to 
> the SQL Module, there is a new function call sql:prepare(...).
> 
> This has gone into trunk as revision 11478. Mark Lawson has 
> kindly offered to test this functionality, if anyone else 
> makes use of the SQL Module and wishes to use Prepared 
> Statements then I would also encourage their testing. I am 
> looking forward to feedback :-)
> 
> Just like the Connections all PreparedStatements are cleaned 
> up at the end of the XQuery execution.
> 
> --
> Adam Retter
> 
> eXist Developer
> { United Kingdom }
> ad...@ex...
> irc://irc.freenode.net/existdb
> 
> --------------------------------------------------------------
> ----------------
> Download Intel® Parallel Studio Eval Try the new 
> software tools for yourself. Speed compiling, find bugs 
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>