Re: How do I manage a Non-default Django PostgreSQL database

# UPDATE One of my issues is that my router code was based on and older version of Django. I am not sure if this is exactly correct now but it closely resembles the documentation now: https://docs.djangoproject.com/en/1.8/topics/db/multi-db/ class fbrPostHasteAppV0_1Router(object):

Re: How do I manage a Non-default Django PostgreSQL database

On 04/09/2015 07:12 AM, Stephen M wrote: > If Django migrations with PostgreSQL is a bit flaky (as suggested by > S.O. comment) which backend database is reliably supported by the Django > migrations mechanism? The premise is false. Postgres is almost certainly the best-supported database for Djan

Re: How do I manage a Non-default Django PostgreSQL database

If Django migrations with PostgreSQL is a bit flaky (as suggested by S.O. comment) which backend database is reliably supported by the Django migrations mechanism? On Wednesday, April 8, 2015 at 7:53:11 PM UTC-5, Stephen M wrote: > > Also posted to stackoverflow: How do I manage a Non-default Dj

Re: How do I manage a Non-default Django PostgreSQL database

If Django migrations with PostgreSQL is a bit flaky (as suggested by S.O. comment) which backend database is reliably supported by the Django migrations mechanism? -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group