> Yes, _step would generally take the most time, as that's where the
> actual work happens.
>
> Yes, you would call _step once for every row produced by SELECT (as well
> as certain PRAGMAs), and only once for other statements that don't
> produce a resultset.
Great, thank you. Another question:
If a single _step() call takes a long time to execute (a few minutes), is my
only option to just wait for it? Does SQLite not allow any kind of callback
mechanism for each _step() to indicate how many percentages are done (or how
many bytes have been read/written), and allow for cancellation of the process?
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
