nPostProcessor Customizing configuration metadata with a BeanFactoryPostProcessor Example: the Class name substitution PropertyPlaceholderConfigurer Example: the PropertyOverrideConfigurer Customizing AnnotationConfigApplicationContext Simple construction Building the container programmatically using register(Class… ) Enabling component scanning with scan(String… ) Support for web applications with Annotatio methods Combining Java and XML configuration XML-centric use of @Configuration classes @Configuration class-centric use of XML with @ImportResource Environment abstraction Bean definition profiles @Profile

nPostProcessor Customizing configuration metadata with a BeanFactoryPostProcessor Example: the Class name substitution PropertyPlaceholderConfigurer Example: the PropertyOverrideConfigurer Customizing AnnotationConfigApplicationContext Simple construction Building the container programmatically using register(Class… ) Enabling component scanning with scan(String… ) Support for web applications with Annotati methods Combining Java and XML configuration XML-centric use of @Configuration classes @Configuration class-centric use of XML with @ImportResource Environment abstraction Bean definition profiles @Profile

Model classes, fields and model instances all map to database concepts: Thing Corresponds to… Model class Database table Field instance Column on a table Model instance Row in a database table When starting import * db = SqliteDatabase('people.db') class Person(Model): name = CharField() birthday = DateField() is_relative = BooleanField() class Meta: database = db # This model uses convention you should follow – even though the table will contain multiple people, we always name the class using the singular form. There are lots of field types suitable for storing various types of data

classes, fields and model instances all map to database concepts: Object Corresponds to… Model class Database table Field instance Column on a table Model instance Row in a database table When starting import * db = SqliteDatabase('people.db') class Person(Model): name = CharField() birthday = DateField() is_relative = BooleanField() class Meta: database = db # This model uses convention you should follow – even though the table will contain multiple people, we always name the class using the singular form. There are lots of field types suitable for storing various types of data

classes, fields and model instances all map to database concepts: Object Corresponds to… Model class Database table Field instance Column on a table Model instance Row in a database table When starting import * db = SqliteDatabase('people.db') class Person(Model): name = CharField() birthday = DateField() is_relative = BooleanField() class Meta: database = db # This model uses convention you should follow – even though the table will contain multiple people, we always name the class using the singular form. There are lots of field types suitable for storing various types of data

classes, fields and model instances all map to database concepts: Object Corresponds to… Model class Database table Field instance Column on a table Model instance Row in a database table When starting import * db = SqliteDatabase('people.db') class Person(Model): name = CharField() birthday = DateField() is_relative = BooleanField() class Meta: database = db # This model uses convention you should follow – even though the table will contain multiple people, we always name the class using the singular form. There are lots of field types suitable for storing various types of data

classes, fields and model instances all map to database concepts: Object Corresponds to… Model class Database table Field instance Column on a table Model instance Row in a database table When starting classes: from peewee import * db = SqliteDatabase('people.db') class Person(Model): name = CharField() birthday = DateField() class Meta: database = db # This model uses the "people.db" convention you should follow – even though the table will contain multiple people, we always name the class using the singular form. There are lots of field types suitable for storing various types of data

classes, fields and model instances all map to database concepts: Object Corresponds to… Model class Database table Field instance Column on a table Model instance Row in a database table When starting import * db = SqliteDatabase('people.db') class Person(Model): name = CharField() birthday = DateField() is_relative = BooleanField() class Meta: database = db # This model uses convention you should follow – even though the table will contain multiple people, we always name the class using the singular form. There are lots of field types suitable for storing various types of data

Django template language Class-based views Introduction to class-based views Built-in class-based generic views Form handling with class-based views Using mixins with class-based views Basic examples send_mass_mail() mail_admins() mail_managers() Examples Preventing header injection The EmailMessage class Email backends Configuring email for development Internationalization and localization Overview checks contrib app checks Built-in class-based views API Base views Generic display views Generic editing views Generic date views Class-based views mixins Class-based generic views - flattened index

Support for template engines Class-based views Introduction to class-based views Built-in class-based generic views Form handling with class-based views Using mixins with class-based views Basic examples examples Usage in your URLconf Subclassing generic views Asynchronous class-based views Migrations The Commands Backend Support Workflow Transactions Dependencies Migration files Adding migrations to apps Reversing send_mass_mail() mail_admins() mail_managers() Examples Preventing header injection The EmailMessage class Email backends Configuring email for development Internationalization and localization Overview