Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Revisions: Issue #38297 All Revisions ] Back to Issue ]
Summary 0038297: API-Change: Removed org.openbravo.erpCommon.businessUtility.Heartbeat_data_xsql file & code revision columns
Revision 2018-04-26 13:10 by alostale
Description a.) That file xsql was only used by openbravo internal code and having it public today was no longer necessary for any code in pi.

Checking all published modules using getAllModules script did not find any module using it.

What the file did was read data only related to heartbeat & Openbravo registration from ad_system_info table which are areas not known to be customized anyway.

b.) Removal of ad_system_info.code_revision field in database, ad_column, ad_field.
Also removed related entry CODE_REVISION in SystemInfo.Item.CODE_REVISION enum.

c.) Removal of ad_module.version_id and ad_module_install.version_id

Those did save 'mercurial revision' of main repo (ignoring modules) and were only used in 'an obsolete check for local changes in export.database which was changed to a checksum long time ago' and in sending that data to Openbravo heartbeat.

Checking for them in download of all published modules did also not show any module using them.

So risk of this API change should be very low.
Revision 2018-04-09 10:33 by shuehner
Description a.) That file xsql was only used by openbravo internal code and having it public today was no longer necessary for any code in pi.

Checking all published modules using getAllModules script did not find any module using it.

What the file did was read data only related to heartbeat & Openbravo registration from ad_system_info table which are areas not known to be customized anyway.

b.) Removal of ad_system_info.code_revision field in database, ad_column, ad_field.
Also removed related entry CODE_REVISION in SystemInfo.Item.CODE_REVISION enum.

Those did save 'mercurial revision' of main repo (ignoring modules) and were only used in 'an obsolete check for local changes in export.database which was changed to a checksum long time ago' and in sending that data to Openbravo heartbeat.

Checking for them in download of all published modules did also not show any module using them.

So risk of this API change should be very low.
Revision 2018-04-08 18:49 by shuehner
Description That file was only used by openbravo internal code and having it public today was no longer necessary for any code in pi.

Checking all published modules using getAllModules script did not find any module using it.

What the file did was read data only related to heartbeat & Openbravo registration from ad_system_info table which are areas not known to be customized anyway.


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker