On Wed, Feb 10, 2010 at 6:41 PM, PauloS <paulo.scard...@gmail.com> wrote: > Currently it is easy to change the template engine in a Django > project, but if you change the ORM layer you lost the whole Admin > thing, the very app that made Django so special. > > If we are talking about refactoring Admin code (not only html/css > stuff), do you guys think it can be more decoupled from Django ORM? > > Is it possible to design some abstraction middleware to loose the bond > between admin and Django ORM?
Is it possible - almost certainly. After all, you can do anything if you write enough code. However, it's not going to be easy. Django's Admin works by exploiting metadata that the ORM provides. Replacing that metadata source is not going to be a trivial activity. If you want this, *you're* going to have to investigate what changes are required. Proposing that Django adopt a complex abstraction layer to keep from using it's own internal facilities is going to be a hard sell. An approach more likely to succeed is an abstraction layer that lets MyFavouriteORM look like enough like Django's ORM to fool the Admin. Such a tool wouldn't even need to live in Django's core - it could easily live as an external project. So - in summary: It's possibly possible. You're going to have to do the heavy lifting to find out the details. If you can make a concrete proposal that doesn't involve completely rearchitecting Django, we'll consider it. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
