3 ms·
> For example, everyone says you can 'use SQLAlchemy' in Django. On paper this is true. But then you lose the admin, the user auth system, the messages system,
by henriklied 16y ago
> For example, everyone says you can 'use SQLAlchemy' in Django. On paper this is true. But then you lose the admin, the user auth system, the messages system, model forms, and all of the other batteries that make Django useful.
Using SQLAlchemy doesn't change any of that. For pre-built components, like auth and admin, just go with the flow. You're free to use SQLAlchemy side-by-side with Django's ORM.
- stevenwei 16y agoReally? What happens when you want to start customizing the User model, perhaps linking it to a UserProfile. Perhaps you want to have many Users belong to the same Account? Do you create duplicate representations of your models in SQLAlchemy and Django? What happens when you need to start migrating your database schemas? Forgive my lack of imagination, but I can't think of any way of doing what you suggest without it coming across like a horrible hack.