behavior, or have an idea for a new feature please don’t hesitate to open an issue [https://github.com/coleifer/peewee/issues?state=open] on GitHub or contact me [http://charlesleifer.com/contact/]. Indices database Now that we have our models, let’s connect to the database. Although it’s not necessary to open the connection explicitly, it is good practice since it will reveal any errors with your database executed. It is also good to close the connection when you are done – for instance, a web app might open a connection when it receives a request, and close the connection when it sends the response. db

behavior, or have an idea for a new feature please don’t hesitate to open an issue [https://github.com/coleifer/peewee/issues?state=open] on GitHub or contact me [http://charlesleifer.com/contact/]. Indices database Now that we have our models, let’s connect to the database. Although it’s not necessary to open the connection explicitly, it is good practice since it will reveal any errors with your database executed. It is also good to close the connection when you are done – for instance, a web app might open a connection when it receives a request, and close the connection when it sends the response. db

behavior, or have an idea for a new feature please don’t hesitate to open an issue [https://github.com/coleifer/peewee/issues?state=open] on GitHub or contact me [http://charlesleifer.com/contact/]. Indices database Now that we have our models, let’s connect to the database. Although it’s not necessary to open the connection explicitly, it is good practice since it will reveal any errors with your database executed. It is also good to close the connection when you are done – for instance, a web app might open a connection when it receives a request, and close the connection when it sends the response. db

behavior, or have an idea for a new feature please don’t hesitate to open an issue [https://github.com/coleifer/peewee/issues?state=open] on GitHub or contact me [http://charlesleifer.com/contact/]. Indices database Now that we have our models, let’s connect to the database. Although it’s not necessary to open the connection explicitly, it is good practice since it will reveal any errors with your database executed. It is also good to close the connection when you are done – for instance, a web app might open a connection when it receives a request, and close the connection when it sends the response. db

database Now that we have our models, let’s connect to the database. Although it’s not necessary to open the connection explicitly, it is good practice since it will reveal any errors with your database executed. It is also good to close the connection when you are done – for instance, a web app might open a connection when it receives a request, and close the connection when it sends the response. db this: def create_tables(): with database: database.create_tables([User, Relationship, Message]) Open a python shell in the directory alongside the example app and execute the following: >>> from app

database Now that we have our models, let’s connect to the database. Although it’s not necessary to open the connection explicitly, it is good practice since it will reveal any errors with your database executed. It is also good to close the connection when you are done – for instance, a web app might open a connection when it receives a request, and close the connection when it sends the response. db this: def create_tables(): with database: database.create_tables([User, Relationship, Message]) Open a python shell in the directory alongside the example app and execute the following: >>> from app

database Now that we have our models, let’s connect to the database. Although it’s not necessary to open the connection explicitly, it is good practice since it will reveal any errors with your database executed. It is also good to close the connection when you are done – for instance, a web app might open a connection when it receives a request, and close the connection when it sends the response. db this: def create_tables(): with database: database.create_tables([User, Relationship, Message]) Open a python shell in the directory alongside the example app and execute the following: >>> from app

behavior, or have an idea for a new feature please don’t hesitate to open an issue [https://github.com/coleifer/peewee/issues?state=open] on GitHub or contact me [http://charlesleifer.com/contact/]. Indices database Now that we have our models, let’s connect to the database. Although it’s not necessary to open the connection explicitly, it is good practice since it will reveal any errors with your database executed. It is also good to close the connection when you are done – for instance, a web app might open a connection when it receives a request, and close the connection when it sends the response. db

database Now that we have our models, let’s connect to the database. Although it’s not necessary to open the connection explicitly, it is good practice since it will reveal any errors with your database executed. It is also good to close the connection when you are done – for instance, a web app might open a connection when it receives a request, and close the connection when it sends the response. db this: def create_tables(): with database: database.create_tables([User, Relationship, Message]) Open a python shell in the directory alongside the example app and execute the following: 1.3. Example

behavior, or have an idea for a new feature please don’t hesitate to open an issue [https://github.com/coleifer/peewee/issues?state=open] on GitHub or contact me [http://charlesleifer.com/contact/]. Indices database Now that we have our models, let’s connect to the database. Although it’s not necessary to open the connection explicitly, it is good practice since it will reveal any errors with your database executed. It is also good to close the connection when you are done – for instance, a web app might open a connection when it receives a request, and close the connection when it sends the response. >>>