-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace sqlite with Sqlalchemy #75
Comments
I think that this is overkill and only adds another dependency. |
could we make it optional? try:
import sqlalchemy
database=alchemyDB(path)
except ImportError:
import sqllite3
database=sqliteDB(path) i'd someday like to make a small web app out of this and for that an actual db server would be nice, so i do not have the hassle of making sqlite concurrent but WAL could be a fix for that |
A wrapper for sqlalchemy is definitely an over-overkill. If it's important for you, we can change to sqlalchemy, but this issue should be our lowest priority. |
Or we i could just make a wrapper for mysql/postgresql and we don't have the Overkill anymore |
But yes this is far future for me |
Sqlalchemy is exactly what you use in that case |
This allows us database agnostic SQL programming and enables us to Support multiple SQL flavors out of the Box (sqlite, MySQL,postgresql are the ones i know that are defintively supported)
The text was updated successfully, but these errors were encountered: