On Fri, Jun 27, 2008 at 3:06 AM, Will <[EMAIL PROTECTED]> wrote: > Would I have to write an entire new backend for postgres, just to use > a different driver?
You'd need a module that implements the interface of a Django database adapter while using another driver. A few months ago I saw an article by someone who'd been working on a module to use pygresql -- another Python module that can talk to Postgres -- in place of psycopg and who apparently got it partially working before going back to psycopg: http://www.dougblog.com/articles/2008/apr/16/exploring-a-pygresql-backend/ If you're adamantly against using psycopg (I'm not an expert on the comparison, but most Python folks seem to prefer psycopg for its flexibility in allowing customized mappings between Python data types and Postgres data types), you might get in touch with him and see if he still has/is willing to share the code as a starting point for an alternative adapter. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
