Imported From: http://groups.google.com/group/in-portal-dev/browse_thread/thread/a28db8a652319098#
Recently we have touched PortalUser table optimization in Reviewing & Optimizing Database Queries. Here I'm about to address several improvements to that table too.
In-Portal has 2 sections, that are called "Users" and "Administrators". These sections are used to manage users and administrators. In fact both users and administrators are stored in a PortalUser table.
...
- since user always have a primary group, then there is no need to ad it to "UserGroup" table (especially since it's added virtually after user login according to my previous proposal);
- if user has non-default primary group, then it can be specified in new "PrimaryGroupId" field in "PortalUser" table via group dropdown (based on Erik's proposal in this discussionReviewing & Optimizing Database Queries).
Related Tasks
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|