On Thu, 19 Feb 2009, His Nerdship wrote: > I will just do what I said before, namely read the whole table (it won't > be too big) and extract the required row from the returned array. The > reason I wanted a row ID was that all the fields in the display grid can > be edited, so by the time I come to process it, any of them might have > changed from the original in the database so I can't use them in a WHERE > clause.
I've no idea what language you're using for your application, but what you describe is not always the case. I've an application written in python that uses the pysqlite2 middleware. I can fetch a single row, examine it to determine if it meets the criteria for selection, then fetch the next record. Records meeting selection criteria are added to a list and displayed in the appropriate widgets. 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
