[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mysql
Subject:    Re: Date problem
From:       Daniel Beckham <danbeck () mtginfo ! com>
Date:       2000-02-02 14:24:05
[Download RAW message or body]

I had a little problem like this... but it turned out to be a stupid 
programming trick.  I was using the MySQL timestamp value in a PHP function 
that required a unix timestamp. =)  I got very weird results as you might 
well imagine (year 2019, I think).

After converting the MySQL timestamp into a unix timestamp inside of my 
SELECT query, it seemed to have corrected itself. =)

Might you be doing something similar?

Daniel

At 01:41 PM 2/2/00 +0200, you wrote:
>Kole Dunn writes:
>  > Hi all,
>  > I have a date column that displays 2001-00-21 instead of 2000-2-1.
>  > Yesterday, it showed the year as 2010. Anyone know what's going on?
>  > The date is correct on my machine. Here is the results of SHOW FIELDS...
>  >
>  > +---------+--------------+------+-----+---------+----------------+
>  > | Field   | Type         | Null | Key | Default | Extra          |
>  > +---------+--------------+------+-----+---------+----------------+
>  > | qty     | varchar(15)  | YES  |     | NULL    |                |
>  > | sku     | varchar(20)  | YES  |     | NULL    |                |
>  > | product | varchar(50)  | YES  |     | NULL    |                |
>  > | price   | decimal(9,2) | YES  |     | NULL    |                |
>  > | sub     | decimal(9,2) | YES  |     | NULL    |                |
>  > | date    | date         | YES  |     | NULL    |                |
>  > | uid     | varchar(15)  | YES  |     | NULL    |                |
>  > | id      | int(11)      |      | PRI | 0       | auto_increment |
>  > +---------+--------------+------+-----+---------+----------------+
>  >
>  >
>  > KD
>
>HI!
>
>What program did you use that displayed data diffrently ??
>
>Please use mysql monitor program and see what results do you get.
>
>We have not been reported problems that date field changed out of
>itself.
>
>May be some of your programs did the update. You could check it out if
>you had a timestamp column in that table, or if you had update log
>turned on.
>
>Regards,
>
>Sinisa
>
>+----------------------------------------------------------------------+
>| TcX  ____  __     _____   _____  ___     ==  mysql@tcx.se            |
>|     /*/\*\/\*\   /*/ \*\ /*/ \*\ |*|     Sinisa Milivojevic          |
>|    /*/ /*/ /*/   \*\_   |*|   |*||*|     mailto:sinisa@mysql.com     |
>|   /*/ /*/ /*/\*\/*/  \*\|*|   |*||*|     Larnaka, Cyprus             |
>|  /*/     /*/  /*/\*\_/*/ \*\_/*/ |*|____                             |
>|  ^^^^^^^^^^^^/*/^^^^^^^^^^^\*\^^^^^^^^^^^                            |
>|             /*/             \*\                Developers Team       |
>+----------------------------------------------------------------------+
>
>--
>---------------------------------------------------------------------
>Please check "http://www.mysql.com/Manual_chapter/manual_toc.html" before
>posting. To request this thread, e-mail mysql-thread26250@lists.mysql.com
>
>To unsubscribe, send a message to:
>     <mysql-unsubscribe-danbeck=mtginfo.com@lists.mysql.com>
>



-- 
---------------------------------------------------------------------
Please check "http://www.mysql.com/Manual_chapter/manual_toc.html" before
posting. To request this thread, e-mail mysql-thread26267@lists.mysql.com

To unsubscribe, send a message to:
    <mysql-unsubscribe-mysql=progressive-comp.com@lists.mysql.com>

[prev in list] [next in list] [prev in thread] [next in thread]