============ 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. ============ Hello Jacques, I have fixed the above console errors/warning/informational messages. Here is the pull request for the same. https://github.com/apache/ofbiz-framework/pull/1229 If there are no objections to my pull request, then I will commit it in the next few days. I have also created a Jira ticket for the same: https://issues.apache.org/jira/browse/OFBIZ-13413 -- Kind Regards, Ashish Vijaywargiya Vice President of Operations *HotWax Systems* *Enterprise open source experts* http://www.hotwaxsystems.com On Tue, May 19, 2026 at 9:11 AM Ashish Vijaywargiya < [email protected]> wrote: > Yes, exactly. Thanks Jacques for sharing references. > > ======= > When changing the name of a field, or deprecating and replacing a field > that does not require deprecation of the entire entity, then follow the > same pattern leaving the old field there: a "old" prefix added to the field > name, change the original first letter to upper case, and specify the > column-name for the field so it is the same as the original field name. For > example if you are changing the "uomId" field to a new name then change the > field name to "oldUomId" and specify a column-name of "UOM_ID". Just as > when replacing and entity, make sure to write a service to move the data > from the old field to the new one. > ===== > > Thanks, > Ashish > > Sent from my iPhone > > On Mon, 18 May 2026 at 7:57 PM, Jacques Le Roux via dev < > [email protected]> wrote: > >> Le 18/05/2026 à 10:46, Jacques Le Roux via dev a écrit : >> > I'll copy it in the 1st link above. I'll also had your shorter and >> maybe clearer explanation, or maybe only it >> Finally I did not change anything at all. In the wiki page >> >> https://cwiki.apache.org/confluence/display/OFBIZ/Revisions+Requiring+Data+Migration+-+upgrade+ofbiz >> there is a link to >> >> https://cwiki.apache.org/confluence/display/OFBIZ/General+Entity+Overview#GeneralEntityOverview-DeprecatedEntities >> where all is detailed. Better let's thing as they are. >> >> Jacques >> >>
