Hello,
On 2017-03-29 18:00, Richard Hipp wrote:
One could omit all OP_Close opcodes and I think everything would still
work. But sometimes an OP_Close can free up resources sooner rather
than later. Also, some b-tree operations are faster if there is only
a single open cursor on that b-tree, and so it is advantageous to keep
the number of open cursors to a minimum.
OP_Close with virtual tables:
+---------+-------------+---------------+---------------+
| VERSION | SELECT | DELETE | UPDATE |
+---------+-------------+---------------+---------------+
| 3.10 | AT THE END | IN THE MIDDLE | IN THE MIDDLE |
+---------+-------------+---------------+---------------+
| 3.17 | DISAPPEARED | DISAPPEARED | AT THE END |
+---------+-------------+---------------+---------------+
``AT THE END'' means just before OP_Halt. Update of virtual tables is
treated separately so it could be easy adjusted for consistency.
-- best regards
Cezary H. Noweta
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
