Fixed #15846 -- Fixed unfinished sentence in django-admin.txt. Thanks, follower

git-svn-id: http://code.djangoproject.com/svn/django/trunk@16049 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Adrian Holovaty 2011-04-20 16:28:02 +00:00
parent 196ac8f8b3
commit 519534bf03
1 changed files with 7 additions and 7 deletions

View File

@ -383,14 +383,14 @@ installation will be aborted, and any data installed in the call to
Database-specific fixtures Database-specific fixtures
~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~
If you are in a multi-database setup, you may have fixture data that If you're in a multi-database setup, you might have fixture data that
you want to load onto one database, but not onto another. In this you want to load onto one database, but not onto another. In this
situation, you can add database identifier into . If your situation, you can add database identifier into the names of your fixtures.
:setting:`DATABASES` setting has a 'master' database defined, you can
define the fixture ``mydata.master.json`` or For example, if your :setting:`DATABASES` setting has a 'master' database
``mydata.master.json.gz``. This fixture will only be loaded if you defined, name the fixture ``mydata.master.json`` or
have specified that you want to load data onto the ``master`` ``mydata.master.json.gz`` and the fixture will only be loaded when you
database. specify you want to load data into the ``master`` database.
makemessages makemessages
------------ ------------