On Thu, 04 Jul 2013 16:08:38 -0400 Igor Tandetnik <i...@tandetnik.org> wrote:
> 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. Why not simply open a separate connection, and allow the library to do its job? Many, many applications choose to do what you describe, even though it's usually a terrible choice from the point of view of transactionality or performance. No other DBMS I know of willingly allows a single process to corrupt the results of a SELECT statement by calling other functions. --jkl _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
