Hi all,
I have a very strange problem with mysql-4.0.22
running on a big endian processor platform.When the
timestamp gets updated as '2005-01-01 23:00:00', it
actually seems to be converted internally as
20050104230000.Similarly '2005-01-02 23:00:00' is
'20050105230000'.
The problem is that let us say ,some value in one of
the rows got updated at a system time of '2005-01-02
03:00:00'.It's timestamp is now '20050102030000'.But
the DB refresh function is unable to get hold of this
row in the query "SELECT * from tbl_name WHERE
timestamp > '20050101230000'".
This problem happens only when the hour field is 23 on
a Big endian system.(The day somehow gets incremented
by 3 during comparison and insertion).It works fine on
my PC.
I am hoping someone could give me some ideas as to why
this may happen
Thanks in advance,
Manasvini
__________________________________
Discover Yahoo!
Use Yahoo! to plan a weekend, have fun online and more. Check it out!
http://discover.yahoo.com/
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
