This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author erlendaasland
Recipients erlendaasland, ghaering, scorp, serhiy.storchaka
Date 2021-10-18.11:42:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>

  If sqlite3_close_v2() is called with unfinalized prepared statements,
  unclosed BLOB handlers, and/or unfinished sqlite3_backups, it returns
  SQLITE_OK regardless, but instead of deallocating the database connection
  immediately, it marks the database connection as an unusable "zombie" and
  makes arrangements to automatically deallocate the database connection after
  all prepared statements are finalized, all BLOB handles are closed, and all
  backups have finished. The sqlite3_close_v2() interface is intended for use
  with host languages that are garbage collected, and where the order in which
  destructors are called is arbitrary.


  Calling sqlite3_close() or sqlite3_close_v2() with a NULL pointer argument
  is a harmless no-op.
Date User Action Args
2021-10-18 11:42:47erlendaaslandsetrecipients: + erlendaasland, ghaering, serhiy.storchaka, scorp
2021-10-18 11:42:47erlendaaslandsetmessageid: <>
2021-10-18 11:42:47erlendaaslandlinkissue26387 messages
2021-10-18 11:42:47erlendaaslandcreate