Re: [pysqlite] Cursor close method

Edzard Pasma wrote:
> Only recently I discovered that a cursor's close method only resets
> it and leaves it open for reuse. This seems useful to prevent locks
> hanging around if not all rows have been fetched. But the recent APSW
> version no longer works like this and the close method really closes
> the cursor. This is intuitively right and appears also according the
> the DB-API2 spec. Is there any chance that pysqlite is going to
> change like this too? Or would this cause compatibility problems, if
> anyone knows? Anyway I will no longer rely on the current behavior,
> and create a new cursor after closing one.

Thank you for bringing this up. I'll change pysqlite so that it behaves
according to the DB-API.

It will probably break some existing code somewhere on the planet, but
not being doc or spec-compliant is a bug for me, so I'll always fix it
(unless the doc or spec is buggy of course).

-- Gerhard