On 7/4/2013 3:15 PM, James K. Lowden wrote:
This weird case is one of (I would say) misusing the connection. IMO SQLite should return an error if prepare is issued on a connection for which a previous prepare was not finalized or reset. That would forestall discussions like, this and prevent confusion and error.
SQLite worked this way, years ago. At some point, the restriction was removed by popular demand. It is hugely convenient to be able to manipulate one table as you iterate over another. You do have to be careful not to modify the same data you are iterating over, but it's still way better than being unable to make any changes at all. We (the SQLite users) have seen this movie before, and we didn't like it.
-- Igor Tandetnik _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
