Steffen Goeldner wrote:
Fabian wrote:
is it of any use to you to know that XML:DB (a Java based XML kind of JDBC driver) is based on JDBC, and that for that I had to make MonetDB/XQuery able to talk with the JDBC driver? I made this JDBC/XQuery 'marriage' by letting the XQuery server produce SQL-ish results including all of its headers that are required. As such for each XQuery query a single ResultSet is returned with one column (varchar of course) holding the XQuery output. The number of rows is equal to the number of Resources in the XQuery Result.
Well, I'm sure a DBI/XQuery 'marriage' is possible too. (After all, there flows some text between client and server - it's not rocket science.) Further, I predict only minor changes are necessary. However, DBI is somewhat SQL biased (i.e. table-oriented) - thus I doubt that we'll celebrate a golden wedding. BTW: I'm not very enthusiastic about the DBI/MIL 'marriage' too. I support it because it was already there. A separate perl module, more in the spirit of MIL, may be more convenient. (Is it true that you plan a MIL successor? It may be wiser to delay my musing until then ...) There is (a lot of) work in progress... but could you give a hint towards your ideas of an 'ideal' world? Would you opt for a direct linkage of the kernel routines with a Perl wrapper?
regards, Martin
Steffen
------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users