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.4
->==3.15.4
Release Notes
coleifer/peewee
v3.15.4
Compare Source
ReconnectMixin
if connection is lost while inside atransaction (if the transaction was interrupted presumably some changes were
lost and explicit intervention is needed).
db.Model
property to reduce boilerplate.prefetch()
queries with joins instead of subqueries(this helps overcome a MySQL limitation about applying LIMITs to a subquery).
AVG
to whitelist to avoid coercing by default.pyproject.toml
to silence warnings from newer pips whenwheel
package 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.3
Compare Source
scalars()
query method (complementsscalar()
), roughly equivalent towriting
[t[0] for t in query.tuples()]
.View commits
v3.15.2
Compare Source
used for LIKE / ILIKE operations. Refs #2609
__iter__
methodon certain
Column
subclasses. Refs #2606should be bound to, in queries with joins that select from multiple sources.
View commits
v3.15.1
Compare Source
subtypes in subqueries.
transaction on an unopened database.
View commits
v3.15.0
Compare Source
Rollback behavior change in commit
ab43376
(GH #2026). Peewee will no longerautomatically return the cursor
rowcount
for 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
). Therowcount
behavior is still available chaining theas_rowcount()
method:v3.14.10
Compare Source
Previous behavior (peewee 3.12 - 3.14.10):
v3.14.9
Compare Source
table_exists()
with a model-class, refsis_connection_usable()
method ofMySQLDatabase
class.playhouse.dataset.DataSet
and sqlite-web.playhosue.kv
for newer Sqlite.ArrayField.contained_by()
method, a corollary tocontains()
andthe
contains_any()
methods.also for sqlite-web.
full-text index.
setup.py
in the event distutils is not available.View commits
v3.14.8
Compare Source
Back-out all changes to automatically use RETURNING for
SqliteExtDatabase
,CSqliteExtDatabase
andAPSWDatabase
. The issue I found is that when aRETURNING cursor is not fully-consumed, any parent SAVEPOINT (and possibly
transaction) would not be able to be released. Since this is a
backwards-incompatible change, I am going to back it out for now.
Returning clause can still be specified for Sqlite, however it just needs to be
done so manually rather than having it applied automatically.
View commits
v3.14.7
Compare Source
Fix bug in APSW extension with Sqlite 3.35 and newer, due to handling of last
insert rowid with RETURNING. Refs #2479.
View commits
v3.14.6
Compare Source
Fix pesky bug in new
last_insert_id()
on theSqliteExtDatabase
.View commits
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.