Re: [sqlite] Re: Re: Does sqlite3_step searches for a row in the table / or some results buffer?

2007-06-07 Thread John Stanton
Predictability is ensured by using transactions. By using BEGIN and COMMIT to make transactions atomic you enforce a predictable state. B V, Phanisekhar wrote: Thanks Igor, Why it's unpredictable? Why can't the unpredictable be made predictable? Assume I update the column of a row that

RE: [sqlite] Re: Re: Does sqlite3_step searches for a row in the table / or some results buffer?

2007-06-07 Thread B V, Phanisekhar
Thanks Igor, >> Why it's unpredictable? Why can't the unpredictable be made predictable? Assume I update the column of a row that meets the criteria of some select stmt and I am yet to encounter that row in sqlite3_step. So the sqlite3_step on that row will return the old column value or

[sqlite] Re: Re: Does sqlite3_step searches for a row in the table / or some results buffer?

2007-06-07 Thread Igor Tandetnik
B V, Phanisekhar <[EMAIL PROTECTED]> wrote: Why it's unpredictable? You are enumerating rows in some order. A new row may be inserted before or after your current position in this order. If it is inserted before, you will not see it in this enumeration. If it is inserted after, you will