XML as a database replacement

[avalanche333]

I am looking for an API that can work as a database replacement. Key features I am looking for in this tool include:
- Generating unique ID's when new records are added (like an IDENTITY in MS SQL Server, or Autonumber in Access)
- Ability to add, update, delete records
- Ability to retrieve records (less important as this is already very easy in XML)

Please give suggestions and links. Maybe even start a disscussion as to why you think its a good API to use.

Thanks,

 

[grande]

I'd recommend using a database, personally. XML is slooooww.

-------------------------
Matt Grande
C# Master.
Ruby on Rails Admirer.
ActionScript Student.
JavaScript Hate-Monger.

 

[JontyMC]

Why you say XML is slow? It depends on what you are doing.

There are big benefits to be had working with one data format throughout an application. With relational databases a lot of time and effort is spent mapping data to objects and then mapping those objects to something else.

In terms of database API, I love eXist(open-source native XML database). Also I love Orbeon forms.

eXist + XQuery + XSL + XForms is the way forward.

Jon

"I don't regret this, but I both rue and lament it.

 

[harebrain]

Why you say XML is slow? It depends on what you are doing.

Computer with 4MB memory + XML file of 8MB = you're screwed

 

[JontyMC]

Thats why I say its depends what you're doing. XML is not slow per se.

A good native XML database (eXist) will have similar speed to relational database and better in cases where you are returning highly structured data.

Accessing small flat XML files will also be quicker than accessing a database.

Jon

"I don't regret this, but I both rue and lament it.