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

List:       mysql
Subject:    date/datetime checking too strict in 4.1?
From:       Daniel DeLorme <daniel () dan42 ! com>
Date:       2003-05-31 6:54:14
[Download RAW message or body]

I have a query where I use a LIKE on a DATETIME field and it used to work
   i.e.: WHERE article_datetime LIKE '2003-05%'
but when we upgraded to 4.1 it stopped working (it didn't return any
results). In itself I find that increased restrictiveness to accomplish
no purpose. And then I found out that the same query on a DATE field *did*
work as expected. It works on a DATE but not on a DATETIME. Where's the
logic in that?

If possible, I would like to find someplace that has more details on the
nature of the change that was made to date/datetime checking. The changelog
for 4.1.0 isn't very informative, it only says that "DATE/DATETIME checking
is now a bit stricter to support the ability to automatically distinguish
between date, datetime, and time with microseconds."

Thanks,
Daniel DeLorme
-- 
________________________________________________________________________
Daniel "42" DeLorme                                         /| |Ż|/ŻŻŻ\
ICQ:11411269, AIM:DanFortyTwo                              / |_| | Ż| |
encyclopedist @ http://www.animenewsnetwork.com            |___  | / /_
webmaster @ http://dan42.com (Jin-Roh, Millennium Actress)     |_||____|
ŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻŻ


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/mysql?unsub=mysql@progressive-comp.com

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