[development] Re-Thinking Events in Drupal
rich at strangebirdlabs.com
Sun Mar 5 14:36:08 UTC 2006
It would be great if we could match the date handling to something
similar to the iCalendar spec so you could more easily specify
different type of times/dates. It would mean storing the text date
field (eg, 19970714T133000) and a slightly more intensive parsing
You could be able to say 20060310 and have the event occur on March
10, 2006 for all timezones instead of having to specify a specific
start time. This would be especially helpful for global campaigns
that all happen on the same day but different times. You would also
be able to define something with a start time, but no end time which
is also necessary I believe.
On Mar 5, 2006, at 4:55 AM, Adrian Rossouw wrote:
> On 05 Mar 2006, at 11:22 AM, Bèr Kessels wrote:
>> I think nearly all modules out there should try to rethink how /
>> if they would
>> be if they were nothing more then bunch of a:
>> Views and CCK definitions, Views and CCK extensions and custom
> since we are doing the date type stuff now properly.
> how about we consider moving to actual in-database date fields
> instead of using timestamps.
> i quite like being able to use the database for my date handling.
> Truth be told, that is before
> I started using strtotime (which is by far the most useful function
> in php's date handling lib),
> and was dissillusioned at how horrible mysql's date handling is
> compared to postgres.
> Adrian Rossouw
> Drupal developer and Bryght Guy
> http://drupal.org | http://bryght.com
More information about the development