The major problem is: everything in Django is mapped to the ORM. Even the sessions. Sorry for being negative but that is my way to understand this.
2013/9/9 Jonathan Vanasco <jonat...@findmeon.com> > Honestly, I wouldn't do this. > > Django has a lot of "magic" under the hood, and it's ORM does some very > specific things to make this magic happen. It's not just the auth, it's > how everything is structured in the database and how the app integrates > with the database. You're likely to break things and be miserable. Django > , Rails, etc are "all-in" frameworks -- they provide a stack with several > decisions made for you; it's all or nothing. > > I'd personally suggest you either: > > - Continue using Django with their ORM. Create a secondary model that > uses SqlAlchemy to reflect the Django mapping. That will let you use > SqlAlchemy to do advanced read queries. > > - Use a different framework ( Pyramid, Flask, etc ; many have auth plugins > that work with SqlAlchemy models ) > > > -- > 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 sqlalchemy+unsubscr...@googlegroups.com. > To post to this group, send email to sqlalchemy@googlegroups.com. > Visit this group at http://groups.google.com/group/sqlalchemy. > For more options, visit https://groups.google.com/groups/opt_out. > -- *Mauricio de Abreu Antunes* * * Github: https://github.com/mauricioabreu Twitter: https://twitter.com/maugzoide -- 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 sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/groups/opt_out.
