Database Changes After Adding Liferay Account
Created: 3 December 2024 Modified:What data changes occur when an account is added to Liferay. Added account Rock Seller. This user was added by administrator user Test Test with email test@test.com. Keep in mind that Liferay doesn’t enforce referential integrity in the database. Instead it is “enforced” in the code.
Many tables have columns classNameId and classPK. These act as a psuedo foreign key to the ClassName_ table. The ClassName_ table basically references Java classes. These Java classes have associated database tables. ClassPK contains an identifier that references a row in the table. This seems to be used to add levels of abstraction for second order relationships.
Tables that were changed after adding the new account Rock Seller.
- AccountEntry
- Table to store account data.
- Primary key is accountEntryId.
- Row was added for Rock Seller
- AccountEntryId for Rock Seller is 32503.
- AssetEntry
- Table to track assets. In Liferay pretty much anything can be an asset.
- Row was added for Rock Seller account.
- UserId was 20123 pointing to Test Test user.
- ClassNameId was 28707 with ClassPk of 32503. Which points to com.liferay.account.model.AccountEntry in the ClassName_ table.
- Group_
- Table to track groups. Groups are effectively sites. This is a site specifically for the Rock Seller account.
- GroupId was 32504
- ClassNameId was 28707 which points to com.liferay.account.model.AccountEntry in the ClassName_ table.
- ClassPk was 32503 which points to the Rock Seller account.
- ResourcePermission
- Table to track permissions to resources such as portlets and models.
- OwnerId was 20123 which points to the Test Test user.
- Row added for group 32504
- Row added for account 32503
- LayoutSet
- Table to track layout sets which are effectively web pages.
- GroupId is 32504.
- Two layou sets added. One private and one public.
Resources
tags: java - liferay ce - liferay - ce - mariadb - fedora - 41 - fedora 41 - linux - account