Fetch list/tree: The group_by parameter

«

Previous topic

|

|

Next topic

»

Author	Message
Roy Bøhmer	Sunday 07 August 2005 11:10:13 am Could someone give an example on how to use the group_by parameter when doing a content-list or content-tree fetch? I can't find anything in the docs on that, and some trial and error as resulted in only trial and errors :-) Thanks!
Roy Bøhmer	Sunday 07 August 2005 11:37:38 am I found this thread http://ez.no/community/forum/setup_design/group_by_parameter_in_fetch_function, but I still need some more hints. Can I group by a custom date/time attribute? How? It seems like it only picks the first node - more like a 'unique' kind of function. I would like it to return an array containing one array for each group. Enlight me, please :) - roy
Conrad Chu	Tuesday 14 February 2006 4:35:19 pm I don't know the usage myself, but I did find an example of it here Inside /design/standard/templates/toolbar/full/calendar.tpl: {set month_list=fetch( content, calendar, hash( parent_node_id,$log_node.node_id, class_filter_type, include, class_filter_array, $class_identifier_list, attribute_filter, array( and, array( 'published', '>=', $time_start ), array( 'published', '<=', $time_end ) ), group_by, array( "published", "day" ) ) )
Samuel Sauder	Monday 16 October 2006 7:43:28 am I was trying to figure this out too. Note that group_by is deprecated: http://ez.no/doc/ez_publish/technical_manual/3_8/reference/modules/content/fetch_functions/list <i>The optional "group_by" parameter (grouping on a date/time basis) is deprecated since this functionality is not supported by Oracle and PostgreSQL.</i> This doesn't make any sense to me... Is EZ saying that Oracle and PostgreSQL don't support GROUP BY syntax in SQL?

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 18 2025 16:13:47
Script start
Timing:	Jan 18 2025 16:13:47
Module start 'layout'
Timing:	Jan 18 2025 16:13:47
Module start 'content'
Timing:	Jan 18 2025 16:13:47
Module end 'content'
Timing:	Jan 18 2025 16:13:47
Script end

Main resources:

Total runtime	0.0137 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.0044	589.1484	152.6406
Module start 'layout'	0.0044	0.0024	741.7891	39.4766
Module start 'content'	0.0068	0.0049	781.2656	89.2266
Module end 'content'	0.0117	0.0019	870.4922	34.3047
Script end	0.0136		904.7969

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0024	17.4038	14	0.0002
Check MTime	0.0010	7.4945	14	0.0001
Mysql Total
Database connection	0.0005	3.5080	1	0.0005
Mysqli_queries	0.0018	13.2410	3	0.0006
Looping result	0.0000	0.0803	1	0.0000
Template Total	0.0016	11.8	1	0.0016
Template load	0.0009	6.8117	1	0.0009
Template processing	0.0007	4.9730	1	0.0007
Override
Cache load	0.0006	4.4597	1	0.0006
General
dbfile	0.0002	1.7339	8	0.0000
String conversion	0.0000	0.0594	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.0002 secs