On 03/27/2013 04:57 PM, Kay Schenk wrote:
Well Derby does seem to be "embed-able ". See:
http://db.apache.org/derby/papers/DerbyTut/embedded_intro.html
This has been suggested before, as early as 2006. See:
http://markmail.org/message/kp5n2d5yzhprgpjm
Still, is any embedded DB a good thing? Pros and cons...
PRO:
* Very convenient for small things. Imagine if I said that you can write
a document in Write, but you must first install an external application
that Write will connect to. This is rather daunting for new users. Also,
most external systems I expect probably use multiple files, so, if I
want to simply create something small and send it to you, well, I can't
do that easily unless I zip up a directory, send it to you, and then
expect you to install the same DB that I used and then make it work.
So, it boils down to an ability to create a small single file DB.
CON:
* Our current Embedded DB works poorly with large DB, and someone who
does not know better may try to create a very large DB and have
performance issues.
If it is not reliable, then it is probably better to not exist.
--
Andrew Pitonyak
My Macro Document: http://www.pitonyak.org/AndrewMacro.odt
Info: http://www.pitonyak.org/oo.php
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
