> > Maybe it's necessary to go and knock on other XML database developer's
> > doors to ask them to provide an implementation of XML:DB. It was quite
> > impressive how little time it took me to create an XML:DB layer on top
> > of JDBC.
> 
> Is the code/binary for this impl something you can make available? No big 
> deal if not, but I know several people would be interested.

I'd be glad to share it. I'll have to ask my employer, but I can't give
an immediate answer. Holidays, you know. 

> > That's what I'd like to see. And I'm sure that it doesn't confuse people
> > if the behaviour is clearly documented. The only problem is that some
> > implementations may not be able to provide that ID.
> >
> 
> Are you able to provide this in your JDBC impl?

I'm quite sure. I must admit, though, that I haven't finished my
XPathQueryService. That will be one of my next tasks. You may remember
my post about my SQLSelectQueryService, asking for an abstract
QueryService. I'm currently using SQL-style WHERE-statements. Very easy
to implement. :-) By the way, I'm still serious about that proposal.
It's very useful for my SQLSelectQueryService and it would be for XQuery,
I guess.

> >>
> >>> "Delete all documents created in a given date range."
> >>>
> >>> Where the XML instances have the following sample structure:
> >>> <doc created="2001-07-02">
> >>>     <data>...</data>
> >>> </doc>
> >
> > One possibility is to extend the XPathQueryService to contain a method
> > such as this:
> >
> > public interface XPathQueryService extends Service {
> >    ResourceIterator query(String query) throws XMLDBException;
> >    void remove(String query) throws XMLDBException;
> > }
> >
> 
> Would you add this along with the setting of the ID? It seems the expected 
> behavior here would be to remove the result node rather then the document.

Looking at my proposal a second time, you're right. Same problems as
with the IDs. It always comes down to detecting if the XPath statement
resolves to a root node (resource/document) or just a simple node.

So, the "remove"-method should probably be named "removeResources" (at
least, that's what I intended) and should check if the XPath statement
resolves to a root node. Oooh, I'm not happy about this. Still to
complicated. Any other ideas?

Jeremias Märki

mailto:[EMAIL PROTECTED]

OUTLINE AG
Postfach 3954 - Rhynauerstr. 15 - CH-6002 Luzern
Fon +41 (41) 317 2020 - Fax +41 (41) 317 2029
Internet http://www.outline.ch


----------------------------------------------------------------------
Post a message:         mailto:[EMAIL PROTECTED]
Unsubscribe:            mailto:[EMAIL PROTECTED]
Contact adminstrator:   mailto:[EMAIL PROTECTED]
Read archived messages: http://archive.xmldb.org/
----------------------------------------------------------------------

Reply via email to