issue: ad_changelog is loaded in PO, that comes since compiere - the most probable reason is because of defaults in the database, or more uncommon triggers that change the values when being inserted
so, after inserting the record is re-read from DB to take the values assigned there
my suggestion for the asker was that for frequently inserted log tables we could use JDBC insert instead of PO - the PO class has a big overhead as it looks for translations, trees, workflows, foreign keys, etc
maybe AD_ChangeLog is a candidate for such suggestion - use direct INSERT instead of PO
Major
https://mattermost.idempiere.org/idempiere/pl/rqe8dwtsspdpddnbbs3cdjhbey
discussion highlight:
issue: ad_changelog is loaded in PO, that comes since compiere - the most probable reason is because of defaults in the database, or more uncommon triggers that change the values when being inserted
so, after inserting the record is re-read from DB to take the values assigned there
my suggestion for the asker was that for frequently inserted log tables we could use JDBC insert instead of PO - the PO class has a big overhead as it looks for translations, trees, workflows, foreign keys, etc
maybe AD_ChangeLog is a candidate for such suggestion - use direct INSERT instead of PO