Josh Berkus wrote:
Hi Josh,
"What would it take to get OOo to switch from HSQLDB to JavaDB?"
Significant assistance from the Sun Derby team, including migration and tools,
is not at all out of the question. So what are the reasons not to switch?
What's the costs?
Well that is what we would say in French is a "pavé dans la mare", or a
"brick in the millpond" for wont of a better expression.
Funnily enough, your very question was asked I guess about 18 months ago
on this same list, but of course at the time Sun wasn't, or had only
just, become involved in Derby/Apache (I don't remember the exact dates,
just that someone on this list came up with that question).
Not that I can speak for Frank, but personally this question comes as no
surprise to me (and I doubt that it does to Frank either, it was just a
matter of time before it came up). To be honest, I am neutral when it
comes to selecting any particular Java based db solution, since I still
believe that making OOo more and more Java dependent for what I consider
to be core functionality is not the way to go, but that is a whole
different discussion which we've had out here and elsewhere before, so
I'll not go into that again ;-)
The question is : does/can OOo support another Java based db all-in-one
file solution, since that is what I believe Derby is alleged to be. If
the resources are there, why not ? Personally, I'd rather see them
allocated elsewhere (SQLite anybody ?, mysql all-in-one ?), but then
hey, I still haven't been weened off MySQL yet ;-)
Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
