13 messages in com.mysql.lists.win32Re: Strange date behavior
FromSent OnAttachments
Gertrud Lohwasser06 Jul 2000 03:37 
Gertrud Lohwasser06 Jul 2000 04:26 
Gertrud Lohwasser07 Jul 2000 00:19 
Sinisa Milivojevic07 Jul 2000 03:31 
Gertrud Lohwasser07 Jul 2000 04:00 
sin...@mysql.com07 Jul 2000 07:48 
Jonah H. Harris09 Jul 2000 13:23 
Jonah H. Harris09 Jul 2000 13:38 
Nick Arnett09 Jul 2000 15:06 
Sinisa Milivojevic10 Jul 2000 03:27 
Sinisa Milivojevic10 Jul 2000 03:29 
Jonah H. Harris10 Jul 2000 11:13 
Tonci Grgin11 Jul 2000 02:45 
Subject:Re: Strange date behavior
From:Sinisa Milivojevic (sin@mysql.com)
Date:07/10/2000 03:29:06 AM
List:com.mysql.lists.win32

On Mon, 10 Jul 2000, Nick Arnett wrote:

Anybody seen anything like this...

I have a table with a date field, where there seem to be some dates that I can't find with the "=" operator, but they show up when I use a ">" operator. I can't see anything about them that would lead them not to be found by "=".

The table has about 4.5 million rows, with dates from 1996 to the present, but the ones that aren't found by "=" are all from mid-May through the end of June of this year, which leads me to believe that this was caused by changes to the Perl script that fills in the field, but I sure can't see what caused it. I've tried re-running the script to generate all new dates, but I get the same darn thing. I've rebuilt the indexes and upgraded from 3.22 to 3.23. Nothing. I guess my next step will be to wipe out the dates entirely and re-create them.

Any suggestions will be most welcome.

HI!

Check whether column type is date or datetime ...

If it is date, check that a date string used for '=' comparisons is well constructed.

Regards,

Sinisa