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.
I've just found ``Check-in [32be7aae]''
(http://www.sqlite.org/cgi/src/info/32be7aae92ee48bf):
Date: 2016-11-22 01:26:42
User: drh
Comment: Remove unnecessary OP_Close opcodes for a size reduction and
performance increase.
AFAIK, your intention was to remove unnecessary OP_Close (in case of
virtual table cursors). The dangling, problematic OP_Close is at the
very end of ``update.c'' (updateVirtualTable(...)):
sqlite3VdbeAddOp2(v, OP_Close, ephemTab, 0);
-- best regards
Cezary H. Noweta
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
