Excluding nodes from a list fetch?

«

Previous topic

|

|

Next topic

»

Author	Message
Josh Bair	Monday 04 May 2009 7:55:20 pm We have 2 list fetches and want to exclude nodes from the first fetch in the second fetch. The parent_node_ids are the same as well as the class_attribute_filter. Is there anyway to do this without an extended attribute filter or unnecessarily fetching the same node twice? Ideally we would pass an array of node ids to the second fetch and these would be excluded.
Łukasz Serwatka	Monday 04 May 2009 11:30:10 pm This is not possible I'm afraid. You have to use extended attribute filter if you want to filter on specific node ids. I don't know details behind your implementation logic, but it might be also possible to use offset and max params for foreach template function if you want to skip some first nodes in second loop. Then only one fetch could be used. Personal website -> http://serwatka.net Blog (about eZ Publish) -> http://serwatka.net/blog
Josh Bair	Tuesday 05 May 2009 8:07:07 am Hey Łukasz, I was able to use the offset method in a couple tpl locations but we also have an eZ Flow zone with 2 dynamic blocks that could benefit from this. Both blocks use eZFlowLatestObjects -- same class and parent; just a different number of active results.
Bård Farstad	Tuesday 05 May 2009 8:26:22 am What about writing a custom template function optimized for your fetch? That also enables you to tune the query for your situation and optimize for memory usage and performance. -bård Documentation: http://ez.no/doc
Frédéric DAVID	Tuesday 05 May 2009 8:37:59 am for exclude nodes from list fetch, you can use path in your attribute_filter. attribute_filter, array( array( 'path', 'not_in', array( path_string, path_string) ) I don't know for the performance of this method. Blog : http://www.frefred.fr/blog/ez-publish feZ Meta Data : http://projects.ez.no/fezmetadata

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing:	Jan 30 2025 00:52:19
Script start
Timing:	Jan 30 2025 00:52:19
Module start 'layout'
Timing:	Jan 30 2025 00:52:19
Module start 'content'
Timing:	Jan 30 2025 00:52:19
Module end 'content'
Timing:	Jan 30 2025 00:52:19
Script end

Main resources:

Total runtime	0.0131 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0052	588.1328	151.2109
Module start 'layout'	0.0052	0.0025	739.3438	36.6484
Module start 'content'	0.0077	0.0042	775.9922	94.1563
Module end 'content'	0.0119	0.0012	870.1484	37.9922
Script end	0.0131		908.1406

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0024	18.1561	14	0.0002
Check MTime	0.0011	8.1386	14	0.0001
Mysql Total
Database connection	0.0010	7.4133	1	0.0010
Mysqli_queries	0.0022	16.8987	3	0.0007
Looping result	0.0000	0.0857	1	0.0000
Template Total	0.0009	6.7	1	0.0009
Template load	0.0007	5.2356	1	0.0007
Template processing	0.0002	1.4816	1	0.0002
Override
Cache load	0.0005	3.7067	1	0.0005
General
dbfile	0.0007	5.0206	8	0.0001
String conversion	0.0000	0.0456	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs