'attribute_filter' with dates in a fetch function

Previous topic

General

Next topic

Author	Message
Anthony M.	Wednesday 06 September 2006 9:05:19 am Hello, I would like to filter on the date in my fetch function, with the attribute ‘attribute_filter’, like this : fetch( ... 'attribute_filter', array( array( 'classe/champdate' , '>=' , currentdate() ) ) ... ) I would like to test if ‘champdate’ from the class ‘classe’ is greater or equal than the current date, but currentdate() return a timestamp, so is it possible to write the timestamp of ‘champdate’ to compare the timestamps ?? else with 'attribute_filter', we can compare 2 dates with the format 'JJ/MM/AAA' ??? Thanks for your help Anthony Anthony
Claudia Kosny	Wednesday 06 September 2006 12:31:01 pm Hello Anthony If you champdate attribute has the datatype date you can filter exactly the way you stated in your post, the comparison is done via the timestamp of the attribute. If however your attribute champdate has the datatype string things get more complicated. You can transform the output of currentdate() to a more readable date using the datetime() function of EZ. But to compare the dates properly they must be of the format YYYYMMDD and the comparison must be done on a integer basis. With your date format of 'JJ/MM/AAA' (what to me translates as day/month/year using two or three digits) a comparison is not possible as the first of an arbitrary month will always be earlier than the second of another month, no matter what the respective months (or years) are. Greetings from Luxembourg Claudia

Author

Message

Anthony M.

Wednesday 06 September 2006 9:05:19 am

Hello,

I would like to filter on the date in my fetch function, with the attribute ‘attribute_filter’, like this :

fetch( ... 'attribute_filter', array( array( 'classe/champdate' , '>=' , currentdate() ) ) ... )

I would like to test if ‘champdate’ from the class ‘classe’ is greater or equal than the current date, but currentdate() return a timestamp, so is it possible to write the timestamp of ‘champdate’ to compare the timestamps ?? else with 'attribute_filter', we can compare 2 dates with the format 'JJ/MM/AAA' ???

Thanks for your help
Anthony

Anthony

Claudia Kosny

Wednesday 06 September 2006 12:31:01 pm

Hello Anthony

If you champdate attribute has the datatype date you can filter exactly the way you stated in your post, the comparison is done via the timestamp of the attribute.

If however your attribute champdate has the datatype string things get more complicated. You can transform the output of currentdate() to a more readable date using the datetime() function of EZ. But to compare the dates properly they must be of the format YYYYMMDD and the comparison must be done on a integer basis.
With your date format of 'JJ/MM/AAA' (what to me translates as day/month/year using two or three digits) a comparison is not possible as the first of an arbitrary month will always be earlier than the second of another month, no matter what the respective months (or years) are.

Greetings from Luxembourg

Claudia

eZ debug

Timing:	Jan 18 2025 16:01:31
Script start
Timing:	Jan 18 2025 16:01:31
Module start 'layout'
Timing:	Jan 18 2025 16:01:31
Module start 'content'
Timing:	Jan 18 2025 16:01:31
Module end 'content'
Timing:	Jan 18 2025 16:01:31
Script end

Main resources:

Total runtime	0.0177 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.0068	588.0391	152.6406
Module start 'layout'	0.0068	0.0035	740.6797	39.4766
Module start 'content'	0.0103	0.0052	780.1563	89.3516
Module end 'content'	0.0155	0.0022	869.5078	30.3047
Script end	0.0176		899.8125

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0028	15.5868	14	0.0002
Check MTime	0.0011	6.4780	14	0.0001
Mysql Total
Database connection	0.0010	5.6217	1	0.0010
Mysqli_queries	0.0031	17.6634	3	0.0010
Looping result	0.0000	0.0957	1	0.0000
Template Total	0.0018	10.3	1	0.0018
Template load	0.0009	5.0904	1	0.0009
Template processing	0.0009	5.1983	1	0.0009
Override
Cache load	0.0006	3.5518	1	0.0006
General
dbfile	0.0003	1.9364	8	0.0000
String conversion	0.0000	0.0526	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