From 6a55b66facfc2d421c796c7c1e1609d67c506df0 Mon Sep 17 00:00:00 2001 From: Andreu Vallbona Date: Sat, 8 Jun 2024 15:57:13 +0200 Subject: [PATCH] code review fixes (III) --- docs/topics/db/models.txt | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/docs/topics/db/models.txt b/docs/topics/db/models.txt index 2a4a7d58df..abd031e853 100644 --- a/docs/topics/db/models.txt +++ b/docs/topics/db/models.txt @@ -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