模型是您的数据唯一而且准确的信息来源。它包含您正在储存的数据的重要字段和行为。一般来说，每一个模型都映射一个数据库表。
\n基础：
\n每个模型都是一个 Python 的类，这些类继承 django.db.models.Model
模型类的每个属性都相当于一个数据库的字段。
综上诉说，Django 给你一个自动生成访问数据库的 API；请参阅 进行查询。
这个样例模型定义了一个 Person, 其拥有 first_name 和 last_name:
from django.db import models\n\nclass Person(models.Model):\n first_name = models.CharField(max_length=30)\n last_name = models.CharField(max_length=30)\nfirst_name 和 last_name 是模型的字段。每个字段都被指定为一个类属性，并且每个属性映射为一个数据库列。
上面的 Person 模型会创建一个如下的数据库表：
CREATE TABLE myapp_person (\n "id" serial NOT NULL PRIMARY KEY,\n "first_name" varchar(30) NOT NULL,\n "last_name" varchar(30) NOT NULL\n);\n一些技术上的说明：
\n该表的名称 “myapp_person” 是自动从某些模型元数据中派生出来，但可以被改写。有关更多详细信息，请参阅：表命名。
一个 id 字段会被自动添加，但是这种行为可以被改写。请参阅：默认主键字段。
The CREATE TABLE SQL in this example is formatted using PostgreSQL\nsyntax, but it's worth noting Django uses SQL tailored to the database\nbackend specified in your settings file.
一旦你定义了你的模型，你需要告诉 Django 你准备*使用*这些模型。你需要修改设置文件中的 INSTALLED_APPS ，在这个设置中添加包含你 models.py 文件的模块的名字。
例如，如果模型位于你项目中的``myapp.models``中（ 此包结构使用:djadmin:manage.py startapp`命令创建），:setting:`INSTALLED_APPS 应设置如下:
\nINSTALLED_APPS = [\n #...\n 'myapp',\n #...\n]\n当你向 INSTALLED_APPS 添加新的应用的时候，请务必运行:djadmin:manage.py migrate <migrate>，此外你也可以先使用以下命令先进行迁移 manage.py makemigrations。
模型中最重要的、并且也是唯一必须的是数据库的字段定义。字段在类中定义。定义字段名时应小心避免使用与 models API</ref/models/instances>冲突的名称， 如 ``clean`, save, or ``delete``等.
举例：
\nfrom django.db import models\n\nclass Musician(models.Model):\n first_name = models.CharField(max_length=50)\n last_name = models.CharField(max_length=50)\n instrument = models.CharField(max_length=100)\n\nclass Album(models.Model):\n artist = models.ForeignKey(Musician, on_delete=models.CASCADE)\n name = models.CharField(max_length=100)\n release_date = models.DateField()\n num_stars = models.IntegerField()\n模型中每一个字段都应该是相应类的实例， Django 利用这些字段类来实现下面这些功能。
\n字段类型用以指定数据库数据类型（如：INTEGER, VARCHAR, TEXT）
默认的HTML表单输入框</ref/forms/widgets>（如：<input type="text"><select>）
用于Django admin和自动生成表单的基本验证。
Django内置了多种字段类型；你可以在模型字段参考<model-field-types>中看到完整列表。如果Django内置类型不能满足你的需求，你可以很轻松地编写自定义的字段类型；见:doc:/howto/custom-model-fields。
\n每一种字段都需要指定一些特定的参数（参考 model field reference<model-field-types> ） 例如： :class:`~django.db.models.CharField （以及它的子类）需要接收一个 max_length 参数，用以指定数据库存储数据时用的 VARCHAR 大小。
一些可选的参数是通用的，可以用于任何字段类型，详情请见 :ref:`reference<common-model-field-options> ` ，下面介绍一部分经常用到的通用参数：
\nnull如果设置为 True ， 当该字段为空时，Django会将数据库中该字段设置为 NULL 。默认为 False 。
blank如果设置为 True ，该字段允许为空。默认为 False 。
注意该选项与 False 不同， null 选项仅仅是数据库层面的设置，然而 blank 是涉及表单验证方面。如果一个字段设置为 blank=True ，在进行表单验证时，接收的数据该字段值允许为空，而设置为 blank=False 时，不允许为空。
choices该参数接收一个可迭代的列表或元组（基本单位为二元组）。如果指定了该参数，在实例化该模型时，该字段只能取选项列表中的值。
\n一个选项列表：
\nYEAR_IN_SCHOOL_CHOICES = (\n ('FR', 'Freshman'),\n ('SO', 'Sophomore'),\n ('JR', 'Junior'),\n ('SR', 'Senior'),\n ('GR', 'Graduate'),\n)\n每个二元组的第一个值会储存在数据库中，而第二个值将只会用于显示作用。
\n对于一个模型实例，要获取该字段二元组中相对应的第二个值，使用 get_FOO_display() 方法。例如：
from django.db import models\n\nclass Person(models.Model):\n SHIRT_SIZES = (\n ('S', 'Small'),\n ('M', 'Medium'),\n ('L', 'Large'),\n )\n name = models.CharField(max_length=60)\n shirt_size = models.CharField(max_length=1, choices=SHIRT_SIZES)\n>>> p = Person(name="Fred Flintstone", shirt_size="L")\n>>> p.save()\n>>> p.shirt_size\n'L'\n>>> p.get_shirt_size_display()\n'Large'\ndefault该字段的默认值。可以是一个值或者是个可调用的对象，如果是个可调用对象，每次实例化模型时都会调用该对象。
\nhelp_textExtra "help" text to be displayed with the form widget. It's useful for\ndocumentation even if your field isn't used on a form.
\nprimary_key如果设置为 True ，将该字段设置为该模型的主键。
在一个模型中，如果你没有对任何一个字段设置 primary_key=True 选项。 Django 会自动添加一个 IntegerField 字段，用于设置为主键，因此除非你想重写 Django 默认的主键设置行为，你可以不手动设置主键。详情请见 自动设置主键 。
主键字段是只可读的，如果你修改一个模型实例该字段的值并保存，你将等同于创建了一个新的模型实例。例如：
\nfrom django.db import models\n\nclass Fruit(models.Model):\n name = models.CharField(max_length=100, primary_key=True)\n>>> fruit = Fruit.objects.create(name='Apple')\n>>> fruit.name = 'Pear'\n>>> fruit.save()\n>>> Fruit.objects.values_list('name', flat=True)\n<QuerySet ['Apple', 'Pear']>\nunique如果设置为 True，这个字段必须在整个表中保持值唯一。
再次声明，以上只是一些通用参数的简略描述。你可以在 :ref:`common model field option reference<common-model-field-options> ` 中找到完整的介绍。
\n默认情况下， Django 会给每一个模型添加下面的字段：
\nid = models.AutoField(primary_key=True)\n这是一个自增的主键。
\n如果你想指定设置为为主键的字段， 在你想要设置为主键的字段上设置 primary_key=True 选项。如果 Django 看到你显式的设置了 Field.primary_key ，将不会自动在表（模型）中添加 id 列。
每个模型都需要拥有一个设置了 primary_key=True 的字段（无论是显式的设置还是 Django 自动设置）。
除了 ForeignKey ， ManyToManyField 和 OneToOneField ，任何字段类型都接收一个可选的参数 verbose_name ，如果未指定该参数值， Django 会自动使用该字段的属性名作为该参数值，并且把下划线转换为空格。
在该例中：备注名为 "person's first name":: 。
first_name = models.CharField("person's first name", max_length=30)\n在该例中：备注名为 "first name":: 。
first_name = models.CharField(max_length=30)\nForeignKey, ManyToManyField and OneToOneField 接收的第一个参数为模型的类名，后面可以添加一个 verbose_name 参数：
poll = models.ForeignKey(\n Poll,\n on_delete=models.CASCADE,\n verbose_name="the related poll",\n)\nsites = models.ManyToManyField(Site, verbose_name="list of sites")\nplace = models.OneToOneField(\n Place,\n on_delete=models.CASCADE,\n verbose_name="related place",\n)\n一般情况下不需要将 verbose_name 值首字母大写，必要时 Djanog 会自动把首字母转换为大写。
显然，关系型数据库的强大之处在于各表之间的关联关系。 Django 提供了定义三种最常见的数据库关联关系的方法：多对一，多对多，一对一。
\n定义一个多对一的关联关系，使用 django.db.models.ForeignKey 类。就和其他 Field 字段类型一样，只需要在你模型中添加一个值为该类的属性。
ForeignKey requires a positional argument: the class\nto which the model is related.
例如，如果一个 Car 模型 有一个制造者 Manufacturer --就是说一个 Manufacturer 制造许多辆车，但是每辆车都属于某个特定的制造者-- 那么使用下面的方法定义这个关系：
from django.db import models\n\nclass Manufacturer(models.Model):\n # ...\n pass\n\nclass Car(models.Model):\n manufacturer = models.ForeignKey(Manufacturer, on_delete=models.CASCADE)\n # ...\n你也可以创建一个 recursive relationships 关系（一个模型与它本身有多对一的关系）和 :ref:`relationships to models not yet defined <lazy-relationships> ` ；详情请见 :ref:`the model field reference <ref-foreignkey> ` 。
\n建议设置 ForeignKey 字段（上例中的 manufacturer ）名为想要关联的模型名，但是你也可以随意设置为你想要的名称，例如：
class Car(models.Model):\n company_that_makes_it = models.ForeignKey(\n Manufacturer,\n on_delete=models.CASCADE,\n )\n # ...\n定义一个多对多的关联关系，使用 django.db.models.ManyToManyField 类。就和其他 Field 字段类型一样，只需要在你模型中添加一个值为该类的属性。
ManyToManyField requires a positional argument: the\nclass to which the model is related.
例如：如果 Pizza 含有多种 Topping``（配料） -- 也就是一种 ``Topping 可能存在于多个 Pizza 中，并且每个 Pizza 含有多种 Topping --那么可以这样表示这种关系：
from django.db import models\n\nclass Topping(models.Model):\n # ...\n pass\n\nclass Pizza(models.Model):\n # ...\n toppings = models.ManyToManyField(Topping)\n和 ForeignKey 类一样，你也可以创建 recursive relationships 关系（一个对象与他本身有着多对多的关系）和 relationships to models not yet defined 关系。
建议设置 ManyToManyField 字段（上例中的 toppings ）名为一个复数名词，表示所要光联的模型对象的集合。
对于多对多光联关系的两个模型，可以在任何一个模型中添加 ManyToManyField 字段，但只能选择一个模型设置该字段，即不能同时在两模型中添加该字段。
一般来讲，应该把 ManyToManyField 实例放到需要在表单中被编辑的对象中。在之前的例子中， toppings 被放在 Pizza 当中（而不是 Topping 中有指向 pizzas 的 ManyToManyField 实例 ）因为相较于配料被放在不同的披萨当中，披萨当中有很多种配料更加符合常理。按照先前说的，在编辑 Pizza 的表单时用户可以选择多种配料。
ManyToManyField fields also accept a number of\nextra arguments which are explained in the model field reference. These options help define how the relationship\nshould work; all are optional.
如果你只是想要一个类似于记录披萨和配料之间混合和搭配的简单多对多关系，标准的 ManyToManyField 就足够你用了。然而，有的时候你可能会需要在两个模型的关系中记录更多的数据。
举例来讲，考虑一个需要跟踪音乐人属于哪个音乐组的应用程序。在人和他们所在的组之间有一个多对多关系，你可以使用 ManyToManyField 来代表这个关系。然而，你想要记录更多的信息在这样的所属关系当中，比如你想要记录某人是何时加入一个组的。
对于这些情况，Django允许你指定用于控制多对多关系的模型。你可以在中间模型当中添加而外的字段。在实例化 ManyToManyField 的时候使用 through 参数指定多对多关系使用哪个中间模型。对于我们举的音乐家的例子，代码如下：
from django.db import models\n\nclass Person(models.Model):\n name = models.CharField(max_length=128)\n\n def __str__(self):\n return self.name\n\nclass Group(models.Model):\n name = models.CharField(max_length=128)\n members = models.ManyToManyField(Person, through='Membership')\n\n def __str__(self):\n return self.name\n\nclass Membership(models.Model):\n person = models.ForeignKey(Person, on_delete=models.CASCADE)\n group = models.ForeignKey(Group, on_delete=models.CASCADE)\n date_joined = models.DateField()\n invite_reason = models.CharField(max_length=64)\n在设置中间模型的时候，你需要显式地为多对多关系中涉及的模型指定外键。这种显式声明定义了这两个模型之间的关系。
\n在中间模型当中有一些限制条件：
\n你的中间模型要么有且 仅 有一个指向源模型（我们例子当中的 Group ）的外键，要么你必须通过 ManyToManyField.through_fields 参数在多个外键当中手动选择一个外键，如果有多个外健且没有用 through_fields 参数选择一个的话，会出现验证错误。对于指向目标模型（我们例子当中的 Person ）的外键也有同样的限制。
在一个用于描述模型当中自己指向自己的多对多关系的中间模型当中，可以有两个指向同一个模型的外健，但这两个外健分表代表多对多关系（不同）的两端。如果外健的个数 超过 两个，你必须和上面一样指定 through_fields 参数，要不然会出现验证错误。
在定义模型自己指向自己的多对多关系时，如果使用中间模型，你 必须 定义 symmetrical=False （查看 the model field reference）。
现在你已经通过中间模型完成你的 ManyToManyField （例子中的``Membership``），可以开始创建一些多对多关系了。你通过实例化中间模型来创建关系：
>>> ringo = Person.objects.create(name="Ringo Starr")\n>>> paul = Person.objects.create(name="Paul McCartney")\n>>> beatles = Group.objects.create(name="The Beatles")\n>>> m1 = Membership(person=ringo, group=beatles,\n... date_joined=date(1962, 8, 16),\n... invite_reason="Needed a new drummer.")\n>>> m1.save()\n>>> beatles.members.all()\n<QuerySet [<Person: Ringo Starr>]>\n>>> ringo.group_set.all()\n<QuerySet [<Group: The Beatles>]>\n>>> m2 = Membership.objects.create(person=paul, group=beatles,\n... date_joined=date(1960, 8, 1),\n... invite_reason="Wanted to form a band.")\n>>> beatles.members.all()\n<QuerySet [<Person: Ringo Starr>, <Person: Paul McCartney>]>\n和一般的多对多字段不同，你 不能 使用 add()， create()， 或 set() 来创建关系。
>>> # The following statements will not work\n>>> beatles.members.add(john)\n>>> beatles.members.create(name="George Harrison")\n>>> beatles.members.set([john, paul, ringo, george])\n为什么？你不能简单的在 Person 和 Group 之间创立关系 - 你需要指定 Membership 模型当中需要的所有关于此关系的细节信息。因此，在使用中间模型来定义多对多关系的时候这些方法无法使用。创立这种关系的唯一办法是创建中间模型的实例。
remove() 方法也因为同样的原因无法使用。举例来讲，如果通过中间模型定义的自定义中间表没有确保二元祖 (model1, model2) 的唯一，remove() 在被调用的时候没有足够的信息来确定哪一个中间模型需要被删除。
>>> Membership.objects.create(person=ringo, group=beatles,\n... date_joined=date(1968, 9, 4),\n... invite_reason="You've been gone for a month and we miss you.")\n>>> beatles.members.all()\n<QuerySet [<Person: Ringo Starr>, <Person: Paul McCartney>, <Person: Ringo Starr>]>\n>>> # This will not work because it cannot tell which membership to remove\n>>> beatles.members.remove(ringo)\n但是，clear() 方法可以被用来移除一个实例的所有多对多关系：
>>> # Beatles have broken up\n>>> beatles.members.clear()\n>>> # Note that this deletes the intermediate model instances\n>>> Membership.objects.all()\n<QuerySet []>\n一旦你通过创建中间模型创立了多对多关系，你可以执行查询。就和一般的多对多关系一样，你可以使用多对多关联模型的属性来执行查询：
\n# Find all the groups with a member whose name starts with 'Paul'\n>>> Group.objects.filter(members__name__startswith='Paul')\n<QuerySet [<Group: The Beatles>]>\n当你使用中间模型的时候，你也可以查询他的属性：
\n# Find all the members of the Beatles that joined after 1 Jan 1961\n>>> Person.objects.filter(\n... group__name='The Beatles',\n... membership__date_joined__gt=date(1961,1,1))\n<QuerySet [<Person: Ringo Starr]>\n如果你想访问一个关系的信息时你可以直接查询 Membership 模型：
>>> ringos_membership = Membership.objects.get(group=beatles, person=ringo)\n>>> ringos_membership.date_joined\ndatetime.date(1962, 8, 16)\n>>> ringos_membership.invite_reason\n'Needed a new drummer.'\n另一种访问同样信息的方法是通过 Person 对象来查询 ref:many-to-many reverse relationship<m2m-reverse-relationships> ：
>>> ringos_membership = ringo.membership_set.get(group=beatles)\n>>> ringos_membership.date_joined\ndatetime.date(1962, 8, 16)\n>>> ringos_membership.invite_reason\n'Needed a new drummer.'\n使用 OneToOneField 来定义一对一关系。就像使用其他类型的 Field 一样：在模型属性中包含它。
当一个对象以某种方式“扩展”另一个对象时，这对该对象的主键非常有用。
\nOneToOneField 需要一个位置参数：与模型相关的类。
例如，当你要建立一个有关“位置”信息的数据库时，你可能会包含通常的地址，电话等字段。接着，如果你想接着建立一个关于关于餐厅的数据库，除了将位置数据库当中的字段复制到 Restaurant 模型，你也可以将一个指向 Place OneToOneField 放到 Restaurant 当中（因为餐厅“是一个”地点）；事实上，在处理这样的情况时最好使用 inheritance ，它隐含的包括了一个一对一关系。
和 ForeignKey 一样，可以创建 recursive relationship 也可以创建 references to as-yet undefined models 。
OneToOneField 字段还接受一个可选的 parent_link 参数。
OneToOneField 类通常自动的成为模型的主键，这条规则现在不再使用了（然而你可以手动指定 primary_key 参数）。因此，现在可以在单个模型当中指定多个 OneToOneField 字段。
关联另一个应用中的模型是当然可以的。为了实现这一点，在定义模型的文件开头导入需要被关联的模型。接着，接着就可以在其他有需要的模型类当中关联它了。比如：
\nfrom django.db import models\nfrom geography.models import ZipCode\n\nclass Restaurant(models.Model):\n # ...\n zip_code = models.ForeignKey(\n ZipCode,\n on_delete=models.SET_NULL,\n blank=True,\n null=True,\n )\nDjango在模型字段命名方面仅有两个限制。
\n一个字段的名称不能是Python保留字，因为这回导致Python语法错误。比如：
\nclass Example(models.Model):\n pass = models.IntegerField() # 'pass' is a reserved word!\n一个字段名称不能包含连续的多个下划线，原因在于Django查询语法的工作方式。比如：
\nclass Example(models.Model):\n foo__bar = models.IntegerField() # 'foo__bar' has two underscores!\n但是，这些限制是可以被解决的，因为字段名没要求和数据库列名一样。查看 db_column 选项。
SQL保留字，例如 join， where 或 select， 是 可以被用在模型字段名当中的，因为Django在对底层的SQL查询当中清洗了所有的数据库表名和字段名，通过使用特定数据库引擎的引用语法。
如果已经存在的模型字段不能满足你的需求，或者你希望支持一些不太常见的数据库列类型，你可以创建自己的字段类。在 :doc:`/howto/custom-model-fields 中提供了创建自己的字段的各方面内容。
\nMeta 选项Link to this heading#使用内部 Meta类 来给模型赋予元数据，就像：
from django.db import models\n\nclass Ox(models.Model):\n horn_length = models.IntegerField()\n\n class Meta:\n ordering = ["horn_length"]\n verbose_name_plural = "oxen"\n模型的元数据是指“所有不是字段的东西”，比如排序选项（attr:~Options.ordering），数据库表名（db_table），或是人可读的单复数名（verbose_name 和 verbose_name_plural）。都不是必须的，并且在模型当中添加 Meta类 也完全是可选的。
在 model option reference 中列出了 Meta 可使用的全部选项。
objects模型当中最重要的属性是 Manager。它是Django模型和数据库查询操作之间的接口，并且它被用作从数据库当中 retrieve the instances，如果没有指定自定义的 Manager 默认名称是 objects。Manager只能通过模型类来访问，不能通过模型实例来访问。
Define custom methods on a model to add custom "row-level" functionality to your\nobjects. Whereas Manager methods are intended to do\n"table-wide" things, model methods should act on a particular model instance.
This is a valuable technique for keeping business logic in one place -- the\nmodel.
\nFor example, this model has a few custom methods:
\nfrom django.db import models\n\nclass Person(models.Model):\n first_name = models.CharField(max_length=50)\n last_name = models.CharField(max_length=50)\n birth_date = models.DateField()\n\n def baby_boomer_status(self):\n "Returns the person's baby-boomer status."\n import datetime\n if self.birth_date < datetime.date(1945, 8, 1):\n return "Pre-boomer"\n elif self.birth_date < datetime.date(1965, 1, 1):\n return "Baby boomer"\n else:\n return "Post-boomer"\n\n @property\n def full_name(self):\n "Returns the person's full name."\n return '%s %s' % (self.first_name, self.last_name)\nThe last method in this example is a property.
\nThe model instance reference has a complete list\nof methods automatically given to each model.\nYou can override most of these -- see overriding predefined model methods,\nbelow -- but there are a couple that you'll almost always want to define:
\n__str__()A Python "magic method" that returns a string representation of any\nobject. This is what Python and Django will use whenever a model\ninstance needs to be coerced and displayed as a plain string. Most\nnotably, this happens when you display an object in an interactive\nconsole or in the admin.
\nYou'll always want to define this method; the default isn't very helpful\nat all.
\nget_absolute_url()This tells Django how to calculate the URL for an object. Django uses\nthis in its admin interface, and any time it needs to figure out a URL\nfor an object.
\nAny object that has a URL that uniquely identifies it should define this\nmethod.
\nThere's another set of model methods that\nencapsulate a bunch of database behavior that you'll want to customize. In\nparticular you'll often want to change the way save() and\ndelete() work.
You're free to override these methods (and any other model method) to alter\nbehavior.
\nA classic use-case for overriding the built-in methods is if you want something\nto happen whenever you save an object. For example (see\nsave() for documentation of the parameters it accepts):
from django.db import models\n\nclass Blog(models.Model):\n name = models.CharField(max_length=100)\n tagline = models.TextField()\n\n def save(self, *args, **kwargs):\n do_something()\n super().save(*args, **kwargs) # Call the "real" save() method.\n do_something_else()\nYou can also prevent saving:
\nfrom django.db import models\n\nclass Blog(models.Model):\n name = models.CharField(max_length=100)\n tagline = models.TextField()\n\n def save(self, *args, **kwargs):\n if self.name == "Yoko Ono's blog":\n return # Yoko shall never have her own blog!\n else:\n super().save(*args, **kwargs) # Call the "real" save() method.\nIt's important to remember to call the superclass method -- that's\nthat super().save(*args, **kwargs) business -- to ensure\nthat the object still gets saved into the database. If you forget to\ncall the superclass method, the default behavior won't happen and the\ndatabase won't get touched.
It's also important that you pass through the arguments that can be\npassed to the model method -- that's what the *args, **kwargs bit\ndoes. Django will, from time to time, extend the capabilities of\nbuilt-in model methods, adding new arguments. If you use *args,\n**kwargs in your method definitions, you are guaranteed that your\ncode will automatically support those arguments when they are added.
Another common pattern is writing custom SQL statements in model methods and\nmodule-level methods. For more details on using raw SQL, see the documentation\non using raw SQL.
\n模型继承在 Django 中与普通类继承在 Python 中的工作方式几乎完全相同, 但也仍应遵循本页开头的内容. 这意味着其基类应该继承自 django.db.models.Model .
The only decision you have to make is whether you want the parent models to be\nmodels in their own right (with their own database tables), or if the parents\nare just holders of common information that will only be visible through the\nchild models.
\nThere are three styles of inheritance that are possible in Django.
\nOften, you will just want to use the parent class to hold information that\nyou don't want to have to type out for each child model. This class isn't\ngoing to ever be used in isolation, so Abstract base classes are\nwhat you're after.
If you're subclassing an existing model (perhaps something from another\napplication entirely) and want each model to have its own database table,\nMulti-table inheritance is the way to go.
Finally, if you only want to modify the Python-level behavior of a model,\nwithout changing the models fields in any way, you can use\nProxy models.
Abstract base classes are useful when you want to put some common\ninformation into a number of other models. You write your base class\nand put abstract=True in the Meta\nclass. This model will then not be used to create any database\ntable. Instead, when it is used as a base class for other models, its\nfields will be added to those of the child class.
An example:
\nfrom django.db import models\n\nclass CommonInfo(models.Model):\n name = models.CharField(max_length=100)\n age = models.PositiveIntegerField()\n\n class Meta:\n abstract = True\n\nclass Student(CommonInfo):\n home_group = models.CharField(max_length=5)\nThe Student model will have three fields: name, age and\nhome_group. The CommonInfo model cannot be used as a normal Django\nmodel, since it is an abstract base class. It does not generate a database\ntable or have a manager, and cannot be instantiated or saved directly.
Fields inherited from abstract base classes can be overridden with another\nfield or value, or be removed with None.
For many uses, this type of model inheritance will be exactly what you want.\nIt provides a way to factor out common information at the Python level, while\nstill only creating one database table per child model at the database level.
\nMeta inheritanceLink to this heading#When an abstract base class is created, Django makes any Meta\ninner class you declared in the base class available as an\nattribute. If a child class does not declare its own Meta\nclass, it will inherit the parent's Meta. If the child wants to\nextend the parent's Meta class, it can subclass it. For example:
\nfrom django.db import models\n\nclass CommonInfo(models.Model):\n # ...\n class Meta:\n abstract = True\n ordering = ['name']\n\nclass Student(CommonInfo):\n # ...\n class Meta(CommonInfo.Meta):\n db_table = 'student_info'\nDjango does make one adjustment to the Meta class of an abstract base\nclass: before installing the Meta attribute, it sets abstract=False.\nThis means that children of abstract base classes don't automatically become\nabstract classes themselves. Of course, you can make an abstract base class\nthat inherits from another abstract base class. You just need to remember to\nexplicitly set abstract=True each time.
Some attributes won't make sense to include in the Meta class of an\nabstract base class. For example, including db_table would mean that all\nthe child classes (the ones that don't specify their own Meta) would use\nthe same database table, which is almost certainly not what you want.
The second type of model inheritance supported by Django is when each model in\nthe hierarchy is a model all by itself. Each model corresponds to its own\ndatabase table and can be queried and created individually. The inheritance\nrelationship introduces links between the child model and each of its parents\n(via an automatically-created OneToOneField).\nFor example:
from django.db import models\n\nclass Place(models.Model):\n name = models.CharField(max_length=50)\n address = models.CharField(max_length=80)\n\nclass Restaurant(Place):\n serves_hot_dogs = models.BooleanField(default=False)\n serves_pizza = models.BooleanField(default=False)\nAll of the fields of Place will also be available in Restaurant,\nalthough the data will reside in a different database table. So these are both\npossible:
>>> Place.objects.filter(name="Bob's Cafe")\n>>> Restaurant.objects.filter(name="Bob's Cafe")\nIf you have a Place that is also a Restaurant, you can get from the\nPlace object to the Restaurant object by using the lower-case version\nof the model name:
>>> p = Place.objects.get(id=12)\n# If p is a Restaurant object, this will give the child class:\n>>> p.restaurant\n<Restaurant: ...>\nHowever, if p in the above example was not a Restaurant (it had been\ncreated directly as a Place object or was the parent of some other class),\nreferring to p.restaurant would raise a Restaurant.DoesNotExist\nexception.
The automatically-created OneToOneField on\nRestaurant that links it to Place looks like this:
place_ptr = models.OneToOneField(\n Place, on_delete=models.CASCADE,\n parent_link=True,\n)\nYou can override that field by declaring your own\nOneToOneField with parent_link=True on Restaurant.
Meta and multi-table inheritanceLink to this heading#In the multi-table inheritance situation, it doesn't make sense for a child\nclass to inherit from its parent's Meta class. All the Meta options\nhave already been applied to the parent class and applying them again would\nnormally only lead to contradictory behavior (this is in contrast with the\nabstract base class case, where the base class doesn't exist in its own\nright).
\nSo a child model does not have access to its parent's Meta class. However, there are a few limited cases where the child\ninherits behavior from the parent: if the child does not specify an\nordering attribute or a\nget_latest_by attribute, it will inherit\nthese from its parent.
If the parent has an ordering and you don't want the child to have any natural\nordering, you can explicitly disable it:
\nclass ChildModel(ParentModel):\n # ...\n class Meta:\n # Remove parent's ordering effect\n ordering = []\nBecause multi-table inheritance uses an implicit\nOneToOneField to link the child and\nthe parent, it's possible to move from the parent down to the child,\nas in the above example. However, this uses up the name that is the\ndefault related_name value for\nForeignKey and\nManyToManyField relations. If you\nare putting those types of relations on a subclass of the parent model, you\nmust specify the related_name\nattribute on each such field. If you forget, Django will raise a validation\nerror.
For example, using the above Place class again, let's create another\nsubclass with a ManyToManyField:
class Supplier(Place):\n customers = models.ManyToManyField(Place)\nThis results in the error:
\nReverse query name for 'Supplier.customers' clashes with reverse query\nname for 'Supplier.place_ptr'.\n\nHINT: Add or change a related_name argument to the definition for\n'Supplier.customers' or 'Supplier.place_ptr'.\nAdding related_name to the customers field as follows would resolve the\nerror: models.ManyToManyField(Place, related_name='provider').
As mentioned, Django will automatically create a\nOneToOneField linking your child\nclass back to any non-abstract parent models. If you want to control the\nname of the attribute linking back to the parent, you can create your\nown OneToOneField and set\nparent_link=True\nto indicate that your field is the link back to the parent class.
When using multi-table inheritance, a new\ndatabase table is created for each subclass of a model. This is usually the\ndesired behavior, since the subclass needs a place to store any additional\ndata fields that are not present on the base class. Sometimes, however, you\nonly want to change the Python behavior of a model -- perhaps to change the\ndefault manager, or add a new method.
\nThis is what proxy model inheritance is for: creating a proxy for the\noriginal model. You can create, delete and update instances of the proxy model\nand all the data will be saved as if you were using the original (non-proxied)\nmodel. The difference is that you can change things like the default model\nordering or the default manager in the proxy, without having to alter the\noriginal.
\nProxy models are declared like normal models. You tell Django that it's a\nproxy model by setting the proxy attribute of\nthe Meta class to True.
For example, suppose you want to add a method to the Person model. You can do it like this:
from django.db import models\n\nclass Person(models.Model):\n first_name = models.CharField(max_length=30)\n last_name = models.CharField(max_length=30)\n\nclass MyPerson(Person):\n class Meta:\n proxy = True\n\n def do_something(self):\n # ...\n pass\nThe MyPerson class operates on the same database table as its parent\nPerson class. In particular, any new instances of Person will also be\naccessible through MyPerson, and vice-versa:
>>> p = Person.objects.create(first_name="foobar")\n>>> MyPerson.objects.get(first_name="foobar")\n<MyPerson: foobar>\n你仍然可以使用一个代理模型来定义模型的默认排序方法。你也许不会想一直对“Persion”进行排序，但是通常情况下用代理模型根据“last_name”属性进行排序。这很简单:
\nclass OrderedPerson(Person):\n class Meta:\n ordering = ["last_name"]\n proxy = True\nNow normal Person queries will be unordered\nand OrderedPerson queries will be ordered by last_name.
代理模型继承“Meta”属性:ref:和普通模型使用同样的方法<meta-and-multi-table-inheritance>。
\nQuerySets still return the model that was requestedLink to this heading#There is no way to have Django return, say, a MyPerson object whenever you\nquery for Person objects. A queryset for Person objects will return\nthose types of objects. The whole point of proxy objects is that code relying\non the original Person will use those and your own code can use the\nextensions you included (that no other code is relying on anyway). It is not\na way to replace the Person (or any other) model everywhere with something\nof your own creation.
一个代理模型必须仅能继承一个非抽象模型类。你不能继承多个非抽象模型类，因为代理模型无法提供不同数据表的任何行间连接。一个代理模型可以继承任意数量的抽象模型类，假如他们*没有*定义任何的模型字段。一个代理模型也可以继承任意数量的代理模型，只需他们共享同一个非抽象父类。
\nIf you don't specify any model managers on a proxy model, it inherits the\nmanagers from its model parents. If you define a manager on the proxy model,\nit will become the default, although any managers defined on the parent\nclasses will still be available.
\nContinuing our example from above, you could change the default manager used\nwhen you query the Person model like this:
from django.db import models\n\nclass NewManager(models.Manager):\n # ...\n pass\n\nclass MyPerson(Person):\n objects = NewManager()\n\n class Meta:\n proxy = True\nIf you wanted to add a new manager to the Proxy, without replacing the\nexisting default, you can use the techniques described in the custom\nmanager documentation: create a base class\ncontaining the new managers and inherit that after the primary base class:
\n# Create an abstract class for the new manager.\nclass ExtraManagers(models.Model):\n secondary = NewManager()\n\n class Meta:\n abstract = True\n\nclass MyPerson(Person, ExtraManagers):\n class Meta:\n proxy = True\n通常情况下，你可能不需要这么做。然而，你需要的时候，这也是可以的。
\nProxy model inheritance might look fairly similar to creating an unmanaged\nmodel, using the managed attribute on a\nmodel's Meta class.
With careful setting of Meta.db_table you could create an unmanaged model that\nshadows an existing model and adds Python methods to it. However, that would be\nvery repetitive and fragile as you need to keep both copies synchronized if you\nmake any changes.
On the other hand, proxy models are intended to behave exactly like the model\nthey are proxying for. They are always in sync with the parent model since they\ndirectly inherit its fields and managers.
\nThe general rules are:
\nIf you are mirroring an existing model or database table and don't want\nall the original database table columns, use Meta.managed=False.\nThat option is normally useful for modeling database views and tables\nnot under the control of Django.
If you are wanting to change the Python-only behavior of a model, but\nkeep all the same fields as in the original, use Meta.proxy=True.\nThis sets things up so that the proxy model is an exact copy of the\nstorage structure of the original model when data is saved.
Just as with Python's subclassing, it's possible for a Django model to inherit\nfrom multiple parent models. Keep in mind that normal Python name resolution\nrules apply. The first base class that a particular name (e.g. Meta) appears in will be the one that is used; for example, this\nmeans that if multiple parents contain a Meta class,\nonly the first one is going to be used, and all others will be ignored.
\nGenerally, you won't need to inherit from multiple parents. The main use-case\nwhere this is useful is for "mix-in" classes: adding a particular extra\nfield or method to every class that inherits the mix-in. Try to keep your\ninheritance hierarchies as simple and straightforward as possible so that you\nwon't have to struggle to work out where a particular piece of information is\ncoming from.
\nNote that inheriting from multiple models that have a common id primary\nkey field will raise an error. To properly use multiple inheritance, you can\nuse an explicit AutoField in the base models:
class Article(models.Model):\n article_id = models.AutoField(primary_key=True)\n ...\n\nclass Book(models.Model):\n book_id = models.AutoField(primary_key=True)\n ...\n\nclass BookReview(Book, Article):\n pass\nOr use a common ancestor to hold the AutoField. This\nrequires using an explicit OneToOneField from each\nparent model to the common ancestor to avoid a clash between the fields that\nare automatically generated and inherited by the child:
class Piece(models.Model):\n pass\n\nclass Article(Piece):\n article_piece = models.OneToOneField(Piece, on_delete=models.CASCADE, parent_link=True)\n ...\n\nclass Book(Piece):\n book_piece = models.OneToOneField(Piece, on_delete=models.CASCADE, parent_link=True)\n ...\n\nclass BookReview(Book, Article):\n pass\nIn normal Python class inheritance, it is permissible for a child class to\noverride any attribute from the parent class. In Django, this isn't usually\npermitted for model fields. If a non-abstract model base class has a field\ncalled author, you can't create another model field or define\nan attribute called author in any class that inherits from that base class.
This restriction doesn't apply to model fields inherited from an abstract\nmodel. Such fields may be overridden with another field or value, or be removed\nby setting field_name = None.
Overriding fields in a parent model leads to difficulties in areas such as\ninitializing new instances (specifying which field is being initialized in\nModel.__init__) and serialization. These are features which normal Python\nclass inheritance doesn't have to deal with in quite the same way, so the\ndifference between Django model inheritance and Python class inheritance isn't\narbitrary.
This restriction only applies to attributes which are\nField instances. Normal Python attributes\ncan be overridden if you wish. It also only applies to the name of the\nattribute as Python sees it: if you are manually specifying the database\ncolumn name, you can have the same column name appearing in both a child and\nan ancestor model for multi-table inheritance (they are columns in two\ndifferent database tables).
Django will raise a FieldError if you override\nany model field in any ancestor model.
The manage.py startapp command creates an application\nstructure that includes a models.py file. If you have many models,\norganizing them in separate files may be useful.
To do so, create a models package. Remove models.py and create a\nmyapp/models/ directory with an __init__.py file and the files to\nstore your models. You must import the models in the __init__.py file.
For example, if you had organic.py and synthetic.py in the models\ndirectory:
from .organic import Person\nfrom .synthetic import Robot\nExplicitly importing each model rather than using from .models import *\nhas the advantages of not cluttering the namespace, making code more readable,\nand keeping code analysis tools useful.