Starting new project: database abstraction in Python, best practice for retaining option of MySQL or PostgreSQL without ORM -


i want retain flexibility of switching between mysql , postgresql without awkwardness of using orm - sql fantastic language , retain it's power without additional overhead of orm.

so...is there best practice abstraction database layer of python application provide stated flexibility.

thanks community!

while sqlalchemy great option. there others. if find sqlalchemy not liking here other orms may work out better you. of them more lightweight, may more you're looking for.

http://coobs.eu.org/xrecord/ -- description sounds may looking for. sounds pretty lightweight , database abstraction, seems little outdated.

http://autumn-orm.org/

http://charlesleifer.com/blog/peewee-a-lightweight-python-orm/ -- includes benchmarks pretty basic uses done.

http://elixir.ematia.de/trac/wiki -- built on top of sqlalchemy, has activerecord style syntax. may more liking.

https://storm.canonical.com/frontpage -- orm used canonical.


Comments

Popular posts from this blog

linux - Mailx and Gmail nss config dir -

c# - Is it possible to remove an existing registration from Autofac container builder? -

php - Mysql PK and FK char(36) vs int(10) -