On Tuesday, September 10, 2013 6:47:41 AM UTC-4, Dennis wrote: > > Thanks for the advice -- your recommendations against this configuration > were a surprise to me... > It's making me rethink what I want (and how much I want it). > I'll post this as a comment to the first stackoverflow question so others > are made aware. >> >> <https://twitter.com/maugzoide> >> >
Not sure why its a surprise. There's a reason why you don't see SqlAlchemy used in Django. To clarify -- it's entirely possible to use SqlAlchemy or most other ORMs with Django... it's just that many of the core "apps" ( like the automatic admin tools , which is why most people choose to use Django in the first place ) are tightly coupled to the stock ORM. By switching the ORM, you lose most of the automatic admin backend functionalities. This is pretty common knowledge, it's listed on their site in a few places, as well as Stack Overflow and Quora. WIthout the admin tools , and ditching the ORM for SqlAlchemy, I don't see much of a point in using Django. You'd probably have an easier time building and maintaining the same project in Flask or Pyramid. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/groups/opt_out.
