More Specific Fetching

Next topic

Author	Message
Matthew Rat	Thursday 10 April 2003 1:16:03 pm I have added 2 fields to the Article class: start_date and stop_date. These are to be used by the template to determine if an article has "expired" or not. I have not been successful in implementing a fetch that will retrieve articles from a given node_id where the start_date is prior to now and where the stop_date is after now. Is this unsupported? I know you can do something similar to this using a "section show=" but that seems incredibly inefficient and could severely slow down the process if you are processing attributes AFTER the database call returns everything in a "folder" or node_id. Any thoughts?
Jan Borsodi	Friday 11 April 2003 7:00:26 am The only way to this at the moment is to create custom template SQLs for the fetching and either put in a custom template operator or template fetch function. -- Amos Documentation: http://ez.no/ez_publish/documentation FAQ: http://ez.no/ez_publish/documentation/faq

Author

Message

Thursday 10 April 2003 1:16:03 pm

I have added 2 fields to the Article class: start_date and stop_date. These are to be used by the template to determine if an article has "expired" or not. I have not been successful in implementing a fetch that will retrieve articles from a given node_id where the start_date is prior to now and where the stop_date is after now. Is this unsupported? I know you can do something similar to this using a "section show=" but that seems incredibly inefficient and could severely slow down the process if you are processing attributes AFTER the database call returns everything in a "folder" or node_id. Any thoughts?

Jan Borsodi

Friday 11 April 2003 7:00:26 am

The only way to this at the moment is to create custom template SQLs for the fetching and either put in a custom template operator or template fetch function.

--
Amos

Documentation: http://ez.no/ez_publish/documentation
FAQ: http://ez.no/ez_publish/documentation/faq

eZ debug

Timing:	Jan 18 2025 05:12:30
Script start
Timing:	Jan 18 2025 05:12:30
Module start 'layout'
Timing:	Jan 18 2025 05:12:30
Module start 'content'
Timing:	Jan 18 2025 05:12:30
Module end 'content'
Timing:	Jan 18 2025 05:12:30
Script end

Main resources:

Total runtime	0.0172 sec
Peak memory usage	4,096.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0066	589.0234	152.6250
Module start 'layout'	0.0066	0.0033	741.6484	39.4453
Module start 'content'	0.0099	0.0050	781.0938	89.2109
Module end 'content'	0.0150	0.0022	870.3047	30.3047
Script end	0.0171		900.6094

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0027	15.7728	14	0.0002
Check MTime	0.0012	7.0203	14	0.0001
Mysql Total
Database connection	0.0010	5.7271	1	0.0010
Mysqli_queries	0.0027	15.9673	3	0.0009
Looping result	0.0000	0.1000	1	0.0000
Template Total	0.0018	10.3	1	0.0018
Template load	0.0009	5.4535	1	0.0009
Template processing	0.0008	4.8242	1	0.0008
Override
Cache load	0.0007	3.8158	1	0.0007
General
dbfile	0.0003	1.5613	8	0.0000
String conversion	0.0000	0.0597	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