I got the virtual table module which obviously breaks with 3.17 to
work again.
Is there particular cursor behavior which must be provided although an
update is currently or has just been made to the underlying store?
With my new implementation, the existing cursor uses prior data until
it is closed.
What is the correct expectation?
Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
