From: Keith Ivey
Jigal van Hemert wrote:
Maybe because dates before Jan 1, 1970 have an undefined timestamp and
dates
beyond 2038 cannot be used with 32-bit integers? Quite a few people were
born before 1970 and sometimes one needs to store their date of birth
too?
Yes, but birthdates
On 6/21/05, Sebastian wrote:
i never understand why people use datetime anyway.. unix timestamp is so
much easier to work with.
Unix epoch is by definition UTC. Sometimes I want to work with dates
in some local timezone. In other databases that have a more complete
implementation of the SQL
Hi,
just see the client connection timezone here :
http://dev.mysql.com/tech-resources/articles/4.1/time.html
you should certainly use --default-time-zone='-3:00'
Mathias
Selon Simon Garner [EMAIL PROTECTED]:
On 21/06/2005 2:45 p.m., Scott Haneda wrote:
I need to run a BETWEEN select where
i never understand why people use datetime anyway.. unix timestamp is so
much easier to work with.
[EMAIL PROTECTED] wrote:
Hi,
just see the client connection timezone here :
http://dev.mysql.com/tech-resources/articles/4.1/time.html
you should certainly use --default-time-zone='-3:00'
On 21/06/2005 6:55 p.m., Sebastian wrote:
i never understand why people use datetime anyway.. unix timestamp is so
much easier to work with.
Because DATETIME is stored natively as a date and time, which means you
can then use the date and time SQL functions with them (such as
DATE_ADD,
From: Sebastian
i never understand why people use datetime anyway.. unix timestamp is so
much easier to work with.
Maybe because dates before Jan 1, 1970 have an undefined timestamp and dates
beyond 2038 cannot be used with 32-bit integers? Quite a few people were
born before 1970 and sometimes
Jigal van Hemert wrote:
Maybe because dates before Jan 1, 1970 have an undefined timestamp and dates
beyond 2038 cannot be used with 32-bit integers? Quite a few people were
born before 1970 and sometimes one needs to store their date of birth too?
Yes, but birthdates are generally DATE, not
I need to run a BETWEEN select where I put in a date rate, the time was at
one point irrelevant, but now the client is in a new time zone +3 hours
ahead, so
BETWEEN 2005010100 AND 20051201235959 is what I pass in now, which is
wrong, how can I add three hours to it and get the days and
On 21/06/2005 2:45 p.m., Scott Haneda wrote:
I need to run a BETWEEN select where I put in a date rate, the time was at
one point irrelevant, but now the client is in a new time zone +3 hours
ahead, so
BETWEEN 2005010100 AND 20051201235959 is what I pass in now, which is
wrong, how can I
