On Monday 04 February 2002 21:51, you wrote:
> Yes, you could. But searching becomes much harder, you need to be
> XML-aware in the body and title, before inserting to the db. Things like
> bbcode and JS escaping becomes a whole new dimension, and you're still
> using SQL rather than XPath, to select nodes.
This is why I submitted an XML db interface (optionally an XML db subproject)
for the TODO. We are doing XML. I agree, if we want to do it seriously
without squeezing it back into a simple table/relations structure, an XML db
is a must. Though never forget: there are things which RDBMS are very good
at, there are cases where it pays off to convert XML into and out of a table
structure.
> Ideally - a database, would be 1 large, compressed XML document, and the
> database engine, would be aware of values, vs elements, etc.
No, sorry. This is stupid. Your OS already has clever knowledge about how to
look up documents fast, why defeat that? Storing lots of very small fragments
is rubbish, too. Rather, I agree with the way the two OSS XML-database
projects I know do: Store medium-sized documents, each on its own, with a
sophisticated index that encompasses a complete collection of documents. This
way you can do quite fast queries (depending on indexing scheme), and still
have the power (flexibility) of XPath and/or XQL. Have a look at
xml.apache.org, one of these DBs is part of Apache XML, just like AxKit.
--
CU
Joerg
PGP Public Key at http://ich.bin.kein.hoschi.de/~trouble/public_key.asc
PGP Key fingerprint = D34F 57C4 99D8 8F16 E16E 7779 CDDC 41A4 4C48 6F94
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
