databases/py-peewee 4.5.1 NetBSD

4.5.3 * JSON path keys on Postgres are rendered inline (`data->>'key'`, `'{"a","b"}'::text[]`) instead of as bound parameters, so `GROUP BY` and `ORDER BY` on a JSON lookup work under psycopg3, which binds each occurrence of a key as a distinct parameter. Applies to the core `JSONField` and to `playhouse.postgres_ext`. * `Cast()` and other wrapped nodes over a plain value no longer break result row processing. * A write query with a `RETURNING` clause now runs again on every explicit `execute()` call (like a write query without one). Iterating the query still reads the result of the last execution. Previously repeated `execute()` calls returned the cached result without running the query. * Fix regression in model select `.exists()`

4.5.2 * Don't cache ``None`` on unselected FK join trees. * Some fixes for edge-cases around non-unique aliases and unicode aliases. * Ensure subqueries get appropriate parens inside single argument functions. Functions that do not want the extra parens (exists, e.g.) will not add extra parens. * `exists()` wraps the query in `EXISTS(...)` rather than replacing its columns, fixing queries that order by or filter on a selected alias, and queries on MySQL that select two columns w/the same name. * Composite primary key columns are introspected in key-order.

4.5.1 * `EnumField` and `IntEnumField` validate member value types (`str` and `int` respectively) at field construction. * `EnumField` and `IntEnumField` default `choices` to `(value, name)` pairs derived from the enum. * Fix 3075, migration generation for `EnumField`. Generated migrations will emit the storage field type (e.g. `IntegerField`) rather than `EnumField()`.

4.5.0 Backwards-incompatible: * MySQL and MariaDB connections no longer set `sql_mode`. Peewee had been setting `PIPES_AS_CONCAT`, but the param replaced the server's mode rather than adding to it, which silently disabled `STRICT_TRANS_TABLES` (etc). Going forward Peewee will not modify `sql_mode` by default and use `CONCAT()` rather than `||` for MySQL/MariaDB. * MySQL and MariaDB connection charset defaults to `utf8mb4` instead of `utf8`, which is an alias for `utf8mb3` and cannot store 4-byte characters. * A field's `sequence=` is now qualified with the model's `Meta.schema`. If the name you pass already contains a dot it is treated as fully-qualified and used as-is, so `sequence='other.seq'` is unaffected by `Meta.schema`. Also, …