I'm glad you found the problem! Sorry my suggestion did not work. I'm still
confused on why you have quotes around the field names in the order by part
of the query, though.
All the best!
-steve-
-
Before posting, please chec
On Monday 17 February 2003 21:06, Ken Goff wrote:
> I have encountered what appears to be a bug in MySQL regarding ORDER
> BY related to a date field when also used in conjunction with
> DATE_FORMAT() or UNIX_TIMESTAMP(). When these functions are applied
> to my date field, MySQL ignores any includ
> SELECT * FROM EventList ORDER BY 'EventDate', 'EventOrder' LIMIT 50;
I'm surprised you happened to get anything in order. Maybe the message got
simplified by the list manager, but did you really mean to order by a
constant string?
Why not:
SELECT * FROM EventList ORDER BY `EventDate`, `
I have encountered what appears to be a bug in MySQL regarding ORDER
BY related to a date field when also used in conjunction with
DATE_FORMAT() or UNIX_TIMESTAMP(). When these functions are applied
to my date field, MySQL ignores any included ORDER BY within the
query. I first noticed this bug
Thanks for the help everyone. I tried changing the type to timestamp¹ and
that did not fix the problem, however when I changed the type to
int¹ and it worked as it was suppose to.
Thanks,
Lael
I have just been able to repeat a bug in a rather simple ORDER BY queries
that was introduced in 3.23.34. I wonder how in the world our test suite
managed to miss it. We should have a fix shortly and as soon as it is
available, will post a patch and will also release 3.23.35. Which reminds us
