On 16 Mar 2010, at 6:12pm, HLS wrote:

> It just seem so simplistic that SQLITE3 does not allow for
> Open Cursor
> for each fetch
>     Issue Update based on ROWID
> endfor
> Close Cursor

One reason you cannot do this is that changing the value of a field may change 
how you step from row to row.  You might change something which needs an index 
changed, for example.  When you start working out how locking by rows works you 
find that you need to lock not just that row but the rows near it, in case one 
of them suddenly moves away.  It can get quite complicated.  One of the things 
that makes SQLite very simple is that it doesn't try to do this, it has either 
everything or nothing locked.

sqlite-users mailing list

Reply via email to