<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>
</head>
<body>
<p style="margin: 0;">
<span>
<span></span>
</span>
</p>
<p style="margin: 0px;"> </p>
<div style="margin: 5px 0px 5px 0px;">
<br/>
"Santiago A." <svaa@ciberpiula.net> hat am 17. November 2011 um 11:55 geschrieben:
<br/>
<br/>
>[...]
<br/>
> Sure that for small amount of data and single user (e.g. configuration
<br/>
> files), XML is a good option.
</div>
<p style="margin: 0px;"> </p>
<p style="margin: 0px;">XML was invented to markup texts. Later programmers noticed that it is also nice for config files.</p>
<p style="margin: 0px;">A few hundred MB of XML does not sound much compared to some big SQL databases. But because it is "not that much" we want to search them in real time (multiple queries taking less than half a second). That is not a trivial task, not in a XML database, nor in a SQL database.</p>
<p style="margin: 0px;"> </p>
<p style="margin: 0px;">Another important point is, that our data is hierarchical, has lots of optional elements and attributes, the data model changes often and the data is inconsistent. Using a SQL database for that would be stupid. </p>
<p> </p>
<p>After a year of programming with hierarchical structures I came to the conclusion, that hierarchical databases are greatly underestimated. If your SQL tables are not filled dense and/or if you have a lot of parent-child relationships you should try them out. </p>
<p> </p>
<p> </p>
<p>Mattias</p>
<p> </p>
<p> </p>
</body>
</html>