Pre loading of content object attributes when you fetch nodes using content 'list' or 'tree' fetch: http://issues.ez.no/IssueView.php?Id=14471&activeItem=10&rv[]=1055&rm=1&column=8&sortOrder=4
As far as I understand it correctly, when is switch the default setting off, a number of lightweight direct fetch queries will be used instead of this gigantic "OR compound", right? This should not affect the functionality in any way?
Just to make sure: before you implement a INI-based setting (or whatever) in eZ Publish 4.1.x, if I disable the load_data_map by default in 4.0.x, all my lists will be generated based on small queries, no matter how many items fetched, right? There is no internal limit of 15, right?
Hi,
I have severe troubles with sloooow queries like the one described in this thread. I see that this has been solved in 4.1, but what about eZ 3.8.6? I am running a huge site with about 100 000 content objects. Fetches like these can take up to several minutes to perform.
Does anyone have a clue on how to fix this in eZ 3.8.6?
Best regards, /Nicklas
Nicklas Lundgren, Managing Director
Novitell AB, Sweden