Django to use SQLAlchemy
The Django team has decided to use SQLAlchemy as their database library of choice in future versions of the web framework.
Quoth Adrian:
The Django database API would not change, and the SQLAlchemy backend would be *optional*. The point of the SQLAlchemy backend would be to expose the underlying SQLAlchemy API if you need to do something truly complicated, rather than having to fall into raw SQL.
Additionally…
…this would be an *optional* add-on — the existing model machinery would stay put. I.e., people could still use Django without SQLAlchemy, and that would be the default. I wouldn’t rule out a full migration to SQLAlchemy (i.e., making it default) in the future, but we’d rather not add a dependency at this point.
The SVN branch will be called sqlalchemy if you want to look for it.
Via: SQLAlchemy News
October 9th, 2006 at 7:30 am
[...] A few months ago I read about ORMs and (SQLAlchemy in particular) and decided it was time to start using them in my scripts for database access. I have no problem writing some SQL, but being able to handle database information as objects and getting closer to database independence (e.g. SQLite vs. MySQL) seemed like a good thing. So after hearing about how Django will be including SQLAlchemy in the future, I decided it was time to give it another try. [...]