Download
There are many pros and contras to each technology and it’s highly depending on what are you gonna do with XML / SQlite.
It is not absolutely necessary to handle million rows of data to run into XML difficulties, when the data becomes 20M > size, you will start having real problems. At some point it becomes inefficient and leads to a waste of resources. I hope that you know, that the size of the data on the filesystem is a factor of 2 smaller than the in memory DOM?
Who is „no-one“? developer or the end user?
As I have already said, the end-user himself does not notice anything of this process, because the entire administration and installation runs from the script.
SQlite is probably easier to work with than XPath for most developers and I don't really think that sqlite will need more development time overhead.
It is not absolutely necessary to handle million rows of data to run into XML difficulties, when the data becomes 20M > size, you will start having real problems. At some point it becomes inefficient and leads to a waste of resources. I hope that you know, that the size of the data on the filesystem is a factor of 2 smaller than the in memory DOM?
(2016-05-16, 00:13:03)shawn_a Wrote: It is because no-one wants to deal with databases to spin up a tiny website and was designed that way
Who is „no-one“? developer or the end user?
As I have already said, the end-user himself does not notice anything of this process, because the entire administration and installation runs from the script.
SQlite is probably easier to work with than XPath for most developers and I don't really think that sqlite will need more development time overhead.
