[geeklog-devel] FW: Events Block behavior for today's events

Mark Howard mark at the-howards.net
Mon Apr 14 07:09:18 EDT 2008

Hi Joe -

I agree with Dirk - the use of CURDATE() provides the desired behavior.

I won't dispute the fact that many other similar issues exist.  ;^)


-----Original Message-----
From: geeklog-devel-bounces at lists.geeklog.net
[mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Joe Mucchiello
Sent: Sunday, April 13, 2008 11:42 AM
To: Geeklog Development
Subject: Re: [geeklog-devel] FW: Events Block behavior for today's events

At 11:31 AM 4/13/2008, Dirk Haun wrote:
>Michael Jervis wrote:
> >I looked into it and it works as expected in current CVS.
>Hmm. I created an event for today, 2 hours in the future. It does not show
>   SELECT * FROM gl_events WHERE dateend >= NOW();

NOW() is APR 13, 2008, 11:40:34 AM EST

>does not return the event, whereas
>   SELECT * FROM gl_events WHERE dateend >= CURDATE();

CURDATE() is APR 13, 2008

>So that change does seem to make sense. Doesn't exactly match my idea of
>NOW(), but there you go ...

NOW() and CURDATE() do different things.

Event "times" in the databse as stored in two pairs of fields using 
separate date and time types. If the date fields were timestamps, 
NOW() would work as you expect.

Issues like this exist throughout the calendar plugin.

Joe Mucchiello
Throwing Dice Games

geeklog-devel mailing list
geeklog-devel at lists.geeklog.net

More information about the geeklog-devel mailing list