Aer you not storing a date associated with each record??
If you're not, I'd highly recommend doing that, rather than just hoping
that mysql will return the order of results the way you want it. Ordering
by date should be pretty inefficient also.
mysql returns the records in the order they were entered, so say you
entered meet A after meet B, when it was infact before meet B mysql will
return meet A as the most recent meet..
Also, finding out about sorting would be a *real* easy task if you just
looked at the documentation on mysql.com...
Atle
On Thu, 22 Feb 2001, Adam C Buggia wrote:
>
> there is a table result and a table meet where a column in result is
> "meet_hnd." (there maybe hundreds of results per meet) so I have indexed
> the result table on meet_hnd. This sped things up dramatically. Now, the
> I see it, though we are indexed on meet_hnd, when searching for results
> mysql is starting at the first meet_hnd though we are most likely wanting
> to retrieve the last meet_hnd. If this were indexed in reverse order than
> the first meet_hnd would most likely be the one we are looking for.
>
>
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
