I see. I was not aware of this because the display results of "select * from <TBLXYZ>" has always shown up in ascending order of ID. I don't recall a single instance where it was delivered out of order, and hence my assumption.
Now I understand Kishore's comment better about the DB not knowing about occurance and having to use order by. Will do. Kavita On 10/14/10 12:10 PM, "Alan Chandler" <a...@chandlerfamily.org.uk> wrote: > On 14/10/10 17:26, Kavita Raghunathan wrote: >> I found an example: >> Select * from<tblxyz> order by ID where limit 1 offset n-1 >> >> Will retreive the nth row. >> In this case order by ID is probably not necessary as its already ordered >> with a few missing rows. > > It might happen to be ordered - but that is an implementation detail. > Unless you use the ORDER BY clause the database may deliver the records > in any order it wishes. It is not forced to use the ID order. > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
