Igor, Why it's unpredictable? It's because of different sqlite versions or even in the same sqlite version it's unpredictable? If the latter is the case, I would like to know the internal of sqlite which makes it unpredictable.
Richard, In sqlite 3.3.8, since it allows INSERT while SELECT statement is running, I assume that it will return an 11th row. Can you explain how step operation works interiorly on a table? (Does it gets all the results at one time and returns a single result during each sqlite3_step or it searches for the rows matching the criteria one after the other (i.e. in each sqlite3_step call it searches for the row from the current row onwards till the end of the table) ? Regards, Phani -----Original Message----- From: Igor Tandetnik [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 06, 2007 5:41 PM To: SQLite Subject: [sqlite] Re: Does sqlite3_step searches for a row in the table / or some results buffer? B V, Phanisekhar <[EMAIL PROTECTED]> wrote: > Assume a query > > "select * from table " > > Let there be 10 rows in the table > > Hence there will be 10 rows in the result corresponding to the above > query. We can get all these 10 rows by calling sqlite3_step 10 times. > > Assume after 3 sqlite3_step calls, we insert a row into this table. > Now after insertion we call sqlite3_step for the instruction "select > * from table". Will this newly added row also get returned in this > case? It may or may not. In general, it's unpredictable. In this particular case, it will most likely appear at the end of enumeration, as an 11th row. Igor Tandetnik ------------------------------------------------------------------------ ----- To unsubscribe, send email to [EMAIL PROTECTED] ------------------------------------------------------------------------ ----- ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
