XML Database

[indranilb]

I want to use a small object orientated database to store and retrieve XML files. Any ideas how? I don't want to use any SQL databases, as the distribution would have to have a transparent database layer, and the user can't go in and do any settings (ODBC, etc.). I am not really bothered about complexity, etc. Ideal languages would be C++/C.

Thanks
Indranil

[dhanam]

You may want to consider reevaluating your design.
It concerns me that you want to store the XML files and process them. XML is NOT meant to replace Database. XML is just a good format to EXCHANGE data. Nothing more, Nothing less.

You might want to use some database to store you data. When you need to pass the data to different machine, then use XML to pass the data.

[indranilb]

Let me rephrase that. I want a database where I can easily map and generate XML files. I do not wish to store XML files as is. That would be deviant to the design, as it would just be a flat file referencing system. However, I do want to map them seamlessly. From my design thus far, it would be prudent to use a OO database for this. I am specifically looking for an OO Database that would do this, and preferably is Opensource, and written in C++.

[dhanam]

Well. I don't know much about OO database.
However, exisiting RDBMS's like Oracle and SQL Server 2000 all have support for retrieving a result set in a XML form.
You can use this database's to store your data and when you need to pass this data around use SQL query to get XML and pass XML around.
Hope this helps!

[indranilb]

Thanks for your post. I really don't think a SQL based database, or any RDBMS for that matter, would provide an effective model for the generation and reverse generation of XML files. As an XML document is completely OO based, it only makes sense to use an OO database. Of course, you could always do it with an RDBMS. But would you accomplish it with the same relative ease, and direct mapping. I think not.

[dhanam]

Well.
The database schema and the XML schema does not have to be always exact. In case if your db schema and XML schema are different, any way you have to have code to generate and reverse generate XML. It's not direct any more.
Most of the time XML schema will be different from database schema, because you may pass only subset or Join couple of database and form a XML.
Everything depends on your design and I think "strongly" tying XML schema to the database schema, is NOT a good idea at all.

[indranilb]

Well, it entirely depends on what you are designing the database schema to do in the first place. If you are only designing it to contain XML data, then it should form close patterns with the actual design. It will definitely bring some amount of clarity for other programmers. I suppose a table based structure could do the same thing as well. At the end of the day, my primary concern is to use a small database, something less than 1 MB installation size, and I need quick and efficient results.

In any case, we must agree to disagree!