> I expect #2 to work best. Make sure to enclose the whole thing in an
> explicit transaction (or at least, run large batches within explicit
> transactions; one implicit transaction per deleted row will be slow as
> molasses).

If I do this, would you expect _step() for the "BEGIN TRANSACTION" query and 
_step() for each "DELETE" query to be very fast, but the _step() for the "END 
TRANSACTION" query to take most (99%) of the time?

Would you expect a similar speed boost for "INSERT"? Is one by one "INSERT" in 
a similar way slow as molasses, and wrapping many inserts in a transaction 
recommended?                                    
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to