[In-Portal] Extremely Long Priority numbers stored in Cache for "Parsed Sections"

[Dmitry A.]

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 ;)

Cheers!

[Alexander Obuhovich]

I agree. It looks like when priority is not and integer number, then it could be stored like this. Section priority is used only once, when section's order inside parent section is determined. After that it's no longer is needed. I propose we unset "priority" key from cached section contents.

Just remembered, that we have DBG_SHOW_TREE_PRIORITY option for debugger, when this priority is shown, then we can't just unset it. We could convert it to string, so it won't take too much space in serialized form.

--
You received this message because you are subscribed to the Google Groups "In-Portal Bugs Team" group.
To post to this group, send email to in-port...@googlegroups.com.
To unsubscribe from this group, send email to in-portal-bug...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/in-portal-bugs?hl=en.

--
Best Regards,

http://www.in-portal.com
http://www.alex-time.com

[Dmitry A.]

Okay, so we are converting all Priority values to string? or we just
need to adjust the once that auto-generated?

Cheers!

> > in-portal-bug...@googlegroups.com<in-portal-bugs%2Bunsubscribe@go oglegroups.com>

[Alexander Obuhovich]

There are not auto-generated priorities, since all sections (in tree) are created by developers. So 1st option then, yes.

To unsubscribe from this group, send email to in-portal-bug...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/in-portal-bugs?hl=en.

[Alexander Obuhovich]

Here is the task: http://tracker.in-portal.org/view.php?id=658