On 07.12.20 22:35, Jörg Schmidt wrote:
-----Original Message-----
From: Jim Jagielski [mailto:j...@jagunet.com]
Sent: Monday, December 07, 2020 10:11 PM
To: dev
Subject: Re: [discussion] future embedded DB in AOO
I agree that eating our own dogfood and using Derby would be
the "better" path to take; plus it is relatively small while
at the same time being quite powerful and compliant.
As already written: I don't know both systems and I only made my statement
based on the information I found on Wikipedia.
If Mechtilde (and others) have real experience with one of the two databases,
this would have more weight.
Maybe one more thing: Is the problem database even important?
We cannot build with Java 11 and up. Decisions have to be made soon.
Strategy has to be setup. A Roadmap would be great
LO, for example, has much more manpower than we do, and yet Firebird in LO
still seems to me to be a construction site, because actually everyone advises
me to stay with HSQLDB (as far as an embedded DB is concerned).
More Manpower does not mean they invest it into Base. So I would not
judge on our strength or weakness.
AOO should avoid getting into the same situation, because invested work that
ultimately creates no benefit for the user is badly invested.
That statement is true but incomplete. We need to take into account how
much work it is for us to maintain an embedded DB. The DB eats our
resources. A good choice can make a difference in the future.
Yes, it is a very soft argument to warn not to start at all, because you are
afraid, that you can not make it.
But many other questions seem to me to be more urgent, e.g. the currently
detected problems with Big Sur (maybe other MacOS versions?)
Well, there are always more important topics. I want to take some time,
develop some strategy Maybe a roadmap. Maybe it is a good Idea to check
the options a bit. Maybe even to have something to talk about on next
FOSDEM.
We have a Room and a Deadline and no talks yet. :)
I just want to know how everyone feels on this topic, since we need to
make a decision someday.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org