You are writing a comment about Replacing Django's ORM with SQLAlchemy, here is a quick summary:
The second example in the Loose Coupling in Django series. This one looks at a place where Django's loose coupling is at its tightest: the Django ORM.
You are responding to this comment written by Siddharta on July 24th 2008, 00:12.
The problem is that all the third party modules/admin interface rely on using the Django ORM. Will it mess up if half the project uses Django's ORM and the other part uses SQLAlchemy?
Please be aware that comment forms go stale after one hour.
Comments may make use of LifeFlow MarkDown. Raw html will be escaped.
Quick Introduction to LifeFlow MarkDown Syntax
A highlighted code block:
Other common languages work as well: scheme, python, java, html, etc.
Other markdown syntax: