Analyze how tables such AccountEntry_x_ID or User_x_ID are can affect DB Partition

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 7.4.13 DXP U34, Master
• Fix Version/s: 7.0.X, 7.1.X, 7.2.X, 7.3.X, 7.4.13 DXP U47, 7.4.3.47 CE GA47, Master
• Component/s: Database Partitioning
• Labels:
  • 7.4-known-issues
  • 7.4.13-u47
  • FCBARCELONAWEB
  • backend_test
  • fc_22_08
  • fc_22_09
  • fc_22_10
  • liferay-ga39-ce-743-known-issues
  • liferay-ga40-ce-743-known-issues
  • liferay-ga41-ce-743-known-issues
  • liferay-ga42-ce-743-known-issues
  • liferay-ga43-ce-743-known-issues
  • liferay-ga44-ce-743-known-issues
  • liferay-ga45-ce-743-known-issues
  • liferay-ga46-ce-743-known-issues
  • liferay-ga48-ce-743-known-issues
  • pt-app-security-review
• Branch Version/s:
  7.3.x, 7.2.x, 7.1.x, 7.0.x
• Backported to Branch:
  Committed
• Fix Priority: 5
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/124366
• Bug Type: Database Upgrade

It seems that iin the method com.liferay.object.model.impl.ObjectDefinitionImpl#getExtensionDBTableName we are regerating tables like:

• AccountEntry_x_20098
• User_x_20098

We should analyze how these tables are created and see if they impact the DB Partition feature