Peewee

Latest version: v3.17.3

Safety actively analyzes 623133 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 24

3.17.3

* Better fix for 2871 (extraneous queries when coercing query to list), and
new fix in 2872 for regression in truthiness of cursor.

[View commits](https://github.com/coleifer/peewee/compare/3.17.2...3.17.3)

3.17.2

* Full support for `psycopg3`.
* Basic support for Sqlite `jsonb`.
* Fix bug where calling `list(query)` resulted in extra queries, 2871

[View commits](https://github.com/coleifer/peewee/compare/3.17.1...3.17.2)

3.17.1

* Add bitwise and other helper methods to `BigBitField`, 2802.
* Add `add_column_default` and `drop_column_default` migrator methods for
specifying a server-side default value, 2803.
* The new `star` attribute was causing issues for users who had a field named
star on their models. This attribute is now renamed to `__star__`. 2796.
* Fix compatibility issues with 3.12 related to utcnow() deprecation.
* Add stricter locking on connection pool to prevent race conditions.
* Add adapters and converters to Sqlite to replace ones deprecated in 3.12.
* Fix bug in `model_to_dict()` when only aliases are present.
* Fix version check for Sqlite native drop column support.
* Do not specify a `reconnect=` argument to `ping()` if using MySQL 8.x.

[View commits](https://github.com/coleifer/peewee/compare/3.17.0...3.17.1)

3.17.0

Not secure
* Only roll-back in the outermost `db.transaction` decorator/ctx manager if
an unhandled exception occurs. Previously, an unhandled exception that
occurred in a nested `transaction` context would trigger a rollback. The use
of nested `transaction` has long been discouraged in the documentation: the
recommendation is to always use `db.atomic`, which will use savepoints to
properly handle nested blocks. However, the new behavior should make it
easier to reason about transaction boundaries - see 2767 for discussion.
* Cover transaction `BEGIN` in the reconnect-mixin. Given that no transaction
has been started, reconnecting when beginning a new transaction ensures that
a reconnect will occur if it is safe to do so.
* Add support for setting `isolation_level` in `db.atomic()` and
`db.transaction()` when using Postgres and MySQL/MariaDB, which will apply to
the wrapped transaction. Note: Sqlite has supported a similar `lock_type`
parameter for some time.
* Add support for the Sqlite `SQLITE_DETERMINISTIC` function flag. This allows
user-defined Sqlite functions to be used in indexes and may be used by the
query planner.
* Fix unreported bug in dataset import when inferred field name differs from
column name.

[View commits](https://github.com/coleifer/peewee/compare/3.16.3...3.17.0)

3.16.3

Not secure
* Support for Cython 3.0.
* Add flag to `ManyToManyField` to prevent setting/getting values on unsaved
instances. This is worthwhile, since reading or writing a many-to-many has no
meaning when the instance is unsaved.
* Adds a `star()` helper to `Source` base-class for selecting all columns.
* Fix missing `binary` types for mysql-connector and mariadb-connector.
* Add `extract()` method to MySQL `JSONField` for extracting a jsonpath.

[View commits](https://github.com/coleifer/peewee/compare/3.16.2...3.16.3)

3.16.2

Not secure
Fixes a longstanding issue with thread-safety of various decorators, including
`atomic()`, `transaction()`, `savepoint()`. The context-managers are
unaffected. See 2709 for details.

[View commits](https://github.com/coleifer/peewee/compare/3.16.1...3.16.2)

Page 1 of 24

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.