never thought of 1.3.2 Changes from version 1.0 The biggest changes between 1.0 and 2.0 are in the syntax used for constructing queries. The first iteration of peewee I threw up on github was about 600 lines and experience, I decided to rewrite and unify the API a bit. The result is a tradeoff. The newer syntax may be a bit more verbose at times, but at least it will be consistent. 4 Chapter 1. Contents: ’a’) ) Note: If you are already familiar with Django’s ORM, you can use the “double underscore” syntax using the SelectQuery.filter() method: >>> for tweet in Tweet.filter(user__username=’Charlie’):

atomic update TweetCount.update(count=F('count') + 1).where(user=charlie) You can use django-style syntax to create select queries: # how many active users are there? User.filter(active=True).count() # Another Entry If you are already familiar with Django’s ORM, you can use the “double underscore” syntax: >>> for entry in Entry.filter(blog__name='My Blog'): ... print entry.title Old entry Some Entry a django-like syntax for building a query. The key difference between filter() and SelectQuery.where() is that filter() supports traversing joins using django’s “double-underscore” syntax: >>> sq = Entry

atomic update TweetCount.update(count=F(’count’) + 1).where(user=charlie) You can use django-style syntax to create select queries: # how many active users are there? User.filter(active=True).count() # Another Entry If you are already familiar with Django’s ORM, you can use the “double underscore” syntax: >>> for entry in Entry.filter(blog__name=’My Blog’): ... print entry.title Old entry Some Entry django-like syntax for building a query. The key difference between filter() and SelectQuery.where() is that filter() supports traversing joins using django’s “double- underscore” syntax: >>> sq = Entry

atomic update TweetCount.update(count=F('count') + 1).where(user=charlie) You can use django-style syntax to create select queries: # how many active users are there? User.filter(active=True).count() # Another Entry If you are already familiar with Django’s ORM, you can use the “double underscore” syntax: >>> for entry in Entry.filter(blog__name='My Blog'): ... print entry.title Old entry Some Entry a django-like syntax for building a query. The key difference between filter() and SelectQuery.where() is that filter() supports traversing joins using django’s “double-underscore” syntax: >>> sq = Entry

atomic update TweetCount.update(count=F(’count’) + 1).where(user=charlie) You can use django-style syntax to create select queries: # how many active users are there? User.filter(active=True).count() # Another Entry If you are already familiar with Django’s ORM, you can use the “double underscore” syntax: 1.3. Peewee Cookbook 9 peewee Documentation, Release 1.0.0 >>> for entry in Entry.filter(blog__name=’My django-like syntax for building a query. The key difference between filter() and SelectQuery.where() is that filter() supports traversing joins using django’s “double- underscore” syntax: >>> sq = Entry

explicit in your code when you want to sort your results. That said, to specify a default ordering, the syntax is similar to that of Django. Meta.order_by is a tuple of field names, and to indicate descending issue a REPLACE query. Currently this feature is not supported for Postgres databases, but the 9.5 syntax will be added soon. Note This feature is only available on SQLite and MySQL databases. on_conflict([action=None])

explicit in your code when you want to sort your results. That said, to specify a default ordering, the syntax is similar to that of Django. Meta.order_by is a tuple of field names, and to indicate descending issue a REPLACE query. Currently this feature is not supported for Postgres databases, but the 9.5 syntax will be added soon. Note: This feature is only available on SQLite and MySQL databases. on_con

any potential constraint violation. Postgresql and SQLite (3.24.0 and newer) provide a different syntax that allows for more granular control over which constraint violation should trigger the conflict

any potential constraint violation. Postgresql and SQLite (3.24.0 and newer) provide a different syntax that allows for more granular control over which constraint violation should trigger the conflict

any potential constraint violation. Postgresql and SQLite (3.24.0 and newer) provide a different syntax that allows for more granular control over which constraint violation should trigger the conflict