Inner class Meta

In Django this class works like post_meta in WordPress. In Django, it acts as a configuration class and keeps the configuration data in one place. Class Meta is the place in your code logic where your model.fields MEET With your form.widgets. So under Class Meta() you create the link between your model’ fields and the different widgets you want to have in your form.
Model metadata is “anything that’s not a field”, such as ordering options (ordering), database table name (db_table), or human-readable singular and plural names (verbose_name and verbose_name_plural). None are required, and adding class Meta to a model is completely optional.
A complete list of all possible Meta options are in this document (https://docs.djangoproject.com/en/dev/ref/models/options/):
To override the database table name, use the db_table parameter in class Meta.
db_table
db_table = ‘”name_left_in_lowercase”‘
app_label
app_label = ‘myapp’
base_manager_name
db_tablespace
default_manager_name
default_related_name
get_latest_by
managed
order_with_respect_to
ordering
permissions (Defaults to (‘add’, ‘change’, ‘delete’, ‘view’)
proxy
required_db_features
required_db_vendor
indexes
unique_together
index_together
constraints
verbose_name
verbose_name_plural
label
label_lower