Changes between Initial Version and Version 1 of Ticket #19775


Ignore:
Timestamp:
Feb 8, 2013, 4:01:09 AM (12 years ago)
Author:
Claude Paroz
Comment:

I think that not depending on a specific database alias might be a desirable goal for the future. However, this will need some more cleanup regarding django.db.connection (see for example #13528).

Meanwhile, updating the documentation seems the right thing to do at short term.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #19775

    • Property Triage Stage Unreviewed → Accepted

  • Ticket #19775 – Description

    initial v1  
    33https://docs.djangoproject.com/en/1.4/topics/db/multi-db/#defining-your-databases
    44
    5 """
     5''
    66... Django uses the database with the alias of default when no other database has been selected. If you don’t have a default database, you need to be careful to always specify the database that you want to use.
    7 
    8 """
     7''
    98
    109However, when you actually remove, or do not include a "default" and attempt to syncdb with Postgresql, you get the following error that explicitly tells you, that you *must* define a "default" database:
    1110
     11{{{
    1212>python manage.py syncdb
    1313Traceback (most recent call last):
    … …  
    3131    raise ImproperlyConfigured("You must define a '%s' database" % DEFAULT_DB_ALIAS)
    3232django.core.exceptions.ImproperlyConfigured: You must define a 'default' database
    33 
    34 
     33}}}
Back to Top