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!

Relationship Graph

[ View Issue ] [ Dependency Graph ]

Viewing Issue Simple Details
ID	Category	Type	Reproducibility	Date Submitted	Last Update
0000658	[In-Portal CMS] Optimization	task	N/A	2010-03-27 17:18	2012-07-25 05:33

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

Summary	0000658: Extremely Long Priority numbers stored in Cache for "Parsed Sections"
Description	Hi all, I think we have a little bug/issue in parsed_sections serialized array that is stored in Cache table. Some records have super long Priority numbers. I know we don't use/put this long digits so it must something auto-calculated or something. here is an example: s:1:"r";s:15:"no_pass_through";i:1;}s:11:"permissions";a:2:{i:0;s: 4:"view";i:1;s:4:"edit";}s:8:"priority";d: 4.29999999999999982236431605997495353221893310546875;s:4:"type";i:1;s: 13:"SectionPrefix There not too many of this, but I thin k we should bring it to the human read format and safe a bit of DB space ;)
Additional Information	Plan: 1. convert all priorities to strings before storing them in database 2. attach sections_parsed cache size before and after the fix