Date: 06/26/08 (MySQL Communtiy) Keywords: mysql, database, sql I have two RHEL5 machines, both built & configured at the same time. Both have MySQL 5.0.45 installed and share an identical database. I put that in red, since it seems to be where the problem is. The strange thing is that both machines returned 334 yesterday. If I change the query (on the supposed broken box) to this: I get 334. I realize there several ways of doing this, but I'm more interested in why, out of nowhere, MySQL decides not to allow WHERE DATE(datetimefield)=blah anymore. Ideas?
|