Fabian wrote:
Steffen Goeldner wrote:
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.
I was just trying to point out that XQuery already can give you SQL-ish output, so the only thing you have to do is make sure you don't send the wrong (auto) commands, such as auto-commit, and all of your tabular/resultset based routines should be happy. I mapped XQuery's Results on SQL's ResultSets, and XQuery's Resources on SQL's Rows.
Understood. I just removed the restriction for the language parameter in DBD::monetdb. The AutoCommit handler calls 'set auto_commit = ...' only for SQL. The commit()/rollback() methods call commit/rollback for SQL, commit();/abort(); otherwise. It may be better to call the latter only for MIL and nothing otherwise. Opinions? Steffen