by Raskii » Fri Feb 09, 2007 10:37 am
The problem is twofold:
First: The builtin MySQL (or whatever DB you're using) sorting algorithm is being used, which makes it much harder to do any data manipulation to help things sort better (this is because your data's being sorted before you even get it!)
Second: The data - which is coming from roster_players.dateupdatedutc - is in a poor format for proper sorting (it's stored as "m/d/y H:i:s").
The best fix for this would be to change the format that roster_player.dateupdatedutc uses. Preferrably to something more sortable such as the UNIX Epoch ("U"). Doing this would allow you to continue using builtin DB sorting and eliminate one of the steps needed for reformatting the date later on.
Because the preferred fix would take more time than I have to get the sorting problem fixed, I'm working on a quick - and VERY dirty - method instead.
I'll post it here when I'm done.