FR: Actually raise the exceptions that you are exposing

[sevenrats]

trafficstars

Description

You expose sqlite Errors at the main level but these aren't the ones you actually raise (See core for example, where you raise sqlite3.OperationalError). The implementer is forced to import sqlite3 alongside your package in order to catch this exception but this appears not to be your intention.

occurs on release main branch untested, but looks like it still has the problem.