sql - Sqlite Transaction - When Does Reserve Lock Take Effect -

I was thinking at the point after issuing a current transaction, () the call attach to the reserve lock and write Starts to stop?

Does the reserve lock match the actual start transaction call, or is it done only after the name of the commute and running the transaction?

I ask B / C to take advantage of my current data access layer, and not everyone has the need to write a custom transaction to stop the status of a race, I started Do not want to call (), and then call any combination of existing selection / insert / update wrapper to solve any problem, while having unique write access, eventually call a commute. I am trying to avoid the circumstances of the race, I want the reserve lock on the transaction to be active for the transaction that starts "immediately" (i.e., before it comes back).

If more explanations or details are required, please let me know and I will be happy to make them available. Thanks for your expertise please.

say:

first read operations against a database Creates a stock lock for and creates the first writing operation reserve lock

When all changes are completed in the page cache, then the first actual writing operation committ . . To force a force to apply a lock while executing BEGIN , get started :

After an initial time, No other database connection will be able to write to the database or it can get a quick one or BEGIN exclusivity. However other processes can continue to read from the database.

If you want to stop reading (which should not be necessary because all transactions are properly sorted in any case), BEGIN Explore .