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

[Andrzej J. T. <an...@ch...>]

Adam replied to Rob:

> 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).

This sounds like a perfect instance justifying having an external extensions mechanism/repository/wiki (same thing for
GATE, IMO).

That way anyone (not just committers) could create and post useful extensions and all you would have to do is check
prerequisites (eg. eXist version), download jars and add a few lines to conf.xml.

No need to keep these extensions in the eXist SVN, and many good reasons to keep them out of it.

-- 
Andrzej Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com