mirrors/django
mirrors/django
0
0
Fork 0
mirror of https://github.com/django/django.git synced 2024-11-24 20:07:01 +01:00
Code Issues Releases Wiki Activity

code review fixes (III)

Browse Source
This commit is contained in:
Andreu Vallbona 2024-06-08 15:57:13 +02:00
parent ae301918d3
commit 6a55b66fac
No known key found for this signature in database
GPG Key ID: 6518C0CC0E2BE73D
1 changed files with 4 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/topics/db/models.txt
View File

@ -47,11 +47,9 @@ The above ``Person`` model would create a database table like this:
Some technical notes:
* The name of the table, ``myapp_person``, is automatically derived from
some model metadata but can be overridden, normally are automatically
generated by combining the name of the app (``myapp``) and the lowercase
name of the model (``person``) . See :ref:`table-names` for more
details.
* By default, the name of the table (``myapp_person``) is automatically derived
from model metadata, combining the name of the app (``myapp``) and the lowercase
name of the model (``person``). See :ref:`table-names` for more details.
* An ``id`` field is added automatically, but this behavior can be
overridden. See :ref:`automatic-primary-key-fields`.
@ -66,7 +64,7 @@ Some technical notes:
* It's tailored to the database you're using, so database-specific field types
such as ``auto_increment`` (MySQL), ``bigint PRIMARY KEY GENERATED BY DEFAULT
AS IDENTITY`` (PostgreSQL), or ``integer primary key autoincrement`` (SQLite)
are handled for you automatically. Same goes for the quoting of field names
are handled for you automatically. The same goes for the quoting of field names
-- e.g., using double quotes or single quotes.
Using models