DateTimeField() peewee supports a handful of field types which map to different column types in sqlite. Conversion between python and the database is handled transparently, including the proper handling of None/NULL TextField() # <-- TEXT pub_date = DateTimeField() # <-- DATETIME blog = ForeignKeyField() # <-- INTEGER referencing the Blog table This is a typical example of how to specify models with peewee. There database columns. Each field type has a corresponding SQL storage class (i.e. varchar, int), and conversion between python data types and underlying storage is handled transparently. When creating a Model

DateTimeField() peewee supports a handful of field types which map to different column types in sqlite. Conversion between python and the database is handled transparently, including the proper handling of None/NULL Documentation, Release 0.9.7 pub_date = DateTimeField() # <-- DATETIME blog = ForeignKeyField() # <-- INTEGER referencing the Blog table This is a typical example of how to specify models with peewee. There database columns. Each field type has a corresponding SQL storage class (i.e. varchar, int), and conversion between python data types and underlying storage is handled transparently. When creating a Model

fields and columns Well, for one, columns are gone. They were a shim that I used to hack in non-integer primary keys. I always thought the field SQL generation was one of the grosser parts of the module primary key and it is a PrimaryKeyField (or subclass), it will be an automatically incrementing integer • if you specify a primary key and it is anything else peewee assumes you are in control and will create(username=’somebody’) db.commit() 1.4.4 Non-integer Primary Keys and other Tricks Non-integer primary keys If you would like use a non-integer primary key (which I generally don’t recommend), you

Model methods Fields Field types table Self-referential Foreign Keys Implementing Many to Many Non-integer Primary Keys Field class API Querying API Constructing queries Where clause Performing advanced DateTimeField() peewee supports a handful of field types which map to different column types in sqlite. Conversion between python and the database is handled transparently, including the proper handling of None/NULL TextField() # <-- TEXT pub_date = DateTimeField() # <-- DATETIME blog = ForeignKeyField(Blog) # <-- INTEGER referencing the Blog table This is a typical example of how to specify models with peewee. There

1.0.0 peewee supports a handful of field types which map to different column types in sqlite. Conversion between python and the database is handled transparently, including the proper handling of None/NULL TextField() # <-- TEXT pub_date = DateTimeField() # <-- DATETIME blog = ForeignKeyField(Blog) # <-- INTEGER referencing the Blog table This is a typical example of how to specify models with peewee. There database columns. Each field type has a corresponding SQL storage class (i.e. varchar, int), and conversion between python data types and underlying storage is handled transparently. When creating a Model

Fields Fields Creating 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 different field types which map to different column types commonly supported by database engines. Conversion between python types and those used in the database is handled transparently, allowing you to use Because we have not specified a primary key, peewee will automatically add an auto-incrementing integer primary key field named id. Note If you would like to start using peewee with an existing database

Field-naming conflicts Creating 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 different field types which map to different column types commonly supported by database engines. Conversion between python types and those used in the database is handled transparently, allowing you to use Because we have not specified a primary key, peewee will automatically add an auto-incrementing integer primary key field named id. Note If you would like to start using peewee with an existing database

different field types which map to different column types commonly supported by database engines. Conversion between python types and those used in the database is handled transparently, allowing you to use Because we have not specified a primary key, peewee will automatically add an auto-incrementing integer primary key field named id. Note: If you would like to start using peewee with an existing database database columns. Each field type has a corresponding SQL storage class (i.e. varchar, int), and conversion between python data types and underlying storage is handled transparently. When creating a Model

different field types which map to different column types commonly supported by database engines. Conversion between python types and those used in the database is handled transparently, allowing you to use Because we have not specified a primary key, peewee will automatically add an auto-incrementing integer primary key field named id. Note: If you would like to start using peewee with an existing database database columns. Each field type has a corresponding SQL storage class (i.e. varchar, int), and conversion between python data types and underlying storage is handled transparently. When creating a Model

different field types which map to different column types commonly supported by database engines. Conversion between python types and those used in the database is handled transparently, allowing you to use Because we have not specified a primary key, peewee will automatically add an auto-incrementing integer primary key field named id. Note: If you would like to start using peewee with an existing database database columns. Each field type has a corresponding SQL storage class (i.e. varchar, int), and conversion between python data types and underlying storage is handled transparently. When creating a Model