diff options
| author | Preston Holmes <preston@ptone.com> | 2012-10-21 07:37:57 -0700 |
|---|---|---|
| committer | Preston Holmes <preston@ptone.com> | 2012-10-21 07:41:59 -0700 |
| commit | 1a3ff63199cd14f772a86090c4546953f3f19343 (patch) | |
| tree | 8828b11369a8953f6d6c7caed172475bd5954462 | |
| parent | 6b3d2bc9810153506620c7794a7a87ade29e3a97 (diff) | |
Updated error message for bad database engine
removing typo in the process. Thanks to Carlos Palol for the catch.
Closes pull 450
| -rw-r--r-- | django/core/management/sql.py | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/django/core/management/sql.py b/django/core/management/sql.py index ac16a5b358..78cd17a23a 100644 --- a/django/core/management/sql.py +++ b/django/core/management/sql.py @@ -17,9 +17,8 @@ def sql_create(app, style, connection): # This must be the "dummy" database backend, which means the user # hasn't set ENGINE for the database. raise CommandError("Django doesn't know which syntax to use for your SQL statements,\n" + - "because you haven't specified the ENGINE setting for the database.\n" + - "Edit your settings file and change DATBASES['default']['ENGINE'] to something like\n" + - "'django.db.backends.postgresql' or 'django.db.backends.mysql'.") + "because you haven't properly specified the ENGINE setting for the database.\n" + + "see: https://docs.djangoproject.com/en/dev/ref/settings/#databases") # Get installed models, so we generate REFERENCES right. # We trim models from the current app so that the sqlreset command does not |
