A date type is not a standard type? Well, you should stop. You know, deep holes and silly, stuff like that. And, to be clear, MySQL is FAR FAR FAR AWAY from being THE RDBMS.
Off Topic:
Who hired you A.D.A., if I may ask. Speak for yourself and let Rudy speak for him self. Itāll be wiser and manlier. And a point on which Iām sure Rudy would agree with me.
[QUOTE=itmiticÄ;5131260]I shall leave to others to understand why the title of this thread āGetting Distinct Dateā is not the same with āGetting Distinct UNIX_TIMESTAMPā:[/quote]this was addressed in post #12
steve didnāt want distinct dates at all, he merely wanted to list orders for a date range, and divide the list by date with a date heading
and right from the beginning of the whole thread, it has always been about integers, so all your yammering about standard sql now is an unnecessary diversion
the chances are remote that you will admit that you really didnāt understand the implications for your BETWEEN attempt
displaying the date for a group of orders was not the main issue, it was getting the right WHERE clause, and letās face it, you failed there
Yeah, itās about date. Getting the date (day: Sat 3rd June) out of the timestamp alongside the order id column would prepare the data for the final report the OP wants.
Post #12 doesnāt change what the OP wants: he still only wants the day part from the orderDate column, along with the ID column.
And he wants a report which he can easily build after the query that returns the day part from timestamp.
You suggested him to make the processing of the UNIX_TIMESTAMP in php instead. Why? Since MySQL is guilty (read source) for the UNIX_TIMESTAMP joy (read issue). Is this how things are done: screw up in MySQL and FIX IT! in php? I seriously doubt it.
Speak for yourself and let Rudy speak for him self. Itāll be wiser and manlier. And a point on which Iām sure Rudy would agree with me.