On Dec 14, 2007 7:44 PM, James Bennett <[EMAIL PROTECTED]> wrote: > > On Dec 14, 2007 5:55 PM, Empty <[EMAIL PROTECTED]> wrote: > > As an aside, if the database backends were truly pluggable, like > > sessions, then we could prove the stability, usability, and commitment > > of the implementation without core commitment ahead of time. A brief > > search showed that this was discussed here: > > As I've already said, you can write a database backend, right now, and > use it with Django, right now, without needing it to be part of Django > itself. The DATABASE_BACKEND setting will -- in addition to the named > backends which ship with Django -- accept a dotted Python path to a > backend module and use that. All you need to do is write the code.
I didn't read that from your original post and the investigating I did I did not find that, so that's great to know. Thanks so much. Michael Trier blog.michaeltrier.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
