-
Type: Bug Report
-
Status: Closed
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: 5.0.3-B1
-
Fix Version/s: 5.2.0-B1
-
Component/s: Optimization
-
Labels:None
-
External issue URL:
-
Additional information:
-
Story Points:1
-
External issue ID:658
-
Copy Issue Key:
-
Patch Instructions:
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
- mentioned in
-
Page Loading...