Edward Wilson wrote:
What I was trying to say was: with other db products the drivers (or something
somewhere)
calculated the number of rows returned in a query automagicly. I have never
had to do anything
'extra' to get the number of rows in a query other than
resultset-object.rowcout - 'rowcout' being
whatever the syntax was for that particular environment. So what I meant was,
I have always taken
for granted that the rowcount was 'apart of' the query returned from the
database and not
something that I had to do 'extra' in addition to fetching the data to begin
with. I hope this
was clear.
The other DB, usually, perform the query, retrive all the rows and
stores them somewere. When you get the number of rows in your query, the
query had been completly executed.
SQLite does the same. Your resulset is called "table" and you can get it
using sqlite3_get_table("SELECT bla bla bla bla bla").
But Sqlite permits *also* to retrive the data as soon as they are
calculated. This permits to save memory (no one has to store somewhere
the resultset) and to process the results while the query is executed.
Paolo
