Update dependency peewee to v3.16.2 #19
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.








This PR contains the following updates:
==3.14.8->==3.16.2Release Notes
coleifer/peewee
v3.16.2Compare Source
Fixes a longstanding issue with thread-safety of various decorators, including
atomic(),transaction(),savepoint(). The context-managers areunaffected. See #2709 for details.
View commits
v3.16.1Compare Source
language-level to 3.
PREFETCH_TYPE.JOIN.
when possible. This can be overridden by passing
legacy=Trueflag.View commits
v3.16.0Compare Source
This release contains backwards-incompatible changes in the way Peewee
initializes connections to the underlying database driver. Previously, peewee
implemented autocommit semantics on-top of the existing DB-API transactional
workflow. Going forward, Peewee instead places the DB-API driver into
autocommit mode directly.
Why this change?
Previously, Peewee emulated autocommit behavior for top-level queries issued
outside of a transaction. This necessitated a number of checks which had to be
performed each time a query was executed, so as to ensure that we didn't end up
with uncommitted writes or, conversely, idle read transactions. By running the
underlying driver in autocommit mode, we can eliminate all these checks, since
we are already managing transactions ourselves.
Behaviorally, there should be no change -- Peewee will still treat top-level
queries outside of transactions as being autocommitted, while queries inside of
atomic()/with db:blocks are implicitly committed at the end of theblock, or rolled-back if an exception occurs.
How might this affect me?
Database.connection()orDatabase.cursor(), your queries will now beexecuted in autocommit mode.
commit=argument is deprecated for thecursor(),execute()andexecute_sql()methods.Databaseimplementation (whether for a database thatis not officially supported, or for the purpose of overriding default
behaviors), you will want to ensure that your connections are opened in
autocommit mode.
Other changes:
get_columns()implementation now returns columns in their declaredorder.
View commits
v3.15.4Compare Source
ReconnectMixinif connection is lost while inside atransaction (if the transaction was interrupted presumably some changes were
lost and explicit intervention is needed).
db.Modelproperty to reduce boilerplate.prefetch()queries with joins instead of subqueries(this helps overcome a MySQL limitation about applying LIMITs to a subquery).
AVGto whitelist to avoid coercing by default.pyproject.tomlto silence warnings from newer pips whenwheelpackage is not available.
This release has a small helper for reducing boilerplate in some cases by
exposing a base model class as an attribute of the database instance.
v3.15.3Compare Source
scalars()query method (complementsscalar()), roughly equivalent towriting
[t[0] for t in query.tuples()].View commits
v3.15.2Compare Source
used for LIKE / ILIKE operations. Refs #2609
__iter__methodon certain
Columnsubclasses. Refs #2606should be bound to, in queries with joins that select from multiple sources.
View commits
v3.15.1Compare Source
subtypes in subqueries.
transaction on an unopened database.
View commits
v3.15.0Compare Source
Rollback behavior change in commit
ab43376(GH #2026). Peewee will no longerautomatically return the cursor
rowcountfor certain bulk-inserts. Thisshould only affect users of MySQL and Sqlite who relied on a bulk INSERT
returning the
rowcount(as opposed to the cursor'slastrowid). Therowcountbehavior is still available chaining theas_rowcount()method:v3.14.10Compare Source
Previous behavior (peewee 3.12 - 3.14.10):
v3.14.9Compare Source
table_exists()with a model-class, refsis_connection_usable()method ofMySQLDatabaseclass.playhouse.dataset.DataSetand sqlite-web.playhosue.kvfor newer Sqlite.ArrayField.contained_by()method, a corollary tocontains()andthe
contains_any()methods.also for sqlite-web.
full-text index.
setup.pyin the event distutils is not available.View commits
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.