On Thu, Feb 17, 2005 21:16:45 PM +0100, Verena RuffI am not sure where the problem was with this approach (I just followed the discussion on the list, I wasn't in the process), but it has been discussed wildly and there have been some more issues. Perhaps you find some more information here:
([EMAIL PROTECTED]) wrote:Hi,
AFAIK one of the main problems was that database documents should be XML based documents like the ones of writer, calc, ... This means the database needs to write its binary data within the document structure and never at the end of it (because there will always be at least the closing XML Tag of the root element). SQLite needs to append data at the end of a document and changing this behavior would have been too much to realize it in the short timeframe for developing the base application.I still don't see any _technical_merits that favor HSQLDB over SQLite. More to the point, there are technical reasons to use SQLite.
Er... probably is a stupid question, but what would/did prevent "database documents" from being zip archives just like OOWriter/OOCalc etc... containing:
one really XML _file_ with all the tags wherever they want to be one normal SQLite _file_/database, just when you use SQLite from the command line other auxiliary stuff?
In other words, why is the particular SQLite behavior you mention
above a problem for embedding it in OO.o?
http://dba.openoffice.org/servlets/ReadMsg?list=users&msgId=1424882
http://dba.openoffice.org/servlets/ReadMsg?list=users&msgId=1428064
regards, Verena
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
