On Jan 8, 8:43 am, Venkatraman S <venka...@gmail.com> wrote: > On Sun, Jan 8, 2012 at 9:49 AM, Chen Xu <xuche...@gmail.com> wrote: > > > Since Django has its own database schema, can we still use sqlalchemy > > instead? > > Just to correct the nomeclature : Django has an ORM, and *NOT* a database > schema. An application has its own schema. > And to answer the 'modified' Q : django's orm is pretty good. (but yes, i > would expect that you can swap it with sqlalchemy, but I havent done it > yet). > > -Vhttp://blizzardzblogs.blogspot.com/
To add to what the above poster said, the blog irrational exuberance has an entire series on django's loose coupling philosophy. <a href='http://lethain.com/replacing-django-s-orm-with-sqlalchemy/'>This article</a> is on using SQLAlchemy. I've really been considering switching over to jinja based on his articles (since it seems like it won't break anything, other than all my render_to_response and will need to longform the return render). For my money, django's ORM seems to do a pretty good job. I haven't yet said to myself "wow, it would be nice if it did X" but I say that all the time to myself about the templating engine (which is why I'm considering the switch). -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
