On Thu, 19 Feb 2009, P Kishor wrote: > There is the rowid, but I am not sure what you want to do... are you > expecting a database table to be a linear list of entries? Generally one > uses a spreadsheet for that kind of stuff. A SQL database doesn't have an > internal concept of order. You specify a criteria and the db returns a SET > of rows or records. You can constrain the SET by specifying criteria (the > WHERE clause), and you can impose an order on the returned rows by > specifying an ORDER clause.
And, there is no particular order of rows in the table. They can be re-ordered behind the scenes when the db engine determines benefits to the change. That's why it's never a good idea to use row IDs. Rich -- Richard B. Shepard, Ph.D. | Integrity Credibility Applied Ecosystem Services, Inc. | Innovation <http://www.appl-ecosys.com> Voice: 503-667-4517 Fax: 503-667-8863 _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
