Best practices - DateTime vs Database question

2006-01-17 Thread John Peacock
I'm in the planning stages for a membership database (probably using Catalyst) to replace InfoCentral (worst-case PHP spagetti code, since massively hacked by yours truly). One feature I want to improve upon is the calendar. Since this is going to be for my synagogue, I need to also display

Re: Best practices - DateTime vs Database question

2006-01-17 Thread Dave Rolsky
On Tue, 17 Jan 2006, John Peacock wrote: My questions are: 1) What should I store in the database? a) Native MySQL DATETIME field? I'd go with this one, since it will make it easiest to do many operations in the DBMS (sorting, restriction queries by date, etc). 2) Should I use DateTime at

Re: Best practices - DateTime vs Database question

2006-01-17 Thread John Peacock
Dave Rolsky wrote: If you need to translate Hebrew dates into Gregorian dates, which I assume you do, then I'd think DateTime would help with that. The other way round, actually. The calendar has to correspond to the current common calendar, and I want to display the corresponding Hebrew

Re: Best practices - DateTime vs Database question

2006-01-17 Thread kellan
On 1/17/06, Dave Rolsky [EMAIL PROTECTED] wrote: a) Native MySQL DATETIME field? I'd go with this one, since it will make it easiest to do many operations in the DBMS (sorting, restriction queries by date, etc). With the caveat that MySQL's understanding of timezones can be a bit