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 peewee import * db = SqliteDatabase('people.db') class Person(Model): name = CharField() birthday = DateField() is_relative = BooleanField() 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

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 peewee import * db = SqliteDatabase('people.db') class Person(Model): name = CharField() birthday = DateField() is_relative = BooleanField() 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

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 peewee import * db = SqliteDatabase('people.db') class Person(Model): name = CharField() birthday = DateField() is_relative = BooleanField() 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 peewee import * db = SqliteDatabase('people.db') class Person(Model): name = CharField() birthday = DateField() is_relative = BooleanField() 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

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 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" database. Note: 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