6.2.8:
* In Python 3.9, "find_unused_port" has been moved to
"test.support.socket_helper". Reported by Michał Górny.
* If we use "set_get_returns_none()" in the environment,
the value could not be correctly inherited by the child
databases. Reported by Patrick Laimbock and modern GCC
warnings.
* If you install this library under Python 3 >= 3.6, let
you know this is a legacy library and points you to
"berkeleydb" library.
Packaging changes: make bl3 refer to PGSQL_VERSION, not 12, reverting
an earlier change labeled "revbump" which does not make sense for such
a change.
Upstream changes: bugfixes
0.16.18
Support custom function in update.
Add Model.refresh_from_db.
Add timezone support, be careful to upgrade to this version, see docs for details.
Remove aerich in case of cyclic dependency.
PostgreSQL 13.1, 12.5, 11.10, 10.15, 9.6.20, and 9.5.24
Security Issues
* CVE-2020-25695: Multiple features escape "security restricted operation" sandbox
* CVE-2020-25694: Reconnection can downgrade connection security settings
* CVE-2020-25696: psql's \gset allows overwriting specially treated variables
Bug Fixes and Improvements
This update also fixes over 65 bugs that were reported in the last several months. Some of these issues only affect version 13, but may also apply to other supported versions.
Some of these fixes include:
Fix a breakage in the replication protocol by ensuring that two "command completion" events are expected for START_REPLICATION.
Ensure fsync is called on the SLRU caches that PostgreSQL maintains. This prevents potential data loss due to an operating system crash.
Fix ALTER ROLE usage for users with the BYPASSRLS permission.
ALTER TABLE ONLY ... DROP EXPRESSION is disallowed on partitioned tables when there are child tables.
Ensure that ALTER TABLE ONLY ... ENABLE/DISABLE TRIGGER does not apply to child tables.
Fix for ALTER TABLE ... SET NOT NULL on partitioned tables to avoid a potential deadlock in parallel pg_restore.
Fix handling of expressions in CREATE TABLE LIKE with inheritance.
DROP INDEX CONCURRENTLY is disallowed on partitioned tables.
Allow LOCK TABLE to succeed on a self-referential view instead of throwing an error.
Several fixes around statistics collection and progress reporting for REINDEX CONCURRENTLY.
Ensure that GENERATED columns are updated when any columns they depend on are updated via a rule or an updatable view.
Support hash partitioning with text array columns as partition keys.
Allow the jsonpath .datetime() method to accept ISO 8601-format timestamps.
During a "smart" shutdown, ensure background processes are not terminated until all foreground client sessions are completed, fixing an issue that broke the processing of parallel queries.
Several fixes for the query planner and optimizer.
Ensure that data is de-toasted before being inserted into a BRIN index. This could manifest itself with errors like "missing chunk number 0 for toast value NNN". If you have seen a similar error in an existing BRIN index, you should be able to correct it by using REINDEX on the index.
Fix the output of EXPLAIN to have the correct XML tag nesting for incremental sort plans.
Several fixes for memory leaks, including ones involving RLS policies, using CALL with PL/pgSQL, SIGHUP processing a configuration parameter that cannot be applied without a restart, and an edge-case for index lookup for a partition.
libpq can now support arbitrary-length lines in the .pgpass file.
On Windows, psql now reads the output of a backtick command in text mode, not binary mode, so it can now properly handle newlines.
Fix how pg_dump, pg_restore, clusterdb, reindexdb, and vacuumdb use complex connection-string parameters.
When the \connect command of psql reuses connection parameters, ensure that all non-overridden parameters from a previous connection string are also re-used.
Ensure that pg_dump collects per-column information about extension configuration tables, avoiding crashes when specifying --inserts.
Ensure that parallel pg_restore processes foreign keys referencing partitioned tables in the correct order.
Several fixes for contrib/pgcrypto, including a memory leak fix.
DB Browser for SQLite 3.12.1
This is the first bug fix release for our 3.12.x series.
There aren't any "super critical must upgrade" bugs fixed, so updating isn't urgent. 😄
The changes in this over the 3.12.0 release include:
Enhancements
Completely reworked interface for accessing DBHub.io
Add .Net DateTime.Ticks to list of supported display formats
Add more options for setting font sizes
New predefined settings for simplified window layout
Bug fixes
Fix loading of project files with empty filter values
Fix initial table view when using the -t / --table command line option
Add status message when opening a file from the recent file list (4dfe4f7)
Make sure to not show "NULL" for empty but non-NULL values in the Edit dialog
Fix plot being drawn before all data is loaded
Restore original default for having condition format in filter line (f28ecc0)
Fix default font in the format toolbar (c4b2ffc)
Improve binary detection for cases starting by chance by a BOM
Make sure the order of the statements in the SQL log is correct (05db901)
Fix executing selected SQL text when there are multi-byte characters
Fix executing SQL queries with compound operators
Fix SQL import of files with BOM
Also update schema when clicking the Refresh button in Browse Data tab (16c3d8d)
Select column in table results when column header is pressed
Tweak the output wording for command line options
Remove the default property of the cancel button in the "Fetching data..." dialog
Fix not being saved and not applied when modifying database cells in Windows external program (f2d8f79)
Fix incorrect display of SQL calltips containing non-US-ASCII characters (9f7851b)
Fix to 'Window Layout' options work properly
Building and packaging
Fix CMake warning during compilation (115aa00)
snap: Add environment variables to set Qt theme (7b5d652)
Updated to OpenSSL 1.1.1h for the Windows and macOS builds
Platform specific
No longer force Light theme on macOS when "Follow the desktop style" is chosen (508118f)
Keep registry key consistent on Windows
Allow use of integrated graphics card instead of high performance graphics card in macOS
Use native path separators in Preferences dialog (f38b829)
Added message box for informative command line arguments for Windows
2.22.1
* [BUGFIX] Fix potential "mmap: invalid argument" errors in loading the head chunks, after an unclean shutdown, by performing read repairs.
* [BUGFIX] Fix serving metrics and API when reloading scrape config.
* [BUGFIX] Fix head chunk size calculation for size based retention.
pkgsrc: changes: re-enable .la
There are some test issues, but it seems better to move to 0.48 than
stay at 0.47. If you are a pkgsrc user of guile-pg and disagree,
please speak up (and help test/fix!).
- 0.48 | 2020-10-26
- installation by default deletes the .la files
See README re "SOFIXFLAGS".
- configuration changes
- configure script tries to use pkg-config(1)
The configure script now tries to use pkg-config(1) to determine
directory values for the ‘-I’ and ‘-L’ compiler switches. The
standard way is still supported (see README).
- configure-time ‘INITDB’ specification
For "make check", you can specify to the configure script the
initdb(1) program to use with option ‘INITDB=/path/to/initdb’.
For example:
./configure INITDB=/usr/lib/postgresql/9.4/bin/initdb
This saves the value of ‘INITDB’ so you don't need to specify it
manually for each "make check" invocation (see README).
- builtin array variant types now have prefix-asterisk names
Previously, the builtin array variant types had names that end
in "[]" (i.e., one or more pairs of square braces). These now
have prefix-asterisk names.
(was) (now)
text[] *text
text[][] **text
int4[] *int4
aclitem[] *aclitem
Furthermore, old-style names are no longer supported. This is
concomitant w/ dropping of ‘define-db-col-type-array-variant’
(see below).
- dropped items
All these were announced in Guile-PG 0.47 (2015-02-23).
- module ‘(database postgres-resdisp)’
- proc ‘(database postgres) pg-lo-read’
- procs in module ‘(database postgres-types)’
- ‘dbcoltypes’
- ‘dbcoltype-lookup’
- ‘dbcoltype:stringifier’
- ‘dbcoltype:default’
- ‘dbcoltype:objectifier’
- ‘define-db-col-type-array-variant’
OpenLDAP 2.4.56
Fixed slapd to remove assert in certificateListValidate
Fixed slapd to remove assert in csnNormalize23
Fixed slapd to better parse ldapi listener URIs
3.14.0
This release has been a bit overdue and there are numerous small improvements
and bug-fixes. The bugfix that prompted this release is 2293, which is a
regression in the Django-inspired .filter() APIs that could cause some
filter expressions to be discarded from the generated SQL. Many thanks for the
excellent bug report, Jakub.
Add an experimental helper, shortcuts.resolve_multimodel_query(), for resolving multiple models used in a compound select query.
Add a lateral() method to select query for use with lateral joins.
Added support for nested transactions (savepoints) in cockroach-db (requires 20.1 or newer).
Automatically escape wildcards passed to string-matching methods.
Allow index-type to be specified on MySQL.
Added a new API, converter() to be used for specifying a function to use to convert a row-value pulled off the cursor.
Add set() and clear() method to the bitfield flag descriptor.
Add support for range types with IN and other expressions.
Support CTEs bound to compound select queries.
Bug-fixes
Fix to return related object id when accessing via the object-id descriptor, when the related object is not populated.
Fix to ensure we do not insert a NULL value for a primary key.
Fix to conditionally set the field/column on an added column in a migration.
Apply field conversion logic to model-class values.
Clone node before modifying it to be flat in an enclosed nodelist expr.
Fix an invalid item assignment in nodelist.
Fix an incorrect truthiness check used with save() and only=.
Fix regression in filter() where using both *args and **kwargs caused the expressions passed as args to be discarded.
These binaries are not installed in the official binary distributions.
We probably installed them as a side effect of using pax(1) to copy the
whole bin/ directory. Use ${INSTALL_PROGRAM} instead.
This PostgreSQL extension contains support functions to improve the performance
of Promscale. While Promscale will run without it, adding this extension will
cause it to perform better.
Promscale allows Prometheus to store data in a PostgreSQL instance using the
TimescaleDB extension. Promscale can also act directly as a
Prometheus Data Source for Grafana, or other software.
By allowing a user to use SQL, in addition to PromQL, this platform empowers
the user to ask complex analytical queries from their metrics data, and thus
extract more meaningful insights.
v0.16.0
-------
Feature release
* Improved performance for async iteration on cursors
* Support for deterministic user functions in Python 3.8+
* Reduced logging severity for exceptions returned from children
* Fix InvalidStateError when setting future results
* Allow user to catch exceptions from `close()`
* Tested under Python 3.9
repmgr 5.2.0 is a major release.
This release provides support for PostgreSQL 13, released in September 2020.
This release removes support for PostgreSQL 9.3, which was designated EOL in November 2018.
A.1.1. General improvements
Configuration: support include, include_dir and include_if_exists directives (see configuration file include directives).
repmgr standby switchover: Improve sanity check failure log output from the demotion candidate.
If database connection configuration is not consistent across all nodes, it's possible remote repmgr invocations (e.g. during switchover, from the promotion candidate to the demotion candidate) will not be able to connect to the database. This will now be explicitly reported as a database connection failure, rather than as a failure of the respective sanity check.
repmgr cluster crosscheck / repmgr cluster matrix: improve text mode output format, in particular so that node identifiers of arbitrary length are displayed correctly.
repmgr primary unregister: the --force can be provided to unregister an active primary node, provided it has no registered standby nodes.
repmgr standby clone: new option --verify-backup to run PostgreSQL's pg_verifybackup utility after cloning a standby to verify the integrity of the copied data (PostgreSQL 13 and later).
repmgr standby clone: when cloning from Barman, setting --waldir (PostgreSQL 9.6 and earlier: --xlogdir) in pg_basebackup_options will cause repmgr to create a WAL directory outside of the main data directory and symlink it from there, in the same way as would happen when cloning using pg_basebackup.
repmgr standby follow: In PostgreSQL 13 and later, a standby no longer requires a restart to follow a new upstream node.
The old behaviour (always restarting the standby to follow a new node) can be restored by setting the configuration file parameter standby_follow_restart to true.
repmgr node rejoin: enable a node to attach to a target node even the target node has a lower timeline (PostgreSQL 9.6 and later).
repmgr node rejoin: in PostgreSQL 13 and later, support pg_rewind's ability to automatically run crash recovery on a PostgreSQL instance which was not shut down cleanly.
repmgr node check: option --db-connection added to check if repmgr can connect to the database on the local node.
repmgr node check: report database connection error if the --optformat was provided.
Improve handling of pg_control read errors.
It is now possible to dump the contents of repmgr metadata tables with pg_dump.
A.1.2. repmgrd enhancements
Following additional parameters can be provided to failover_validation_command:
%n: node ID
%a: node name
%v: number of visible nodes
%u: number of shared upstream nodes
%t: total number of nodes
Configuration option always_promote (default: false) to control whether a node should be promoted if the repmgr metadata is not up-to-date on that node.
A.1.3. Bug fixes
repmgr standby clone: fix issue with cloning from Barman where the tablespace mapping file was not flushed to disk before attempting to retrieve files from Barman.
repmgr node rejoin: ensure that when verifying a standby node has attached to its upstream, the node has started streaming before confirming the success of the rejoin operation.
repmgrd: ensure primary connection is reset if same as upstream.
What's new in psycopg 2.8.6
- Fixed memory leak changing connection encoding to the current one.
- Fixed search of mxDateTime headers in virtualenvs.
- Added missing values from errorcodes.
- `cursor.query` reports the query of the last :sql:`COPY` opearation too.
- `~psycopg2.errorcodes` map and `~psycopg2.errors` classes updated to
PostgreSQL 13.
- Added wheel packages for ARM architecture.
- Wheel package compiled against OpenSSL 1.1.1g.
What's new in psycopg 2.8.5
- Fixed use of `!connection_factory` and `!cursor_factory` together.
- Added support for `~logging.LoggerAdapter` in
`~psycopg2.extras.LoggingConnection`.
- `~psycopg2.extensions.Column` objects in `cursor.description` can be sliced.
- Added AIX support.
- Fixed `~copy.copy()` of `~psycopg2.extras.DictCursor` rows
Redis 6.0.9
===========
Upgrade urgency: SECURITY if you use an affected platform (see below).
Otherwise the upgrade urgency is MODERATE.
This release fixes a potential heap overflow when using a heap allocator other
than jemalloc or glibc's malloc. See:
https://github.com/redis/redis/pull/7963
Other fixes in this release:
New:
* Memory reporting of clients argv
* Add redis-cli control on raw format line delimiter
* Add redis-cli support for rediss:// -u prefix
* Get rss size support for NetBSD and DragonFlyBSD
Behavior changes:
* WATCH no longer ignores keys which have expired for MULTI/EXEC
* Correct OBJECT ENCODING response for stream type
* Allow blocked XREAD on a cluster replica
* TLS: Do not require CA config if not used
Bug fixes:
* INFO report real peak memory (before eviction)
* Allow requirepass config to clear the password
* Fix config rewrite file handling to make it really atomic
* Fix excessive categories being displayed from ACLs
* Add fsync in replica when full RDB payload was received
* Don't write replies to socket when output buffer limit reached
* Fix redis-check-rdb support for modules aux data
* Other smaller bug fixes
Modules API:
* Add APIs for version and compatibility checks
* Add RM_GetClientCertificate
* Add RM_GetDetachedThreadSafeContext
* Add RM_GetCommandKeys
* Add Swapdb Module Event
* RM_GetContextFlags provides indication of being in a fork child
* RM_GetContextFlags document missing flags: MULTI_DIRTY, IS_CHILD
* Expose real client on connection events
* Minor improvements to module blocked on keys
0.16.17
Add on_delete in ManyToManyField.
Support F expression in annotate.
Fix QuerySet.select_related in case of join same table twice.
Integrate Aerich into the install.
Note that the 5.6 series will be end of life in February 2021. The
current major version is 8.0, which isn't in pkgsrc yet. You CAN NOT
upgrade directly from 5.6 to 8.0, therefore it is recommended for anybody
running 5.6 to upgrade to this version, then upgrade to 5.7.
Changes in MySQL 5.6.50 (2020-10-19, General Availability)
Functionality Added or Changed
LOCK TABLES privilege checking for views was improved. (Bug #31304432)
Bugs Fixed
InnoDB: In session started with START TRANSACTION WITH CONSISTENT
SNAPSHOT, a range query returned a truncated result. The end
range flag was not reset at the beginning of the index read
resulting in an aborted read and missing rows. (Bug #30950714,
Bug #98642)
References: This issue is a regression of: Bug #23481444.
In bootstrapping mode, certain multiple-statement transactions
could cause unexpected server behavior. (Bug #31650096)
Assigning CONCAT('') or CONCAT_WS('') to a variable set the
variable to NULL, not the empty string. (Bug #31320716, Bug
#99485, Bug #31413167, Bug #99722)
ORDER BY queries were not executed correctly when sort_buffer_size
and max_sort_length were set to values which caused the internal
limit on the maximum number of keys allowed per sort buffer to
be set to 0. (Bug #30175483)
The internal method Field_tiny::pack() did not always perform
bounds checking as expected. (Bug #29948029)
References: See also: Bug #31591391.
A large number of nested arguments in full-text search query
caused an error. (Bug #29929684)
An assertion could be raised when the SQL layer passed incorrect
information to InnoDB about the type of operation to be performed
on a temporary table. (Bug #22503696)
Upstream changes:
5.0.0 (2020-10-12)
Features
Provide wheels for aarch64, i686, ppc64le, s390x architectures on Linux as well as x86_64. #500
Provide wheels for Python 3.9. #534
Removal
Drop Python 3.5 support; Python 3.6 is the minimal supported Python version.
7.2.0
- You can now implicitly convert a `const std::string &` to `zview`.
- Replaced some overloads for C strings and C++ strings with `zview`.
- Deprecating `binarystring`. Use `std::basic_string<std::byte>` instead!
- Array parser did not recognise escaping in unquoted values.
- gcc10 test build fix: a result iterator is not the same thing as a `row`.
- Doc fix: field size does _not_ include terminating zero. (#356)
- Fix error message in `demangle_type_name`: printed result, not raw name.
- Fix compile warning in `demangle_type_name` on GNU systems.
- Document that string conversions assume non-null values.
- Start playing with C++20 _concepts._
- Sketch out concepts-based `PQconnectdbParams` support. (#343)
- Add missing link to "datatypes" documentation. (#346)
- Supports `to_string`, `stream_to`, etc. for `binarystring`. (#312)
- Fixed infinite recursion when using `std::optional` in `stream_to`. (#364)
- Home-rolled hex-escaping. Saves an allocation.
- Catch floating-point negative overflow in `check_cast`, not underflow.
- Bit more work on CMake build doc. (#318)
- Typo in `datatypes.md`: `nullness`, not `nullness_traits`. (#353)
- Fixed test names map in `tests/runner.cxx`. (#354)
- Integral `from_string` now accept leading whitespace, as in composite types.
- Experimental support basics for composite types. (#355)
- Use `stream_from` without knowing the number of fields. (#357)
- Global `size_buffer` function.
- `quote()` now works for always-null types without conversions defined.
- `std::nullopt` now converts to an SQL null.
- Skip quoting and escaping array/composite fields of "safe" types.
- New type trait: `is_unquoted_safe`.
- Forbid invalid specialisations of `query_value`.
- Fixed `mktemp` invocation that broke on FreeBSD.
- Avoid unneeded encode/decode step on more binary data.
- If `__cxa_demangle` fails, fall back on raw type name. (#361)
Changes in MySQL 5.7.32 (2020-10-19, General Availability)
Functionality Added or Changed
Bugs Fixed
Functionality Added or Changed
LOCK TABLES privilege checking for views was improved.
Bugs Fixed
InnoDB: A query that updated the clustered index of an internal temporary table returned an incorrect result. The modified pages of the clustered index were not added to the flush list resulting in lost changes when the modified pages were evicted from the buffer pool.
References: This issue is a regression of:
InnoDB: An ALTER TABLE ... IMPORT TABLESPACE operation on a large encrypted and compressed table failed with a Page decompress failed after reading from disk error. The decryption operation did not use the encryption block size used during encryption. Also, the encryption process did not consider compressed length, while the decryption process decrypts data by compressed length only.
InnoDB: A failure occurred during a concurrent update operation. The failure was due to an invalid previous record value.
InnoDB: The function used to process the SHOW ENGINE INNODB MUTEX statement was insufficiently isolated from other threads adding new mutexes concurrently.
InnoDB: The buffer control block structure (buf_block_t) was freed while reducing the size of the buffer pool, causing an assertion failure. The fix for this bug also backports important aspects of the fix for
InnoDB: In session started with START TRANSACTION WITH CONSISTENT SNAPSHOT, a range query returned a truncated result. The end range flag was not reset at the beginning of the index read resulting in an aborted read and missing rows.
References: This issue is a regression of:
InnoDB: A full-text phrase search raised an assertion failure.
Thanks to TXSQL (Tencent MySQL) for the contribution.
References: This issue is a regression of:
InnoDB: A long running statistics calculation operation on a large table blocked other operations requiring access to the table's statistics, causing those operations to fail. A new statistics calculation mutex was introduced, which permits concurrent access table statistics.
Thanks to Kamil Holubicki for the contribution.
InnoDB: Two connections attempted to use the same transaction handler object resulting in a stalled query.
Replication: When a replication source server shuts down and restarts, its MEMORY tables become empty. To replicate this effect to replicas, the first time that the source uses a given MEMORY table after startup, it logs an event that notifies replicas that the table must be emptied by writing a statement to the binary log to that effect. Previously, this was a DELETE statement, but it is now a TRUNCATE TABLE statement. A replica server also writes this statement to its own binary log when it shuts down and restarts. The statement is always logged in statement format, even if the binary logging format is set to ROW, and it is written even if read_only or super_read_only mode is set on the server.
Replication: When the system variable session_track_gtids was set to OWN_GTID on a multithreaded replica, the replica’s performance would degrade over time and begin to lag behind the master. The cause was the buildup of the GTIDs recorded by the replica’s worker threads at each transaction commit, which increased the time taken by the worker threads to insert new ones. Session state tracking is now disabled for worker threads on a multithreaded replica. Thanks to Facebook for the contribution.
Certain cases of successful LDAP authentication could cause the server to hang.
In bootstrapping mode, certain multiple-statement transactions could cause unexpected server behavior.
Sensitive LDAP authentication plugin system variables now display as asterisks when retrieved in SQL statements.
After the fix for
References: This issue is a regression of:
Some INSERT statements were not handled correctly.
Certain prepared statements could cause an unexpected server exit.
mysqlpump object validation included objects in excluded databases.
LDAP authentication plugins enforced CA verification incorrectly, which could result in use of an incorrect CA.
ORDER BY queries were not executed correctly when sort_buffer_size and max_sort_length were set to values which caused the internal limit on the maximum number of keys allowed per sort buffer to be set to 0.
A large number of nested arguments in full-text search query caused an error.
When explicit_defaults_for_timestamp was disabled and a NULL was inserted into a generated column declared as TIMESTAMP NOT NULL, the server would attempt to convert the inserted value to CURRENT_TIMESTAMP. Such an insertion is now rejected with ER_BAD_NULL_ERROR.
An assertion could be raised when the SQL layer passed incorrect information to InnoDB about the type of operation to be performed on a temporary table.
1.3.20
Released: October 12, 2020
orm
[orm] [bug]
An ArgumentError with more detail is now raised if the target parameter for Query.join() is set to an unmapped object. Prior to this change a less detailed AttributeError was raised. Pull request courtesy Ramon Williams.
[orm] [bug]
Fixed issue where using a loader option against a string attribute name that is not actually a mapped attribute, such as a plain Python descriptor, would raise an uninformative AttributeError; a descriptive error is now raised.
engine
[engine] [bug]
Fixed issue where a non-string object sent to SQLAlchemyError or a subclass, as occurs with some third party dialects, would fail to stringify correctly. Pull request courtesy Andrzej Bartosiński.
[engine] [bug]
Repaired a function-level import that was not using SQLAlchemy’s standard late-import system within the sqlalchemy.exc module.
sql
[sql] [bug]
Fixed issue where the pickle.dumps() operation against Over construct would produce a recursion overflow.
[sql] [bug]
Fixed bug where an error was not raised in the case where a column() were added to more than one table() at a time. This raised correctly for the Column and Table objects. An ArgumentError is now raised when this occurs.
postgresql
[postgresql] [usecase]
The psycopg2 dialect now support PostgreSQL multiple host connections, by passing host/port combinations to the query string. Pull request courtesy Ramon Williams.
See also
Specfiying multiple fallback hosts
[postgresql] [bug]
Adjusted the Comparator.any() and Comparator.all() methods to implement a straight “NOT” operation for negation, rather than negating the comparison operator.
[postgresql] [bug]
Fixed issue where the ENUM type would not consult the schema translate map when emitting a CREATE TYPE or DROP TYPE during the test to see if the type exists or not. Additionally, repaired an issue where if the same enum were encountered multiple times in a single DDL sequence, the “check” query would run repeatedly rather than relying upon a cached value.
mysql
[mysql] [usecase]
Adjusted the MySQL dialect to correctly parenthesize functional index expressions as accepted by MySQL 8. Pull request courtesy Ramon Williams.
[mysql] [bug]
The “skip_locked” keyword used with with_for_update() will emit a warning when used on MariaDB backends, and will then be ignored. This is a deprecated behavior that will raise in SQLAlchemy 1.4, as an application that requests “skip locked” is looking for a non-blocking operation which is not available on those backends.
[mysql] [bug]
Fixed bug where an UPDATE statement against a JOIN using MySQL multi-table format would fail to include the table prefix for the target table if the statement had no WHERE clause, as only the WHERE clause were scanned to detect a “multi table update” at that particular point. The target is now also scanned if it’s a JOIN to get the leftmost table as the primary table and the additional entries as additional FROM entries.
[mysql] [change]
Add new MySQL reserved words: cube, lateral added in MySQL 8.0.1 and 8.0.14, respectively; this indicates that these terms will be quoted if used as table or column identifier names.
mssql
[mssql] [bug]
Fixed issue where a SQLAlchemy connection URI for Azure DW with authentication=ActiveDirectoryIntegrated (and no username+password) was not constructing the ODBC connection string in a way that was acceptable to the Azure DW instance.
misc
[bug] [pool]
Fixed issue where the following pool parameters were not being propagated to the new pool created when Engine.dispose() were called: pre_ping, use_lifo. Additionally the recycle and reset_on_return parameter is now propagated for the AssertionPool class.
[bug] [associationproxy] [ext]
An informative error is now raised when attempting to use an association proxy element as a plain column expression to be SELECTed from or used in a SQL function; this use case is not currently supported.
[bug] [tests]
Fixed incompatibilities in the test suite when running against Pytest 6.x.
2.22.0
As announced in the 2.21.0 release notes, the experimental gRPC API v2 has been
removed.
[CHANGE] web: Remove APIv2.
[ENHANCEMENT] React UI: Implement missing TSDB head stats section.
[ENHANCEMENT] UI: Add Collapse all button to targets page.
[ENHANCEMENT] UI: Clarify alert state toggle via checkbox icon.
[ENHANCEMENT] Add rule_group_last_evaluation_samples and prometheus_tsdb_data_replay_duration_seconds metrics.
[ENHANCEMENT] Gracefully handle unknown WAL record types.
[ENHANCEMENT] Issue a warning for 64 bit systems running 32 bit binaries.
[BUGFIX] Adjust scrape timestamps to align them to the intended schedule, effectively reducing block size. Workaround for a regression in go1.14+.
[BUGFIX] promtool: Ensure alert rules are marked as restored in unit tests.
[BUGFIX] Eureka: Fix service discovery when compiled in 32-bit.
[BUGFIX] Don't do literal regex matching optimisation when case insensitive.
[BUGFIX] Fix classic UI sometimes running queries for instant query when in range query mode.
