Hello Jacques,
There were two errors/issues in your last email.
1) I have fixed the issue related to column name MARITAL_STATUS_ENUM_ID.
Here is my commit for the same(Please see the commit message where I shared
additional details):
https://github.com/apache/ofbiz-framework/commit/223d09f0ef49a0becdd4bc57760de9b432c2843a
If you are depreciating a field, then you need to follow a rule that says:
Use the col-name value the same as the field's name, which was previously in
use. And I think the database keeps the col-name attribute value as is.
- If you give col-name value in small letters, then it will be stored in small
letters.
- If you give col-name value in capital letters,then it will be stored in
capital letters.
In the year 2009/2010, I got a chance to work on a project where I got to learn
this concept.
There is a Jira issue where this issue was discussed:
https://issues.apache.org/jira/browse/OFBIZ-13329?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel&focusedCommentId=18047281
<https://issues.apache.org/jira/browse/OFBIZ-13329?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel&focusedCommentId=18047281>
Here is the commit notification where the use of "maritalStatusEnumId" was
removed:
https://github.com/apache/ofbiz-framework/commit/109c496e65
2) We are still seeing the following messages on the console. I didn't get a
chance to look into it:
2026-05-17 23:51:35,252 |OFBiz-batch-2 |DatabaseUtil |I|
Getting Column Info From Database
2026-05-17 23:51:35,252 |OFBiz-batch-1 |DatabaseUtil |I| Error getting primary key info from database with null tableName, will
try other means: org.h2.jdbc.JdbcSQLDataException: Invalid value "null" for parameter "table" [90008-240]
2026-05-17 23:51:35,252 |OFBiz-batch-1 |DatabaseUtil |I|
Searching in 7 tables for primary key fields ...
2026-05-17 23:51:35,252 |OFBiz-batch-1 |DatabaseUtil |I|
Reviewed 9 primary key fields from database.
2026-05-17 23:51:35,253 |OFBiz-batch-3 |DatabaseUtil |I| Error getting primary key info from database with null tableName, will
try other means: org.h2.jdbc.JdbcSQLDataException: Invalid value "null" for parameter "table" [90008-240]
2026-05-17 23:51:35,253 |OFBiz-batch-3 |DatabaseUtil |I|
Searching in 6 tables for primary key fields ...
2026-05-17 23:51:35,253 |OFBiz-batch-3 |DatabaseUtil |I|
Reviewed 8 primary key fields from database.
2026-05-17 23:51:35,268 |OFBiz-batch-2 |DatabaseUtil |I| Error getting primary key info from database with null tableName, will
try other means: org.h2.jdbc.JdbcSQLDataException: Invalid value "null" for parameter "table" [90008-240]
2026-05-17 23:51:35,268 |OFBiz-batch-2 |DatabaseUtil |I|
Searching in 870 tables for primary key fields ...
2026-05-17 23:51:35,274 |OFBiz-batch-2 |DatabaseUtil |I|
Reviewed 1697 primary key fields from database.
--
Kind Regards,
Ashish Vijaywargiya
Vice President of Operations
*HotWax Systems*
/Enterprise open source experts/
http://www.hotwaxsystems.com
On Sun, May 17, 2026 at 2:57 PM Jacques Le Roux via dev <[email protected]>
wrote:
Thanks Ashish,
This issue is resolved with a manner I did not know, great.
There is now only this error, not related to H2 IIRW.
2026-05-17 11:17:06,181 |OFBiz-batch-2 |DatabaseUtil |I|
[addColumn] sql failed, trying sql2=ALTER TABLE OFBIZ.PERSON ADD COLUMN
marital_satus_enum_id VARCHAR(20)
2026-05-17 11:17:06,185 |OFBiz-batch-2 |DatabaseUtil |E| Could not add column [marital_satus_enum_id] to table [OFBIZ.PERSON]:
SQL
Exception while executing the following:
ALTER TABLE OFBIZ.PERSON ADD marital_satus_enum_id VARCHAR(20)
Error was: org.h2.jdbc.JdbcSQLSyntaxErrorException: Duplicate column name
"MARITAL_SATUS_ENUM_ID"; SQL statement:
ALTER TABLE OFBIZ.PERSON ADD COLUMN marital_satus_enum_id VARCHAR(20)
[42121-240]
Tmrw I'll check the rest, more for me to get used to H2 in log :)
Jacques
Le 17/05/2026 à 11:03, Ashish Vijaywargiya a écrit :
> Hello Jacques,
>
> Thank you for reporting. I have fixed those errors/warnings in the below
commit:
>
>
https://github.com/apache/ofbiz-framework/commit/2bcbf32a7f4a45a408b858b852eb5ccc3f72746b
>
> --
> Kind Regards,
> Ashish Vijaywargiya
> Vice President of Operations
> *HotWax Systems*
> /Enterprise open source experts/
> http://www.hotwaxsystems.com
>
>
>
> On Sun, May 17, 2026 at 12:37 AM Jacques Le Roux via dev
<[email protected]> wrote:
>
> Hi,
>
> We have just trivial names conflicts in log when loading all with an
existing H2 DB, like at least:
> Column [ROOT_LOCATION] of table [TENANT.COMPONENT] of entity
[Component] is of type [CHARACTER VARYING] in the database, but is defined as
type
> [VARCHAR] in the entity definition.
> Column [INTERNAL_NOTE] of table [OFBIZ.WORK_EFFORT_NOTE] of entity
[WorkEffortNote] is of type [CHARACTER] in the database, but is defined
as type
> [CHAR] in the entity definition.
>
> Trivial, because that has no incidence on operations. Simple global
changes should do it. As it's mostly those kinds above (9134 lines at
all),
> changing them should show others if they exist.
>
> Have a good weekend
>
> Jacques
>
> Le 16/05/2026 à 17:25, Jacques Le Roux via dev a écrit :
> > Hi Ashish,
> >
> > I made an integration on Win7. It's quicker than Derby and
successful.
> >
> > Same on Ubuntu (22 min vs 32): https://ci2.apache.org/#/builders/46
> >
> > Thanks
> >
> > Jacques
> >
> > Le 16/05/2026 à 15:50, Ashish Vijaywargiya a écrit :
> >> Dear All,
> >>
> >> There were no objections from community members to moving with the
> >> H2 database.
> >> https://www.h2database.com/html/main.html
> >>
> >> I implemented the H2 database support and removed the Apache Derby
from the
> >> ofbiz trunk code.
> >>
> >> Here is my commit for your kind reference:
> >>
https://github.com/apache/ofbiz-framework/commit/8306e7a10592ff93defb26d0ddaa8e0a4dbb8595
> >>
> >> For historical purposes, I also created a JIRA ticket as well:
> >> https://issues.apache.org/jira/browse/OFBIZ-13412
> >>
> >> ./gradlew cleanAll loadAll is working fine.
> >>
> >> ./gradlew ofbiz is working fine.
> >>
> >> After the changes, I placed and completed a sales order. And then
created a
> >> customer in the ofbiz backend.
> >>
> >> Everything seems to be working fine with the H2 database.
> >>
> >> I will keep a close eye on the ofbiz mailing list and Jira for
H2-related
> >> issues.
> >> If someone reports issues with the H2 database, we can fix them.
> >>
> >> Thank you.
> >>
> >> --
> >> Kind Regards,
> >> Ashish Vijaywargiya
> >> Vice President of Operations
> >> *HotWax Systems*
> >> *Enterprise open source experts*
> >> http://www.hotwaxsystems.com
> >>
> >>
> >>
> >> On Sun, May 10, 2026 at 11:01 AM Ashish Vijaywargiya <
> >> [email protected]> wrote:
> >>
> >>>>> For that reason, I think we should consider replacing Derby
with another
> >>> embedded database for OFBiz’s out-of-the-box/demo setup.
> >>>
> >>> Hello All,
> >>>
> >>> I agree that we should consider replacing the Derby database with
another
> >>> embedded database.
> >>>
> >>> I also agree that H2 appears to be the best option at the current
time.
> >>>
> >>> I went ahead and replaced Apache Derby in my OFBiz trunk codebase
with the
> >>> H2 database.
> >>> After the changes, I tested the ofbiz code base on H2 db by
placing an
> >>> Order, completing it, and also created a new customer. These
operations
> >>> are working fine for me.
> >>>
> >>> I have pushed the H2-specific modified code to a branch in my
forked
> >>> repository. Please take a look at the code below and let me know
your
> >>> thoughts.
> >>>
> >>>
> >>>
https://github.com/ashishvijaywargiya/ofbiz-framework/tree/default-h2-db-support-ofbiz-trunk
> >>>
> >>> If there are no objections, I will create a PR sometime next week
to merge
> >>> the code into the OFBiz project.
> >>>
> >>> Thank you.
> >>>
> >>> --
> >>> Kind Regards,
> >>> Ashish Vijaywargiya
> >>> Vice President of Operations
> >>> *HotWax Systems*
> >>> *Enterprise open source experts*
> >>> http://www.hotwaxsystems.com
> >>>
> >>>
> >>> On Thu, May 7, 2026 at 1:20 PM Jacopo Cappellato <
> >>> [email protected]> wrote:
> >>>
> >>>> Hi all,
> >>>>
> >>>> Since Apache Derby is now retired, it will no longer receive
updates for
> >>>> bug fixes or security issues.
> >>>> For that reason, I think we should consider replacing Derby with
another
> >>>> embedded database for OFBiz’s out-of-the-box/demo setup.
> >>>>
> >>>> Would anyone be willing to volunteer in either of these areas?
> >>>> * researching and suggesting suitable alternative products that
would fit
> >>>> OFBiz well;
> >>>> * implementing the switch once we agree on a direction.
> >>>>
> >>>> As an alternative, we could also consider no longer shipping a
bundled
> >>>> database at all, and instead relying on Docker images to make
demo
> >>>> instances easy to start.
> >>>> That would be a more significant change for users, so perhaps not
> >>>> something
> >>>> for immediate adoption, but I think it is probably the right
direction to
> >>>> keep in mind for the future.
> >>>>
> >>>> Thoughts?
> >>>>
> >>>> Best,
> >>>> Jacopo
> >>>>
> >>>>
> >>>> On Thu, Dec 4, 2025 at 9:43 AM Jacques Le Roux <
> >>>> [email protected]>
> >>>> wrote:
> >>>>
> >>>>> Hi,
> >>>>>
> >>>>> FYI, not a problem IMO. It works as is.
> >>>>>
> >>>>> Jacques
> >>>>>
> >>>>>
> >>>>>
> >>>>> -------- Message transféré --------
> >>>>> Sujet : Apache Derby is now retired
> >>>>> Date : Wed, 3 Dec 2025 09:38:15 -0800
> >>>>> De : Richard Hillegas <[email protected]>
> >>>>> Répondre à : [email protected]
> >>>>> Pour : [email protected]
> >>>>>
> >>>>>
> >>>>>
> >>>>> The DB PMC announces the retirement of its Derby sub-project,
due to
> >>>>> prolonged low activity. Derby is a small-footprint, pure-Java
relational
> >>>>> database. Derby runs embedded in a local application as well as
> >>>>> client-server over a network. Databases can live on disk or in
memory.
> >>>>> Existing,
> >>>>> official versions support JVMs from Java 1.3 up through Java
21. The
> >>>>> development mainline builds and tests cleanly on Java 25.
> >>>>>
> >>>>> The project's resources remain available in a read-only state.
This
> >>>>> includes the website (https://db.apache.org/derby/), mailing
lists,
> >>>> wiki
> >>>>> (https://cwiki.apache.org/confluence/display/DERBY/FrontPage),
> >>>> Subversion
> >>>>> repository, and JIRA bug tracker. Official distributions remain
> >>>> available
> >>>>> on
> >>>>> an as-is basis at
https://db.apache.org/derby/derby_downloads.html.
> >>>>>
>
