On Friday, February 21, 2003, at 04:40 AM, George Papamarkos wrote:
Actually due to the problem of handling the deletions (you can't point into something that doesnot exist anymore) I prefer to get back as a result the part of the file that have changed (inserted or deleted). Do you believe that this is doable or not ?
It's technically doable, but I'm not sure it's a good idea in the general case. XUpdate modifications can span many documents and you could get a very large data set as a result. A better approach may be to put a hook into the update process that allows you to listen for changes to documents. Basically like the Observable stuff does on Collection. This way it doesn't affect normal operation.
Kimbro Staken
I'd appriciate you advices because I'm currently coding for my PhD and I need to take a decision as soon as possible. Your expertise would be helpful.
Thanx in advance.
George Papamarkos Research Assistant School of Computer Science and Information Systems Birkbeck College University of London. [EMAIL PROTECTED]
-----Original Message-----
From: Kimbro Staken [mailto:[EMAIL PROTECTED]
Sent: ÎÎÎÏÏÎ, 20 ÎÎÎÏÎÏÎÏÎÎÏ 2003 4:21 ÏÎ
To: [EMAIL PROTECTED]
Subject: Re: Some thoughts about changing the default behaviour of some methods.
On Tuesday, February 18, 2003, at 11:30 AM, George Papamarkos wrote:
Dear all, I am currently using Xindice as the XML Repository in my PhD research on ECA Rules for semi-structed data. I intend to create a mechanism in order to be able to see what have changed after an update. I mean for example instead of returning the number of elements that changed, the update method return exaclty what have changed or create a "pointer" to it. Does anyone have any idea of how can I achieve that ?
Do you actually want to return the data that was modified or just a list of keys to modified documents?
I am thinking of creating a framework over the Xindice API and get the
results I want by overriding the already existing methods. Do you
believe
that the use of XMLObjects would help ?
XMLObjects were cut out of 1.1.
I'd appriciate any new idea or recommendation .
Regards,
George Papamarkos Research Assistant School of Computer Science and Information Systems Birkbeck College University of London. [EMAIL PROTECTED]
Kimbro Staken Java and XML Software, Consulting and Writing http://www.xmldatabases.org/ Apache Xindice native XML database http://xml.apache.org/xindice XML:DB Initiative http://www.xmldb.org
Java and XML Software, Consulting and Writing http://www.xmldatabases.org/
Apache Xindice native XML database http://xml.apache.org/xindice
XML:DB Initiative http://www.xmldb.org
