On 8/30/07, George Vilches <[EMAIL PROTECTED]> wrote: > > Folks, > > Now that the database backend refactoring has landed, and DB > functionality is really easy to extend, how does everyone feel about the > possibility of allowing people to specify their own database backends > within their projects (i.e., without modifying the Django source tree in > any way?) I see this as an excellent way for people to increase their
The broad idea seems reasonable to me. There's no point having an easily pluggable database engine if you can't plug in your own database :-) Regarding the approach - I'm inclined to prefer #1. It's simple and easy to explain, and I don't see that there is that much potential for side effects. The only clash I can forsee is if you had your own toplevel module that mirrored the backend names of Django - this doesn't really strike me as something that will be a common problem, and if it is, the solution is easy (rename the clashing external module). I don't see the point of #2. Any given project settings file will only ever need 1 database backend, so why keep an index of backends in the settings file? DB Backends shouldn't be a project specific thing, so #3 isn't really a good approach. We should be encouraging people to write standalone modules that integrate well with Django as a whole, rather than pushing some sort of 'copy this module into your project' approach. 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 [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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
