event_timezones.offset+event_timezones.offset_dst both incorrectly set an integer '0' as default for type 'DATETIME'
pobster - February 21, 2008 - 14:56
| Project: | Event |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | minor |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
Blah, blah, blah - just change them both to default '0000-00-00 00:00:00'.
Throws up an error with the schema module is all.
Pobster
#1
I think these two columns should be a data type of time instead of datetime.
#2
I've changed the default as suggested. Not sure what to do about the date vs datetime issue. IIRC there was a reason I had chosen datetime over time.
#3
Automatically closed -- issue fixed for two weeks with no activity.
#4
I have this problem
adding event, but I have "start 00 00"
аnd errors in logs
event_timezones doesn't exist query: SELECT e.event_start, e.event_end, e.timezone, e.has_time, e.has_end_date .....