Anonymous committed aeacf5b

magic-removal: Proofread docs/legacy_databases.txt

  • Participants
  • Parent commits 9e778f8
  • Branches magic-removal

Comments (0)

Files changed (1)

File docs/legacy_databases.txt

 Save this as a file by using standard Unix output redirection::
- inspectdb >
+ inspectdb >
 This feature is meant as a shortcut, not as definitive model generation. See
 the ` documentation`_ for more information.
-Once you've cleaned up the model, put the module in the ``models`` directory of
-your app, and add it to your ``INSTALLED_APPS`` setting.
+Once you've cleaned up your models, name the file ```` and put it in
+the Python package that holds your app. Then add the app to your
+``INSTALLED_APPS`` setting.
 .. documentation:
 Install the core Django tables
-Next, run the `` init`` command to install Django's core tables
-in your database::
+Next, run the `` syncdb`` command to install any extra needed database
+records such as admin permissions and content types:: init
-This won't work if your database already contains tables that have any of the
-following names:
-    * ``django_site``
-    * ``django_content_type``
-    * ``django_sessions``
-    * ``auth_permission``
-    * ``auth_group``
-    * ``auth_user``
-    * ``auth_message``
-    * ``auth_group_permissions``
-    * ``auth_user_groups``
-    * ``auth_user_user_permission``
-If that's the case, try renaming one of your tables to resolve naming
-conflicts. Currently, there's no way of customizing the names of Django's
-database tables without editing Django's source code itself.
-Install metadata about your app
-Django has a couple of database tables that contain metadata about your apps.
-You'll need to execute the SQL output by this command::
- sqlinitialdata [appname]
 See whether it worked