Bump peewee from 3.15.4 to 3.16.0

[dependabot]

Bumps peewee from 3.15.4 to 3.16.0.

Release notes

Sourced from peewee's releases.

3.16.0

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 the block, or rolled-back if an exception occurs.

How might this affect me?

• If you are using the underlying database connection or cursors, e.g. via Database.connection() or Database.cursor(), your queries will now be executed in autocommit mode.
• The commit= argument is deprecated for the cursor(), execute() and execute_sql() methods.
• If you have a custom Database implementation (whether for a database that is 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:

• Some fixes to help with packaging in Python 3.11.
• MySQL get_columns() implementation now returns columns in their declared order.

View commits

Changelog

Sourced from peewee's changelog.

3.16.0

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 the block, or rolled-back if an exception occurs.

How might this affect me?

• If you are using the underlying database connection or cursors, e.g. via Database.connection() or Database.cursor(), your queries will now be executed in autocommit mode.
• The commit= argument is deprecated for the cursor(), execute() and execute_sql() methods.
• If you have a custom Database implementation (whether for a database that is 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:

• Some fixes to help with packaging in Python 3.11.
• MySQL get_columns() implementation now returns columns in their declared order.

View commits

Commits

• 7d6ad68 3.16.0
• 7610757 Clarify docs on bulk_update()
• b5cee5e Additional note to changelog
• f599914 Restore the commit= parameter to minimize breaking 3rd party code.
• 97f77a3 Prepare changelog notes.
• aa8d4e7 Remove cursor withhold for psycopg2 server-side queries.
• ca30a05 Additional doc changes for autocommit change.
• cde3a44 Small doc change
• 6783491 Remove additional db-api-related workarounds and APIs.
• cc73066 Additional changes to shift things over to autocommit.
• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)

[dependabot]

Superseded by #29.