mirror of
				https://github.com/django/django.git
				synced 2025-11-04 05:35:37 +00:00 
			
		
		
		
	Fixed #25038 -- Reverted incorrect documentation about inspectdb introspecting views.
This reverts commit bd691f4586 (refs #24177).
			
			
This commit is contained in:
		
							parent
							
								
									4352e865a7
								
							
						
					
					
						commit
						9f0d67137c
					
				
					 2 changed files with 5 additions and 13 deletions
				
			
		| 
						 | 
					@ -332,17 +332,17 @@ inspectdb
 | 
				
			||||||
 | 
					
 | 
				
			||||||
.. django-admin:: inspectdb
 | 
					.. django-admin:: inspectdb
 | 
				
			||||||
 | 
					
 | 
				
			||||||
Introspects the database tables and views in the database pointed-to by the
 | 
					Introspects the database tables in the database pointed-to by the
 | 
				
			||||||
:setting:`NAME` setting and outputs a Django model module (a ``models.py``
 | 
					:setting:`NAME` setting and outputs a Django model module (a ``models.py``
 | 
				
			||||||
file) to standard output.
 | 
					file) to standard output.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
Use this if you have a legacy database with which you'd like to use Django.
 | 
					Use this if you have a legacy database with which you'd like to use Django.
 | 
				
			||||||
The script will inspect the database and create a model for each table or view
 | 
					The script will inspect the database and create a model for each table within
 | 
				
			||||||
within it.
 | 
					it.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
As you might expect, the created models will have an attribute for every field
 | 
					As you might expect, the created models will have an attribute for every field
 | 
				
			||||||
in the table or view. Note that ``inspectdb`` has a few special cases in its
 | 
					in the table. Note that ``inspectdb`` has a few special cases in its field-name
 | 
				
			||||||
field-name output:
 | 
					output:
 | 
				
			||||||
 | 
					
 | 
				
			||||||
* If ``inspectdb`` cannot map a column's type to a model field type, it'll
 | 
					* If ``inspectdb`` cannot map a column's type to a model field type, it'll
 | 
				
			||||||
  use ``TextField`` and will insert the Python comment
 | 
					  use ``TextField`` and will insert the Python comment
 | 
				
			||||||
| 
						 | 
					@ -385,11 +385,6 @@ it because ``True`` is its default value).
 | 
				
			||||||
The :djadminopt:`--database` option may be used to specify the
 | 
					The :djadminopt:`--database` option may be used to specify the
 | 
				
			||||||
database to introspect.
 | 
					database to introspect.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
.. versionadded:: 1.8
 | 
					 | 
				
			||||||
 | 
					 | 
				
			||||||
    A feature to inspect database views was added. In previous versions, only
 | 
					 | 
				
			||||||
    tables (not views) were inspected.
 | 
					 | 
				
			||||||
 | 
					 | 
				
			||||||
loaddata <fixture fixture ...>
 | 
					loaddata <fixture fixture ...>
 | 
				
			||||||
------------------------------
 | 
					------------------------------
 | 
				
			||||||
 | 
					
 | 
				
			||||||
| 
						 | 
					
 | 
				
			||||||
| 
						 | 
					@ -424,9 +424,6 @@ Management Commands
 | 
				
			||||||
  introspect :class:`~django.db.models.AutoField` for MySQL and PostgreSQL
 | 
					  introspect :class:`~django.db.models.AutoField` for MySQL and PostgreSQL
 | 
				
			||||||
  databases.
 | 
					  databases.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
* :djadmin:`inspectdb` now introspects database views on all database backends.
 | 
					 | 
				
			||||||
  In previous versions, only tables (not views) were inspected.
 | 
					 | 
				
			||||||
 | 
					 | 
				
			||||||
* When calling management commands from code through :ref:`call_command
 | 
					* When calling management commands from code through :ref:`call_command
 | 
				
			||||||
  <call-command>` and passing options, the option name can match the command
 | 
					  <call-command>` and passing options, the option name can match the command
 | 
				
			||||||
  line option name (without the initial dashes) or the final option destination
 | 
					  line option name (without the initial dashes) or the final option destination
 | 
				
			||||||
| 
						 | 
					
 | 
				
			||||||
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue