TimeStamp issue

2006-03-02 Thread rtroiana
Hi All, I have recently noticed in the MySQL 5.0 documentation in section 11.3.1. The DATETIME, DATE, and TIMESTAMP Types, it's mentioned that TIMESTAMP values cannot be earlier than 1970 or later than 2037. This means that a date such as '1968-01-01', while legal as a DATETIME or DATE

Re: TimeStamp issue

2006-03-02 Thread gerald_clark
rtroiana wrote: Hi All, I have recently noticed in the MySQL 5.0 documentation in section 11.3.1. The DATETIME, DATE, and TIMESTAMP Types, it's mentioned that TIMESTAMP values cannot be earlier than 1970 or later than 2037. This means that a date such as '1968-01-01', while legal as a

Re: TimeStamp issue

2006-03-02 Thread Rhino
/nanonseconds. If you have to keep the fractional part of the seconds, you could store them in a second column defined as some kind of integer. -- Rhino - Original Message - From: rtroiana [EMAIL PROTECTED] To: mysql@lists.mysql.com Sent: Thursday, March 02, 2006 10:10 AM Subject: TimeStamp

Re: TimeStamp issue

2006-03-02 Thread SGreen
in a second column defined as some kind of integer. -- Rhino - Original Message - From: rtroiana [EMAIL PROTECTED] To: mysql@lists.mysql.com Sent: Thursday, March 02, 2006 10:10 AM Subject: TimeStamp issue Hi All, I have recently noticed in the MySQL 5.0 documentation

Fw: TimeStamp issue

2006-03-02 Thread Rhino
. The different formats are explained here: http://dev.mysql.com/doc/refman/5.0/en/datetime.html. -- Rhino - Original Message - From: rtroiana [EMAIL PROTECTED] To: 'Rhino' [EMAIL PROTECTED] Sent: Thursday, March 02, 2006 1:29 PM Subject: RE: TimeStamp issue Thanks for the reply. I'm using

Re: TimeStamp issue

2006-03-02 Thread Rhino
] To: Rhino Cc: mysql@lists.mysql.com ; rtroiana Sent: Thursday, March 02, 2006 1:42 PM Subject: Re: TimeStamp issue In fact, no time values in MySQL are fractional (yet). All times are stored to the nearest second regardless of which date-time-like storage type you use

RE: TimeStamp issue

2006-03-02 Thread rtroiana
to a DateTime column, since I couldn't find that in the documentation? _ From: Rhino [mailto:[EMAIL PROTECTED] Sent: Thursday, March 02, 2006 3:50 PM To: [EMAIL PROTECTED] Cc: mysql@lists.mysql.com; rtroiana Subject: Re: TimeStamp issue Thanks for keeping me honest! I'd

Re: TimeStamp issue

2006-03-02 Thread sheeri kritzer
On 3/2/06, rtroiana [EMAIL PROTECTED] wrote: Thanks to all of you for replying. I'm using DATETIME instead of TIMESTAMP now. Although I still haven't find the answer for my second question. I used to use CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP as default value for my TimeStamp

Timestamp issue in mysql

2002-09-17 Thread Prafulla Girgaonkar
Hello Following is the description of the problem being faced. Problem: The first timestamp column in a table is set to current date-time value as soon as we update one or more columns in the table. Example: The guest information is stored in a table named GUEST. The schema for it is as

Timestamp issue

2002-09-17 Thread Prafulla Girgaonkar
Mysql Version:: Server version 3.23.47-nt Protocol version10 Connection . via named pipe UNIX socket MySQL OS:: Windows NT 4.0 Workstation Hello Following is the description of the problem being faced. Problem: The first timestamp column in a table

Re: Timestamp issue

2002-09-17 Thread Mikhail Entaltsev
automatically. ... You need to change type of fields from timestamp to datetime. Best regards, Mikhail. - Original Message - From: Prafulla Girgaonkar [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Tuesday, September 17, 2002 1:19 PM Subject: Timestamp issue Mysql

re: Timestamp issue in mysql

2002-09-17 Thread Victoria Reznichenko
Prafulla, Tuesday, September 17, 2002, 2:12:58 PM, you wrote: PG Following is the description of the problem being faced. PG Problem: PG The first timestamp column in a table is set to current date-time value as soon as we update one or more columns in the table. It's a normal behaviour of

Critical TIMESTAMP issue?

2001-09-26 Thread Gunter Leeb
Hi everyone, TIMESTAMP types are supposed to contain millis and even nonos. How can I ensure these are set, retrieved and used for ORDER BY and comparisons in MySQL? I cannot find a way to get even millis back. Also MySQL does not seem to order by this information. See below example. Is this a

Re: Critical TIMESTAMP issue?

2001-09-26 Thread Jeremy Zawodny
On Wed, Sep 26, 2001 at 04:53:18PM -0500, Gunter Leeb wrote: Hi everyone, TIMESTAMP types are supposed to contain millis and even nonos. Not according to the documentation. How can I ensure these are set, retrieved and used for ORDER BY and comparisons in MySQL? There is no built-in type