In a sentence, I'd say apsw is "the SQLite lover's SQLite library". The python stdlib one tries to provide a generic interface ("DBAPI") which is great if you want to be able to swap to a different database engine later, but it's bad for actually getting the most out of SQLite.
This library is great, and recently saved a project of mine. Figuring out what was going on with some of python's sqlite3 quirks was too much of a hassle, meanwhile this more or less just worked the way I expected it to. Because of this experience I started defaulting to it over sqlite3 for other projects as well.
In a sentence, I'd say apsw is "the SQLite lover's SQLite library". The python stdlib one tries to provide a generic interface ("DBAPI") which is great if you want to be able to swap to a different database engine later, but it's bad for actually getting the most out of SQLite.
Why do you say it's bad?
Everything to do with transactions, including nested transactions.
This library is great, and recently saved a project of mine. Figuring out what was going on with some of python's sqlite3 quirks was too much of a hassle, meanwhile this more or less just worked the way I expected it to. Because of this experience I started defaulting to it over sqlite3 for other projects as well.
(This documentation page explains the library's intent: https://rogerbinns.github.io/apsw/pysqlite.html)
what quirks did you bump into with sqlite3?
Thank you HackerNews. I learned something new and will be using APSW for my next Sqlite project.
It’s a great wrapper, but we should add a year. Not exactly new.
The latest commit was 1 hour ago
Abandonware!
ahh. It’s been around a while, but maybe the date convention is for articles not repos.
new to many people, just not you.