xml-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henning von Bargen <H.vonBar...@triestram-partner.de>
Subject AW: [vote] A native XML database project under Apache
Date Fri, 19 Oct 2001 06:56:46 GMT
+1 from me (but I'm not a committer).
It is something we all need.

But besides discussing a name for it,
it should be clarified what the project goals are.

For example:

Do we want a 100% pure Java solution?
 I like Java, but I like the Apache HTTP Server as well.
 Maybe some low-level routines (caching, I/O, Parsing) could be 
 implemented in C using the existing Apache framework including SSL
 for the sake of performance.
 Using the existing Apache C framework could have some benefits.
 Roughly spoken, a database server is not too different from a web server:
 It receives requests from many clients and services them.
 The communication between clients and server needs to be secure.
 The main difference is:
 A web server usually returns a file from the file system to answer a
 whereas a database server reads and manipulates the database storage

Do we want the database to have all the features that 
full blown-up database servers like (just for example) Oracle 9i have:
- transactions
- automatic recovery after crashes
- clustering with cache sharing
or do we just want (to keep it simple) 
only a single-process database running on a single server
with no transactions and no recovery options?

I am am not an expert, but the part that seems to 
be most interesting (and difficult) for XML databases
is effective storage and indexing.
I expect several new ideas to come up in that topic in the next few years.
Thus, the database should be quite flexible in the implementation
of storage and indexing.


> -----Urspr√ľngliche Nachricht-----
> Von:	Stefano Mazzocchi [SMTP:stefano@apache.org]
> Gesendet am:	Donnerstag, 18. Oktober 2001 21:53
> An:	Apache XML; Kimbro Staken
> Betreff:	[vote] A native XML database project under Apache
> Hi,
> while the world of native XML databases is full of marketing hype and
> promises, it is evident (for all those who tried) that mapping general
> XML schemas to relational databases can be sometimes very painful and
> not very efficient.
> In fact, it is widely recognized from the database research community
> that while well structured can be easily and efficiently mapped to a
> relational database, less structured (often called semi-structured) data
> is much more difficult to map.
> Don't get me wrong: there are a number of way to store XML in a database
> to add ACID properties to XML documents, but while this is a
> straightforward process for very repeatitive and well structured schemas
> (invoices, stock quotes, money transactions), it is not so for
> semi-structured schemas such as DocBook, SVG or even XSLT.
> Please, place your vote.
> Thanks.
> Stefano.

In case of troubles, e-mail:     webmaster@xml.apache.org
To unsubscribe, e-mail:          general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org

View raw message