On 1 Jul 2013, at 2:54pm, Gabriel Corneanu <gabrielcorne...@gmail.com> wrote:
> While I agree non-standard features should be kept to minimum possible, I
> needed this so often that I simply think there is a larger potential benefit.
> Another example: I don't do web design, but I remember some WYSIWYG editors
> (Macromedia Dreamweaver) where it was easily possible to generate HTML tables
> (paged listings) from result sets. There was no code to write, just mark some
> fields from the result set.
I /do/ write web interfaces for databases kept in SQLite. I do that a lot.
There is no advantage to me of knowing the 'line number' of an entry returned
by a SELECT. What I need to know about the table is the rowid of the row in
the database and I find that by asking for it explicitly:
SELECT rowid,aColumn,anotherColumn FROM MyTable
I sometimes store that rowid in the HTML code I make up my table with:
newRow = document.createElement('tr')
newRow.id = 'teamsRow'+teamRow.rowid
This makes it easy to find the row on the page to change if underlying data
changes, and to know which row of the database to change if the user wants to
change something in the table. But I can’t think of any situation in which I
would want to use the number of the row in the returned set.
Simon.
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
