model tables Model options and table metadata Indexes and Constraints Non-integer Primary Keys, Composite Keys and other Tricks Self-referential foreign keys Circular foreign key dependencies Querying unique = False – boolean indicating whether to create a unique index on this column. See also adding composite indexes. verbose_name = None – string representing the “user-friendly” name of this field help_text either a CompositeKey or to indicate that the model has no primary key. Composite primary keys are discussed in more detail here: Composite primary keys. To indicate that a model should not have a primary key

unique = False – boolean indicating whether to create a unique index on this column. See also adding composite indexes. • verbose_name = None – string representing the “user-friendly” name of this field • either a CompositeKey or to indicate that the model has no primary key. Composite primary keys are discussed in more detail here: Composite primary keys. To indicate that a model should not have a primary key table definition when the schema is created. For instance, suppose you have a people table with a composite primary key of two columns, the person’s first and last name. You wish to have another table relate

model tables Model options and table metadata Indexes and Constraints Non-integer Primary Keys, Composite Keys and other Tricks Self-referential foreign keys Circular foreign key dependencies Querying an index on this column unique = False – create a unique index on this column. See also adding composite indexes. column_name = None – explicitly specify the column name in the database. default = None either a CompositeKey or to indicate that the model has no primary key. Composite primary keys are discussed in more detail here: Composite primary keys. To indicate that a model should not have a primary key

model tables Model options and table metadata Indexes and Constraints Non-integer Primary Keys, Composite Keys and other Tricks Self-referential foreign keys Circular foreign key dependencies Querying unique = False – boolean indicating whether to create a unique index on this column. See also adding composite indexes. column_name = None – string representing the underlying column to use if different, useful either a CompositeKey or to indicate that the model has no primary key. Composite primary keys are discussed in more detail here: Composite primary keys. To indicate that a model should not have a primary key

model tables Model options and table metadata Indexes and Constraints Non-integer Primary Keys, Composite Keys and other Tricks Self-referential foreign keys Circular foreign key dependencies Querying unique = False – boolean indicating whether to create a unique index on this column. See also adding composite indexes. column_name = None – string representing the underlying column to use if different, useful either a CompositeKey or to indicate that the model has no primary key. Composite primary keys are discussed in more detail here: Composite primary keys. To indicate that a model should not have a primary key

model tables Model options and table metadata Indexes and Constraints Non-integer Primary Keys, Composite Keys and other Tricks Self-referential foreign keys Circular foreign key dependencies Querying an index on this column unique = False – create a unique index on this column. See also adding composite indexes. column_name = None – explicitly specify the column name in the database. default = None either a CompositeKey or to indicate that the model has no primary key. Composite primary keys are discussed in more detail here: Composite primary keys. To indicate that a model should not have a primary key

model tables Model options and table metadata Indexes and Constraints Non-integer Primary Keys, Composite Keys and other Tricks Self-referential foreign keys Circular foreign key dependencies Querying unique = False – boolean indicating whether to create a unique index on this column. See also adding composite indexes. column_name = None – string representing the underlying column to use if different, useful either a CompositeKey or to indicate that the model has no primary key. Composite primary keys are discussed in more detail here: Composite primary keys. To indicate that a model should not have a primary key

index on this column • unique = False – create a unique index on this column. See also adding composite indexes. • column_name = None – explicitly specify the column name in the database. • default either a CompositeKey or to indicate that the model has no primary key. Composite primary keys are discussed in more detail here: Composite primary keys. To indicate that a model should not have a primary key table definition when the schema is created. For instance, suppose you have a people table with a composite primary key of two columns, the person’s first and last name. You wish to have another table relate

unique = False – boolean indicating whether to create a unique index on this column. See also adding composite indexes. • column_name = None – string representing the underlying column to use if different, either a CompositeKey or to indicate that the model has no primary key. Composite primary keys are discussed in more detail here: Composite primary keys. To indicate that a model should not have a primary key table definition when the schema is created. For instance, suppose you have a people table with a composite primary key of two columns, the person’s first and last name. You wish to have another table relate

unique = False – boolean indicating whether to create a unique index on this column. See also adding composite indexes. • column_name = None – string representing the underlying column to use if different, either a CompositeKey or to indicate that the model has no primary key. Composite primary keys are discussed in more detail here: Composite primary keys. To indicate that a model should not have a primary key table definition when the schema is created. For instance, suppose you have a people table with a composite primary key of two columns, the person’s first and last name. You wish to have another table relate