changes. Successful patches will have the following: Unit tests. Documentation, both prose form and general API documentation. Code that conforms stylistically with the rest of the Peewee codebase. Bugs Member.delete().where(Member.memid == 37) Delete based on a subquery How can we make that more general, to delete all members who have never made a booking? DELETE FROM members WHERE NOT EXISTS ( SELECT Managing Transactions Peewee provides several interfaces for working with transactions. The most general is the Database.atomic() method, which also supports nested transactions. atomic() blocks will be

Successful patches will have the following: • Unit tests. • Documentation, both prose form and general API documentation. • Code that conforms stylistically with the rest of the Peewee codebase. 1.4 Member.delete().where(Member.memid == 37) Delete based on a subquery How can we make that more general, to delete all members who have never made a booking? DELETE FROM members WHERE NOT EXISTS ( SELECT Managing Transactions Peewee provides several interfaces for working with transactions. The most general is the Database.atomic() method, which also supports nested transactions. atomic() blocks will be

Successful patches will have the following: • Unit tests. • Documentation, both prose form and general API documentation. • Code that conforms stylistically with the rest of the Peewee codebase. 1.4 Member.delete().where(Member.memid == 37) Delete based on a subquery How can we make that more general, to delete all members who have never made a booking? DELETE FROM members WHERE NOT EXISTS ( SELECT Managing Transactions Peewee provides several interfaces for working with transactions. The most general is the Database.atomic() method, which also supports nested transactions. atomic() blocks will be

changes. Successful patches will have the following: Unit tests. Documentation, both prose form and general API documentation. Code that conforms stylistically with the rest of the Peewee codebase. Bugs Member.delete().where(Member.memid == 37) Delete based on a subquery How can we make that more general, to delete all members who have never made a booking? DELETE FROM members WHERE NOT EXISTS ( SELECT Managing Transactions Peewee provides several interfaces for working with transactions. The most general is the Database.atomic() method, which also supports nested transactions. atomic() blocks will be

changes. Successful patches will have the following: Unit tests. Documentation, both prose form and general API documentation. Code that conforms stylistically with the rest of the Peewee codebase. Bugs Managing Transactions Peewee provides several interfaces for working with transactions. The most general is the Database.atomic() method, which also supports nested transactions. atomic() blocks will be information about the window function APIs, see: Function.over() Function.filter() Window For general information on window functions, the postgresql docs [http://www.postgresql.org/docs/9.1/static/tutorial-window

Successful patches will have the following: • Unit tests. • Documentation, both prose form and general API documentation. • Code that conforms stylistically with the rest of the Peewee codebase. 1.4 Managing Transactions Peewee provides several interfaces for working with transactions. The most general is the Database.atomic() method, which also supports nested transactions. atomic() blocks will be information about the window function APIs, see: • Function.over() • Function.filter() • Window For general information on window functions, the postgresql docs. have a good overview. 1.7.17 Retrieving row

changes. Successful patches will have the following: Unit tests. Documentation, both prose form and general API documentation. Code that conforms stylistically with the rest of the Peewee codebase. Bugs Managing Transactions Peewee provides several interfaces for working with transactions. The most general is the Database.atomic() method, which also supports nested transactions. atomic() blocks will be Employee.salary, fn.rank().over( order_by=[Employee.salary]))) For general information on window functions, check out the postgresql docs [http://www.postgresql.org/docs/9

changes. Successful patches will have the following: Unit tests. Documentation, both prose form and general API documentation. Code that conforms stylistically with the rest of the Peewee codebase. Bugs Member.delete().where(Member.memid == 37) Delete based on a subquery How can we make that more general, to delete all members who have never made a booking? DELETE FROM members WHERE NOT EXISTS ( SELECT Managing Transactions Peewee provides several interfaces for working with transactions. The most general is the Database.atomic() method, which also supports nested transactions. atomic() blocks will be

Successful patches will have the following: • Unit tests. • Documentation, both prose form and general API documentation. • Code that conforms stylistically with the rest of the Peewee codebase. 1.4 Managing Transactions Peewee provides several interfaces for working with transactions. The most general is the Database.atomic() method, which also supports nested transactions. atomic() blocks will be (Employee .select( Employee.name, Employee.salary, fn.rank().over( order_by=[Employee.salary]))) For general information on window functions, check out the postgresql docs. 1.7.17 Retrieving row tuples / dictionaries

changes. Successful patches will have the following: Unit tests. Documentation, both prose form and general API documentation. Code that conforms stylistically with the rest of the Peewee codebase. Bugs Employee.salary, fn.rank().over( order_by=[Employee.salary]))) For general information on window functions, check out the postgresql docs [http://www.postgresql.org/docs/9 consider when using prefetch(): Foreign keys must exist between the models being prefetched. In general it is more performant than aggregate_rows(). Typically a lot less data is transferred over the wire