Pankaj D added the comment:
Wondering the same thing myself, and yes sqlite3_column_type() by itself
doesn't seem expensive. I assumed in general it was to allow more
responsiveness for apps with huge number of columns (i.e. large tuple size).
But we have about 20-25 columns and so
Pankaj D added the comment:
I believe I have found the root-cause for this issue.
It is occurring due to the use of the garbage collector in another
“memMonitor” thread (we run it periodically to get stats on objects, track mem
leaks, etc). Since _pysqlite_fetch_one_row() releases the
Pankaj D added the comment:
sorry, 2.7, 3.2 is not an option currently but I am hoping someone can
provide enough info to help probe this more efficiently. There seem to be
references to this issue on the web but no root-cause.
--
___
Python
New submission from Pankaj D :
Hi,
Sporadically, while running an sqlite3 query, the above error is seen.
In order to debug, I modified Objects/tupleobject.c, PyTuple_SetItem() as
follows:
if (!PyTuple_Check(op) || op->ob_refcnt != 1) {
Py_XDECREF(newi
