Murray Altheim wrote:
So am I understand right that <movie> will become a row (in relational database therms) and each subtag (title, directors, ...) a column? Or am I bound to relational model too much?
To answer your last question: yes. Xindice will allow you to store the entire document as a "record" in the database. You can then build indices or further processes into the application. The advantage is that the content is stored *as XML*, i.e., not just as a text string. All of the documents are stored in collections, and all of the collections in one root collection, and that root collection is *one big document*.
Thanks, Murray. I thought that Xindice is a (some kind of) replacement for database, where one can walk along XML files like he did with relational database (SELECTs, INSERTs, DELETEs etc., but now with XPath language). But is some persistent storage like database still needed?
May be XQuery implementation will be more useful in this case.
I'm not sure why you ask this question. Xindice *is* a persistent storage, a database for XML documents. You can select, insert and delete XML files as if they were records. You can alter them using XUpdate (without replacing them entirely). There is already XPath support for various functions built into XIndice, and there are plans to add support for full text searching via Lucene.
Murray
...................................................................... Murray Altheim http://kmi.open.ac.uk/people/murray/ Knowledge Media Institute The Open University, Milton Keynes, Bucks, MK7 6AA, UK .
The Resume of George W. Bush http://www.buzzflash.com/contributors/03/04/23_resume.html
The sleep of reason brings forth monsters -- Goya
