shuyangzhou/liferay-portal — pull request #190 by sara-liu (2012-12-11 03:10:04+00:00)
Title: LPS-31465

There are 22 changes.
1. position: File: portal-trunk/portal-impl/src/com/liferay/portlet/asset/service.xml
Entity:"AssetTag"
Finder code:
< finder name= "G_N" return-type = "AssetTag" >
< finder-column name= "groupId" />
< finder-column name= "name" />

reason:The name must be unique in a group.

2. position: File: portal-trunk/portal-impl/src/com/liferay/portlet/journal/service.xml
Entity: "JournalFolder"
Finder Code:
< finder name= "G_N" return-type = "JournalFolder" >
< finder-column name= "groupId" />
< finder-column name= "name" />

reason: Folder name is unique.

3. position: File: portal-trunk/portal-impl/src/com/liferay/portlet/journal/service.xml
Entity: "JournalTemplate"
Finder Code:
< finder name= "SmallImageId" return-type ="JournalTemplate" >
< finder-column name= "smallImageId" />

reason: When they add a JournalTemplate,they'll use "counterLocalService.increment()" to create a smallImageId for it.

4. position: File: portal-trunk/portal-impl/src/com/liferay/portlet/messageboards/service.xml
Entity: ”MBThread“
Finder Code:
< finder name= "RootMessageId" return-type = "MBMessage" >
< finder-column name= "rootMessageId" />

reason: In entity "MBMessage",rootMessageId have the "filter-primary='true'" attribute.

5. position: File: portal-trunk/portal-impl/src/com/liferay/portlet/messageboards/service.xml
Entity: ”MBThreadFlag“
Finder Code:
< finder name= "U_T" return-type = "MBThreadFlag" >
< finder-column name= "userId" />
< finder-column name= "threadId" />

reason: When a user add a thread,it will create only one MBThrteadFlag.

6. position: File: portal-trunk/portal-impl/src/com/liferay/portlet/shopping/service.xml
Entity: "ShoppingItem"
Finder Code:
< finder name= "SmallImageId" return-type = "ShoppingItem" >
< finder-column name= "smallImageId" />

< finder name= "MediumImageId" return-type = "ShoppingItem" >
< finder-column name= "mediumImageId" />

< finder name= "LargeImageId" return-type = "ShoppingItem" >
< finder-column name= "largeImageId" />

reason: When they add a ShoppingItem,they'll use "counterLocalService.increment()" to create SmallImageId,MediumImageId,LargeImageId for it.

7. position: File: portal-trunk/portal-impl/src/com/liferay/portlet/softwarecatalog/service.xml
Entity: "SCProductScreenshot"
Finder Code:
< finder name= "ThumbnailId" return-type = "SCProductScreenshot" >
< finder-column name= "thumbnailId" />

< finder name= "FullImageId" return-type = "SCProductScreenshot" >
< finder-column name= "fullImageId" />

reason: When they add a SCProductScreenshot, they'll use "counterLocalService.increment()" to create thumbnailId,fullImageId for it.

8. position: File: portal-trunk/portal-impl/src/com/liferay/portlet/softwarecatalog/service.xml
Entity: "SCProductScreenshot"
Finder Code:
< finder name= "P_P" return-type = "SCProductScreenshot" >
< finder-column name= "productEntryId" />
< finder-column name= "priority" />

reason: ProductEntryId can point out the productEntry. If there are a lot of SCProductScreenshots in a productEntry,priority will distinguish them.

9. position: File: portal-trunk/portal-impl/src/com/liferay/portal/service.xml
Entity: "LayoutBranch"
Finder Code:
< finder name= "L_P_M" return-type = "LayoutBranch" >
< finder-column name= "layoutSetBranchId" />
< finder-column name= "plid" />
< finder-column name= "master" />

reason: Plid is layout's primary key.In general,when we add a layout , a layoutBranch date will be created in database for it .Only when we select "content display page " as template for the layout,every layoutSetBranch will create one layoutBrach data,at that time ,layoutSetBranchId will distigunsh them.

10. position:File: portal-trunk/portal-impl/src/com/liferay/portal/service.xml
Entity: "LayoutRevision"
Finder Code:
< finder name= "L_H_P" return-type = "LayoutRevision" >
< finder-column name= "layoutSetBranchId" />
< finder-column name= "head" />
< finder-column name= "plid" />

reason: Same reason with the above.

11. position:File: portal-trunk/portal-impl/src/com/liferay/portal/service.xml
Entity: "Lock"
Finder code:
< finder name= "C_K" return-type = "Lock" >
< finder-column name= "className" />
< finder-column name= "key" />

reason: ClassName shows what model the locked entity is,and the key is entity's primary key.Such as document library portlet,when we locked a document,the className is documentlibrary.model.DLFileEntry,and the key is fileEntryId.

12. position: File: portal-trunk/portal-impl/src/com/liferay/portal/service.xml
Entity: "passwordPolicyRel"
Finder code:
< finder name= "C_C" return-type = "PasswordPolicyRel" >
< finder-column name= "classNameId" />
< finder-column name= "classPK" />

reason: The classNameId shows what member added this passwordPolicy,and classPk is this member's primary key.
Such as ,if we assign a passwordPolicy to a user,the classNameId will point out the mode is user,and classPK is userId.If we add a passwordPolicy to a user who has already added one,it will not create a new data in passwordPolicayRel table.

13. position: File: portal-trunk/portal-impl/src/com/liferay/portal/service.xml
Entity: "PasswordPolicyRel"
Finder code:
< finder name= "P_C_C" return-type = "PasswordPolicyRel" >
< finder-column name= "passwordPolicyId" />
< finder-column name= "classNameId" />
< finder-column name= "classPK" />

reason: Same reason with the above.

14. position: File: portal-trunk/portal-impl/src/com/liferay/portal/service.xml
Entity: "PortalPreferences"
Finder code:
< finder name= "O_O" return-type = "PortalPreferences" >
< finder-column name= "ownerId" />
< finder-column name= "ownerType" />

reason: The ownerType shows what type the owner is, and the ownerId is when the type is that ,it's primary key.
Such as when ownerType = 1,the type is company,and the ownerId will be companyId at that time.

15. position: File: portal-trunk/portal-impl/src/com/liferay/portal/service.xml
Entity: "PortletItem"
Finder code:
< finder name= "G_N_P_C" return-type = "PortletItem" >
< finder-column name= "groupId" />
< finder-column name= "name" case-sensitive = "false" />
< finder-column name= "portletId" />
< finder-column name= "classNameId" />

reason: In the same group,the portletItem name can't be reduplicate in a portlet .

16. position: File: portal-trunk/portal-impl/src/com/liferay/portal/service.xml
Entity: "ResourcePermission"
Finder code:
< finder name= "C_N_S_P_R_O_A" return-type = "ResourcePermission" >
< finder-column name= "companyId" />
< finder-column name= "name" />
< finder-column name= "scope" />
< finder-column name= "primKey" />
< finder-column name= "roleId" />
< finder-column name= "ownerId" />
< finder-column name= "actionIds" />

reason: RoleId would point out what role you added the permission for.the Name is the added permission's name.

17. position: File: portal-trunk/portal-impl/src/com/liferay/portal/service.xml
Entity: "Shard"
Finder code:
< finder name= "C_C" return-type = "Shard" >
< finder-column name= "classNameId" />
< finder-column name= "classPK" />

reason: the classNameId shows the type of the mode,and the classPK is the mode's primary key.

18. position: File: portal-trunk/portal-impl/src/com/liferay/portal/service.xml
Entity: "Ticket"
Finder code:
< finder name= "Key" return-type = "Ticket">
< finder-column name= "key" />

reason: The key is created by ”PortalUUIDUtil.generate()“ when we add a ticket.

19. position: File: portal-trunk/portal-impl/src/com/liferay/portal/service.xml
Entity: "WorkflowDefinitionLink"
Finder code:
< finder name= "G_C_C_C_T" return-type = "WorkflowDefinitionLink" >
< finder-column name= "groupId" />
< finder-column name= "companyId" />
< finder-column name= "classNameId" />
< finder-column name= "classPK" />
< finder-column name= "typePK" />

reason: ClassNameId shows which class mode used the workflow,and it can't be reduplicate.