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

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

Adam,

Yes, so you are suggesting creating an org.exist.xquery.modules.oracle
package with an ExecuteFunction class that uses the sql package where
possible? This sounds like a good approach, although it does create a
dependency between the modules. If you don't see this as a problem then
I would be happy to put it together as I already have the working code.

Cheers
Rob

> -----Original Message-----
> From: Adam Retter [mailto:ad...@ex...] 
> Sent: 22 March 2010 13:22
> To: Walpole, Robert
> Cc: eXist development; tin...@gm...
> Subject: Re: [Exist-development] Prepared Statements in the SQL Module
> 
> Hi Rob,
> 
> Nice to hear from you :-)
> 
> So my old foe the Oracle Cursor is back again! But seriously, 
> if I understand you correctly, then there is no reason not to 
> have an oracle extension module as part of eXist, this could 
> work in cooperation with the sql module, something like this perhaps -
> 
> for $item in oracle:execute(sql:get-connection(...), $sql) return
> $item/sql:column1
> 
> We would not be able to ship the ojdbc.jar with eXist by 
> default, but then that is the same as for the SQL module. We 
> currently do not ship any vendors JDBC implementations, we 
> expect users to place their vendors JDBC implementation in 
> lib/user (e.g. ojdbc.jar if your an Oracle user).
> 
> Erm, did that make any sense?
> 
> Cheers Adam.
> 
> On 22 March 2010 12:54, Walpole, Robert 
> <rob...@me...> wrote:
> > 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&#174; 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
> >>
> >
> 
> 
> 
> --
> Adam Retter
> 
> eXist Developer
> { United Kingdom }
> ad...@ex...
> irc://irc.freenode.net/existdb
>