On Fri, Nov 18, 2016 at 3:11 AM, Simon Slavin <slav...@bigfraud.org> wrote:
> Forgot to say ... > > Most of these problems result from attempting to reuse memory you've > already released. Even if the error is happening inside a SQLite routine, > it will be because you passed it a pointer to an SQLite connection which > had already been _close()'d or a statement which had already been > _finalize()'d. > > > Well, the entire process runs under a single connection that is never closed. Although cursors are opened and closed within some of the Python functions, the close is always at the end of the function. And I have no idea how things get finalized under python, or if that's an issue. Anyway, most of the time I use patterns like for row in c1.execute(...) or with dbfile.connect() as conn: and as I understand it, these protect me from most errors of that kind. Moreover, it seems to me that these would all lead to failure at exactly the same point, rather than at three points up to an hour different from each other. I was thinking it more likely to be one of a) random hardware malfunction b) some bug in memory handling that was subject to influence by other activity in the machine) c) some bug in hanling pointers to the python structures (it would have to be a python or sqlite3 bug.) -- #define QUESTION ((bb) || (!bb)) /* Shakespeare */ _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
