Thread: SQLite version
View Single Post
Old 06-30-2016, 10:20 AM   #4
kovidgoyal
creator of calibre
kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.
 
kovidgoyal's Avatar
 
Posts: 45,445
Karma: 27757438
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
Historically, calibre used to use sqlite3, but I switched to apsw for calibre 1.0 (part of the big database layer rewrite) because it has better performance, and more control over sqlite semantics (apsw is sqlite specific whereas sqlite3 has to conform to the more general DB-API).

Not to mention that one is no longer tied to whatever sqlite is shipped with python.

However, as for your original issue -- I am not aware of any incompatibilities between 3.6 ans 3.7 as long as the db is not using any features that were introduced in 3.7
kovidgoyal is offline   Reply With Quote