Hi Simon,
Ah, so it's the first _step which does the locking, rather than the _prepare.
That makes sense to me. If I had a serious application using, say, a hundred of different prepared queries, I'd rather batch-prepare them all up front then use them when needed without asking question. Compared to having to check before every use whether to prepare or not right in the core of the app code. If prepare were to lock thing up, it would defeat such use.
_______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
