In-Portal Issue Tracker

Welcome to the In-Portal Open Source CMS Issue Tracker! This is a central management / tracking tool for all types of tasks / issues / bugs for the In-Portal Project. Before reporting any issues, please make sure to read the Guide into Issue Tracker and How to Properly Test and Report Bugs!

Dependency Graph

[ View Issue ] [ Relation Graph ] [ Vertical ]

Viewing Issue Simple Details
ID	Category	Type	Reproducibility	Date Submitted	Last Update
0001106	[In-Portal CMS] Optimization	refactoring	N/A	2011-08-24 03:15	2012-07-25 05:33

Reporter	alex	View Status	public
Assigned To	alex
Priority	normal	Resolution	fixed
Status	closed

Summary	0001106: Sorting setting storage improvement ideas
Description	In Admin Console In-Portal makes 4 requests to database during each list-style template display. For example on Phrases list such requests are made: SELECT VariableValue, VariableName FROM PersistantSessionData WHERE VariableName = 'lang_Sort1.' AND PortalUserId = -1 LIMIT 0,1 SELECT VariableValue, VariableName FROM PersistantSessionData WHERE VariableName = 'lang_Sort1_Dir.' AND PortalUserId = -1 LIMIT 0,1 SELECT VariableValue, VariableName FROM PersistantSessionData WHERE VariableName = 'lang_Sort2.' AND PortalUserId = -1 LIMIT 0,1 SELECT VariableValue, VariableName FROM PersistantSessionData WHERE VariableName = 'lang_Sort2_Dir.' AND PortalUserId = -1 LIMIT 0,1 If we change sorting to be stored in one persistent session variable instead of 4 in "FieldName1,order1\|FieldName,order2...." format, then we: 1. save 3 requests to database each time
Additional Information	Plan: 1. code to be changed is located in kDBEventHandler 2. idea is to replace 4 calls to getListSetting/setListSetting method with 1 call (to each method)