build(deps): bump peewee from 4.3.0 to 4.4.0

[dependabot]

Bumps peewee from 4.3.0 to 4.4.0.

Release notes

Sourced from peewee's releases.

4.4.0

In which we learn to migrate (somewhat).

• Add playhouse.migrations for running migration scripts. Migrations are python files defining up(migrator, db) and optionally down(...). Migrations are applied in numeric order a-la Django, and stored by name in a history table. CLI via pwmigrate accepting status, up, down, initial, create, generate, fake and diff. To run from python, migrations.run(db).
• Add basic playhouse.schema_diff for comparing models against the schema and reporting differences (tables to create, columns added or removed, indexes added or removed).
• Allow adding column to existing table as NOT NULL with migrator, which allows skipping the 3-step process of add nullable, populate default, set not null.
• db_url.connect() raises ValueError for a url with no database name, e.g. postgres://dbname (two slashes reads dbname as the host).
• Add a SchemaMigrator.migration_context() helper for wrapping migrations. This was wanted for SQLite in order to disable FK pragma, which could trigger cascading deletes while recreating tables.
• Allow SchemaMigrator.from_database() to support database proxies.
• Add support for newer SQLite ALTER TABLE functionality from 3.53.0.
• Do not allow delete() method to be called on a model instance. Model.delete() is a classmethod for constructing a DELETE query, and model.delete_instance() has always been the correct path for deleting a model instance. This new check just ensures that a new user cannot accidentally delete their whole table by using the class-version from an instance. Fixes #2277.
• Server-side cursors opened inside a transaction on psycopg3 are no longer declared WITH HOLD. They stream and are scoped to the transaction, rather than spooling their remaining rows server-side at commit.
• scalar() applies a LIMIT 1 via first(), rather than running the query unbounded and reading the first value. The query itself is not mutated, the limit is applied only on an internal copy, refs #3068.
• Ensure JSONField works when proxy is already initialized. Thanks @​NotAFlightRisk, refs #3070.
• commit() / rollback() on a closed db will raise rather than silently open a new connection.

View commits

Changelog

Sourced from peewee's changelog.

4.4.0

In which we learn to migrate (somewhat).

• Add playhouse.migrations for running migration scripts. Migrations are python files defining up(migrator, db) and optionally down(...). Migrations are applied in numeric order a-la Django, and stored by name in a history table. CLI via pwmigrate accepting status, up, down, initial, create, generate, fake and diff. To run from python, migrations.run(db).
• Add basic playhouse.schema_diff for comparing models against the schema and reporting differences (tables to create, columns added or removed, indexes added or removed).
• Allow adding column to existing table as NOT NULL with migrator, which allows skipping the 3-step process of add nullable, populate default, set not null.
• db_url.connect() raises ValueError for a url with no database name, e.g. postgres://dbname (two slashes reads dbname as the host).
• Add a SchemaMigrator.migration_context() helper for wrapping migrations. This was wanted for SQLite in order to disable FK pragma, which could trigger cascading deletes while recreating tables.
• Allow SchemaMigrator.from_database() to support database proxies.
• Add support for newer SQLite ALTER TABLE functionality from 3.53.0.
• Do not allow delete() method to be called on a model instance. Model.delete() is a classmethod for constructing a DELETE query, and model.delete_instance() has always been the correct path for deleting a model instance. This new check just ensures that a new user cannot accidentally delete their whole table by using the class-version from an instance. Fixes #2277.
• Server-side cursors opened inside a transaction on psycopg3 are no longer declared WITH HOLD. They stream and are scoped to the transaction, rather than spooling their remaining rows server-side at commit.
• scalar() applies a LIMIT 1 via first(), rather than running the query unbounded and reading the first value. The query itself is not mutated, the limit is applied only on an internal copy, refs #3068.
• Ensure JSONField works when proxy is already initialized. Thanks @​NotAFlightRisk, refs #3070.
• commit() / rollback() on a closed db will raise rather than silently open a new connection.

View commits

Commits

• 942d9c5 4.4.0
• 408aa4c Ensure we properly bind JSONField for initialized proxies.
• 8359b7b Fix for Insert query attempting to access attr before bind.
• 5dacbe9 Flesh out reconnectmixin errors, clarify doc for pg users.
• 9b3bff5 Restore loglevel w/count_queries helper in test_utils
• 08b28d1 commit/rollback on a closed connection will raise rather than re-open.
• fc1811e Add helper for unwrapping db if it's a proxy.
• baee958 When adding a bound col, we might corrupt field state - use a clone.
• f5e439d Apply a LIMIT 1 on scalar(), fixes #3068
• c12b753 Fixup new schema tests so they use the in-mem db.
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)