Please see my responses inline...
Regards,
Michael Brohl
ecomify GmbH - www.ecomify.de
Am 07.03.22 um 18:44 schrieb Development:
So let me try to summarize your response:
#1. The only reason to *keep* derby that you see is that we disagree on the relative difficultly of
getting a "simple build and run" going using docker vs the difficulty of using the
traditional "install java and follow the current instructions" way
#2. You'd like me to start going through the list of all the issues that I
expect will end up as a derby constraint.
Is that correct?
I don't think I have said anything like that.
What I said was that it is not necessary to drop Derby support to
provide the additional option for a Docker image.
* Perhaps we are differing in how difficult we believe it is to install
docker. I have not used docker on windows. Is docker difficult to install on
windows?
I am not using Windows so I cannot tell. I'm using Docker on Mac.
As you can see in https://issues.apache.org/jira/browse/OFBIZ-10407 , I
have provided a Docker image to be used so I'm familiar with Docker and
see it as a good additional way to provide a demo system for interested
users.
I just don't see the necessity to drop Derby support and exclude those
people who do not want to use Docker (for whatever reason) or need the
current OOTB behaviour.
As for my first issue that I expect will end up as a derby constraint, I'll
start with my most recent issue that I run into regularly:
Before that, I should mention that I don't actually use derby so may be blaming some things are derby that are undue,
by misunderstanding some of its abilities. So I'll state it as a question. It that relates to the table names being
mangled. For example: searching the list of tables on "employ" (to match either "employee" or
"employment") misses the tables containing employee position because is is called "empl_position".
So my question is: are table names mangled like that because we have the
convention that index and constraint names include the tablename as a prefix,
and that not mangling the names would have exceeded a derby limit on number of
characters in a name?
I do not know exactly why each table has his name. But in your example,
I would simply search for "empl" and would find what I need...
