On Thu, Nov 22, 2012 at 7:34 AM, Alexandra Paredes <[email protected]> wrote:
> Good afternoon, > > I'm an student of Computer Engineering from Simón Bolívar University, in > Caracas Venezuela. I'm working with a friend on a thesis about ORM and > their "respectfulness" on databases.For a better understanding of Django > ORM, we tried to read the code itself as subject by Russ Magee on an > email, but know we're wondering what would it be the consequences of not > working with Django ORM, What features of the framework may be affected. > > The only things that will be affected are things that need to access the database. Anything else -- request handling, form handling, caching, sending mail, and so on -- will continue to work fine. I've even heard of people using Django's requests and views, but using SQLAlchemy or NoSQL libraries for data store access. The side effect of this will be that you lose the benefits of the most of the ecosystem of Django apps -- for example, you won't even be able to use the contrib auth or admin apps unless you're using the ORM -- but that's just because they need to store and/or access data in a database. Django's ORM provides a common language for data access that 3rd party apps can rely on; if you're not going to use that common language, you're going to need to build a lot on your own. So - the short version -- the ORM is only used to access and modify data in a database. As long as you're not doing that, you don't need to use the ORM. However, most websites will be accessing a data store at some time, in practice, this is a pretty big limitation. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
