The parsing of database tables in Liferay is not complete

Page layout

1: Table layout

The main fields are:

Field	Privatelayout	0 represents a public page
Field	LayoutID	If there are many interfaces in the same community, LayoutID represents each interface, in order
Field	Parentlayoutid	If there are sub-pages under a page you need to specify Parentlayoutid
Field	Priority	Indicate which pages in the same community are at the same level in priority order
Field	Type_	Value range (portlet,embedded,artical,url,link to page), if Type_ is set to Embedded or URL, other systems can be displayed in the Liferay portal
Field	Typesetting	Indicates which template is used for the layout of the page, such as one column or two columns Note: In this case, depending on the Type_ value, the typesettings value is different, for example: Type_ = Portlet,typesettings = state-max-previous= column-1=71_instance_iace, state-max= state-min= Layout-template-id =2_columns_ii Type_ = Url,typesettings = url=http://www.hao123.com sitemap-include=1 target=_blank sitemap-changefreq=daily meta-robots= meta-description= Description=it is testing ... javascript-3= sitemap-priority= javascript-2= javascript-1= meta-keywords= A very important message is saved in the typesettings: How do we know which portlets are in a page, and how these portlets are placed, and this information is stored in this field.

　　

Field: Themeid indicates which theme the page uses, such as Brouchure, Classic, desktop, etc.;

Field: Title indicates the HTML title of the current page, which can be seen in the browser;

Field: GroupId group ID There are two cases in this group: the first refers to the community, and the second refers to the user who has the Power User role;

2: Table Layoutset

Main function: Manage the pages in the community, each community in the table corresponds to two records, one manages the public page, the other one manages the private page.

The fields in the table are:

(1) field: GroupID indicates which community belongs to

(2) field: Privatelayout 0| public page 1| Private page

(3) Field: Logo community logo

(4) field: Themid theme

(5) field: PageCount number of pages owned by the community

(6) Field: VirtualHost Virtual access path for the community

3: Table Portletpreferences

Key Features: Store personalization information

Field: ownerID refers to the owner of this portlet

Field: ownertype

Field: Plid page ID This must be clear, because the Portlet settings for each page may be different

Field: Portletid refers to which portlet

Field: Portletprefence refers to the personalization of this portlet

Okay, the layout of the database table is the main end, here is:

Relationships between communities, organizations, regions, user groups, users

1: Table Group_

The main features are: Save all communities, organizations, regions, user groups, users.

Field: Classnameid where the representative originates: community, organization, region, user group, user.

Field: CLASSPK: When you already know where it came from, which record it came from.

Not finished

The parsing of database tables in Liferay is not complete