keeps track of the connection state using thread-local storage, making the Peewee Database object safe to use with multiple threads. Each thread will have it’s own connection, and as a result any given if your tables already exist, and conditionally create them. If you want to disable this, specify safe=False. After you have created your tables, if you choose to modify your database schema (by adding IntegrityError: # `username` is a unique column, so this username already exists, # making it safe to call .get(). return User.get(User.username == username) You can easily encapsulate this type

keeps track of the connection state using thread-local storage, making the Peewee Database object safe to use with multiple threads. Each thread will have it’s own connection, and conversely, any given if your tables already exist, and conditionally create them. If you want to disable this, specify safe=False. After you have created your tables, if you choose to modify your database schema (by adding IntegrityError: # `username` is a unique column, so this username already exists, # making it safe to call .get(). return User.get(User.username == username) You can easily encapsulate this type

keeps track of the connection state using thread-local storage, making the Peewee Database object safe to use with multiple threads. Each thread will have it’s own connection, and conversely, any given conditionally create them: # Only create the tables if they do not exist. db.create_tables([User, Tweet], safe=True) After you have created your tables, if you choose to modify your database schema (by adding IntegrityError: # `username` is a unique column, so this username already exists, # making it safe to call .get(). return User.get(User.username == username) You can easily encapsulate this type

keeps track of the connection state using thread-local storage, making the Peewee Database object safe to use with multiple threads. Each thread will have it’s own connection, and as a result any given if your tables already exist, and conditionally create them. If you want to disable this, specify safe=False. After you have created your tables, if you choose to modify your database schema (by adding peewee.IntegrityError: # `username` is a unique column, so this username already exists, # making it safe to call .get(). return User.get(User.username == username) You can easily encapsulate this type of

keeps track of the connection state using thread-local storage, making the Peewee Database object safe to use with multiple threads. Each thread will have it’s own connection, and conversely, any given if your tables already exist, and conditionally create them. If you want to disable this, specify safe=False. After you have created your tables, if you choose to modify your database schema (by adding peewee.IntegrityError: # `username` is a unique column, so this username already exists, # making it safe to call .get(). return User.get(User.username == username) You can easily encapsulate this type of

keeps track of the connection state using thread-local storage, making the Peewee Database object safe to use with multiple threads. Each thread will have it’s own connection, and conversely, any given if your tables already exist, and conditionally create them. If you want to disable this, specify safe=False. After you have created your tables, if you choose to modify your database schema (by adding peewee.IntegrityError: # `username` is a unique column, so this username already exists, # making it safe to call .get(). return User.get(User.username == username) You can easily encapsulate this type of

keeps track of the connection state using thread-local storage, making the Peewee Database object safe to use with multiple threads. Each thread will have it’s own connection, and conversely, any given conditionally create them: # Only create the tables if they do not exist. db.create_tables([User, Tweet], safe=True) After you have created your tables, if you choose to modify your database schema (by adding IntegrityError: # `username` is a unique column, so this username already exists, # making it safe to call .get(). return User.get(User.username == username) You can easily encapsulate this type

keeps track of the connection state using thread-local storage, making the Peewee Database object safe to use with multiple threads. Each thread will have it’s own connection, and as a result any given Peewee includes an IF NOT EXISTS clause when creating tables. If you want to disable this, specify safe=False. After you have created your tables, if you choose to modify your database schema (by adding IntegrityError: # `username` is a unique column, so this username already exists, # making it safe to call .get(). return User.get(User.username == username) You can easily encapsulate this type

keeps track of the connection state using thread-local storage, making the Peewee Database object safe to use with multiple threads. Each thread will have it’s own connection, and as a result any given Peewee includes an IF NOT EXISTS clause when creating tables. If you want to disable this, specify safe=False. After you have created your tables, if you choose to modify your database schema (by adding peewee.IntegrityError: # `username` is a unique column, so this username already exists, # making it safe to call .get(). return User.get(User.username == username) You can easily encapsulate this type of

conditionally create them: # Only create the tables if they do not exist. db.create_tables([User, Tweet], safe=True) After you have created your tables, if you choose to modify your database schema (by adding IntegrityError: # `username` is a unique column, so this username already exists, # making it safe to call .get(). return User.get(User.username == username) You can easily encapsulate this type essentially. Note The module gets its name from the fact that all write queries get put into a thread- safe queue. A single worker thread listens to the queue and executes all queries that are sent to it.