mongo-c-driver 1.17.3
=====================
Bug fixes:
* Do not send session ID on GSSAPI auth commands.
* Fix build against zlib when zlib is installed in non-standard location.
* Fix build when source directory path contains a space.
* Fix a platform-specific bug causing mongoc_client_pool_pop to block indefinitely if all clients are checked out.
* Fix a possible buffer overflow with hostnames resolving to IPv6 addresses on OpenSSL.
mongo-c-driver 1.17.2
=====================
Bug fixes:
* Stop the SRV polling thread when an SRV URI is used to connect to a deployment other than a sharded cluster.
mongo-c-driver 1.17.1
=====================
Bug fixes:
* Fix SRV/TXT record lookup for DNS records exceeding 1024 bytes.
mongo-c-driver 1.17.0
=====================
This release adds support for MongoDB 4.4 servers.
Features:
* Support streamable server monitoring to reduce recovery time when the server topology changes.
* Support the MONGODB-AWS authentication mechanism.
* Support Online Certificate Status Protocol (OCSP).
* Support configuring hedged reads in read preferences.
* Reduce the number of round trips necessary for SCRAM and X509 authentication.
* Monitor servers in parallel when using a mongoc_client_pool_t instead of doing serial scans.
* Support the "hint" option in operations using the update, replace, delete, and findAndModify commands.
* Improve behavior for retryable writes.
* Improve resuming behavior of change streams on server errors.
* Remove restriction of 255 character collection namespaces.
Bug fixes:
* Fix criteria for resumable errors in change streams.
* Fix rare crashes when server is invalidated during authentication.
* Reject client session for mongoc_collection_estimated_document_count.
* Fix behavior of a SecondaryPreferred read preference for exhaust cursor operations against a sharded cluster. Prior to the fix, a nonzero maxStalenessSeconds would not trigger sending the read preference.
* Fix SRV polling. Prior to the fix, SRV polling did not properly apply newly discovered results.
* Fix checks for existing GridFS indexes to handle indexes created by the MongoDB shell.
* Fix possible use of invalidated streams during an unordered OP_QUERY bulk write, and when ending many pooled sessions at client destruction.
* Fix a crash when setting the crl_file TLS option for Secure Channel.
* Avoid emitting duplicate ServerChanged events when no change is observed during monitoring.
* Properly handle large SASL messages instead of erroring.
Notes:
* Deprecated "lib" prefixed artifacts are no longer produced when building on Windows.
SQLite Release 3.34.0
Added the sqlite3_txn_state() interface for reporting on the current transaction state of the database connection.
Enhance recursive common table expressions to support two or more recursive terms as is done by SQL Server, since this helps make queries against graphs easier to write and faster to execute.
Improved error messages on CHECK constraint failures.
CLI enhancements:
The .read dot-command now accepts a pipeline in addition to a filename.
Added options --data-only and --nosys to the .dump dot-command.
Added the --nosys option to the .schema dot-command.
Table name quoting works correctly for the .import dot-command.
The generate_series(START,END,STEP) table-valued function extension is now built into the CLI.
The .databases dot-command now show the status of each database file as determined by sqlite3_db_readonly() and sqlite3_txn_state().
Added the --tabs command-line option that sets .mode tabs.
The --init option reports an error if the file named as its argument cannot be opened. The --init option also now honors the --bail option.
Query planner improvements:
Improved estimates for the cost of running a DISTINCT operator.
When doing an UPDATE or DELETE using a multi-column index where only a few of the earlier columns of the index are useful for the index lookup, postpone doing the main table seek until after all WHERE clause constraints have been evaluated, in case those constraints can be covered by unused later terms of the index, thus avoiding unnecessary main table seeks.
The new OP_SeekScan opcode is used to improve performance of multi-column index look-ups when later columns are constrained by an IN operator.
The BEGIN IMMEDIATE and BEGIN EXCLUSIVE commands now work even if one or more attached database files are read-only.
Enhanced FTS5 to support trigram indexes.
Improved performance of WAL mode locking primitives in cases where there are hundreds of connections all accessing the same database file at once.
Enhanced the carray() table-valued function to include a single-argument form that is bound using the auxiliary sqlite3_carray_bind() interface.
The substr() SQL function can now also be called "substring()" for compatibility with SQL Server.
The syntax diagrams are now implemented as Pikchr scripts and rendered as SVG for improved legibility and ease of maintenance.
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.
2.1.3 (2020-09-28)
* Removed old/unused appveyor config
* Remove old Rubies from CI & cross compile list
* Add Ruby 2.6 and 2.7 to the cross compile list
=== 5.37.0 (2020-10-01)
* Recognize more unsigned decimal/float types in the schema dumper (akimd, jeremyevans) (#1720)
* Add Postgres::PGRow::{Array,Hash}Row#op to the pg_row_ops extension if the pg_row extension is loaded (jeremyevans)
* Add Model#column_previously_was and #column_previously_changed? to the dirty plugin (jeremyevans)
* Raise Migrator::Error if attempting to migrate down to a version where there are necessary migration files missing (jeremyevans) (#1716)
Update Ruby on Rails 6.0 related packages to 6.0.3.4.
This is security fix for ruby-actionpack60.
## Rails 6.0.3.4 (October 07, 2020) ##
* [CVE-2020-8264] Prevent XSS in Actionable Exceptions
PostgreSQL 13 contains many new features and enhancements, including:
* Space savings and performance gains from de-duplication of B-tree index entries
* Improved performance for queries that use aggregates or partitioned tables
* Better query planning when using extended statistics
* Parallelized vacuuming of indexes
* Incremental sorting
1.4.3
bug
[bug] [batch] [sqlite]
Added support to drop named CHECK constraints that are specified as part of a column, rather than table wide. Previously, only constraints associated with the table were considered.
[bug] [mysql] [ops]
Fixed issue where the MySQL dialect would not correctly render the server default of a column in an alter operation, if the operation were programmatically generated from an autogenerate pass as it would not accommodate for the full structure of the DefaultClause construct.
[bug] [batch] [sqlite]
Fixed issue where the CAST applied to a JSON column when copying a SQLite table during batch mode would cause the data to be lost, as SQLite’s CAST with JSON appears to convert the data to the value “0”. The CAST is now skipped in a dialect-specific manner, including for JSON columns on SQLite. Pull request courtesy Sebastián Ramírez.
[bug] [commands]
The alembic current command no longer creates an alembic_version table in the database if one does not exist already, returning no version as the current version. This allows checking for migrations in parallel without introducing race conditions. Pull request courtesy Nikolay Edigaryev.
[bug] [batch]
Fixed issue where columns in a foreign-key referenced table would be replaced with null-type columns during a batch operation; while this did not generally have any side effects, it could theoretically impact a batch operation that also targets that table directly and also would interfere with future changes to the .append_column() method to disallow implicit replacement of columns.
[bug] [mssql]
Fixed issue where the mssql_drop_foreign_key=True flag on op.drop_column would lead to incorrect syntax error due to a typo in the SQL emitted, same typo was present in the test as well so it was not detected. Pull request courtesy Oleg Shigorin.
OpenLDAP 2.4.54
Fixed slapd delta-syncrepl to ignore delete ops on deleted entry
Fixed slapd delta-syncrepl to be fully serialized
Fixed slapd delta-syncrepl MOD on zero-length context entry
Fixed slapd sessionlog to use a TAVL tree
Fixed slapd syncrepl to be fully serialized
Fixed slapd syncrepl to call check_syncprov on fresh consumer
Fixed slapd syncrepl to propagate errors from overlay_entry_get_ov
Fixed slapd syncrepl to not create empty ADD ops
Fixed slapd syncrepl replace usage on single valued attrs
Fixed slapd-monitor fix monitor_back_register_database for empty suffix DB
Fixed slapo-accesslog normalizer for reqStart
Fixed slapo-accesslog to not generate new contextCSN on purge
Fixed slapo-syncprov contextCSN generation with empty suffix
TimescaleDB is an open-source database designed to make SQL scalable for
time-series data. It is engineered up from PostgreSQL and packaged as a
PostgreSQL extension, providing automatic partitioning across time and space
(partitioning key), as well as full SQL support.
WWW: https://github.com/timescale/timescaledb
pkgsrc changes: Adjust API_DEPENDS to 2.0. I don't have a specific
reason, but the previous 1.4 is so ancient that accepting it defies
the Principle of Least Astonishment.
Note that regression tests crash, but in the same way as 3.0.1.
3.0.1, when committed, passed, and I believe this is about proj.
Upstream changes: Bug fixes
2.21.0
This release is built with Go 1.15, which deprecates X.509 CommonName
in TLS certificates validation.
In the unlikely case that you use the gRPC API v2 (which is limited to TSDB
admin commands), please note that we will remove this experimental API in the
next minor release 2.22.
[CHANGE] Disable HTTP/2 because of concerns with the Go HTTP/2 client.
[CHANGE] PromQL: query_log_file path is now relative to the config file.
[CHANGE] Promtool: Replace the tsdb command line tool by a promtool tsdb subcommand.
[CHANGE] Rules: Label rule_group_iterations metric with group name.
[FEATURE] Eureka SD: New service discovery.
[FEATURE] Hetzner SD: New service discovery.
[FEATURE] Kubernetes SD: Support Kubernetes EndpointSlices.
[FEATURE] Scrape: Add per scrape-config targets limit.
[ENHANCEMENT] Support composite durations in PromQL, config and UI, e.g. 1h30m.
[ENHANCEMENT] DNS SD: Add SRV record target and port meta labels.
[ENHANCEMENT] Docker Swarm SD: Support tasks and service without published ports.
[ENHANCEMENT] PromQL: Reduce the amount of data queried by remote read when a subquery has an offset.
[ENHANCEMENT] Promtool: Add --time option to query instant command.
[ENHANCEMENT] UI: Respect the --web.page-title parameter in the React UI.
[ENHANCEMENT] UI: Add duration, labels, annotations to alerts page in the React UI.
[ENHANCEMENT] UI: Add duration on the React UI rules page, hide annotation and labels if empty.
[BUGFIX] API: Deduplicate series in /api/v1/series.
[BUGFIX] PromQL: Drop metric name in bool comparison between two instant vectors.
[BUGFIX] PromQL: Exit with an error when time parameters can't be parsed.
[BUGFIX] Remote read: Re-add accidentally removed tracing for remote-read requests.
[BUGFIX] Rules: Detect extra fields in rule files.
[BUGFIX] Rules: Disallow overwriting the metric name in the labels section of recording rules.
[BUGFIX] Rules: Keep evaluation timestamp across reloads.
[BUGFIX] Scrape: Do not stop scrapes in progress during reload.
[BUGFIX] TSDB: Fix chunks.HeadReadWriter: maxt of the files are not set error.
[BUGFIX] TSDB: Delete blocks atomically to prevent corruption when there is a panic/crash during deletion.
[BUGFIX] Triton SD: Fix a panic when triton_sd_config is nil.
[BUGFIX] UI: Fix react UI bug with series going on and off.
[BUGFIX] UI: Fix styling bug for target labels with special names in React UI.
[BUGFIX] Web: Stop CMUX and GRPC servers even with stale connections, preventing the server to stop on SIGTERM.
1.57 2020-09-18T06:57:48Z
- Fixed bug rt133358 t/016_mock_add_resultset_test.t fails (with older DBI)
1.56 2020-09-17T14:35:10Z
- The DBD::st module now supports the last_insert_id method
- Result sets with callbacks can now specify a last_insert_id
3.33.0-r1
Small performance improvement in string handling
apsw module exposes Cursor, Blob, and Backup types (APSW issue 273)
pkg-config is used to detect International Components for Unicode (ICU) sdk when the SQLite ICU extension <https://www.sqlite.org/src/artifact?ci=trunk&filename=ext/icu/README.txt>`___ is enabled. It falls back to icu-config as before..
Added constants:
SQLITE_OPEN_SUPER_JOURNAL
0.16.15
Make DateField accept valid date str.
Add QuerySet.select_for_update().
check default for not None on pydantic model creation
propagate default to pydantic model
Add QuerySet.select_related().
Add custom attribute name for Prefetch instruction.
Add db_constraint for RelationalField family.
Now requires c++17.
Headline:
Easier, faster, neater: the transaction classes now have a stream
method. You specify a query and the C++ types to which you want
the fields converted, and you get to iterate over the rows. And
thanks to C++14 structured bindings, you can read the fields
straight into separate local variables:
for (auto const [id, name]:
tx.stream<int, std::string_view>("SELECT id, name FROM thing"))
{
process(id, name);
}
For super-fast access to a field's text-format contents, convert
it to std::string_view. It'll give you an immediate reference
to the buffer containing the field. Beware though: the buffer
only holds that text for the one iteration. The next iteration
will overwrite it.
Full list of changes at:
https://github.com/jtv/libpqxx/blob/7.1.2/NEWS
2.3.9
Fix that broke several driver builds. Sorry
2.3.8
Add configure support for editline
SQLDriversW was ignoring user config
SQLDataSources Fix termination character
Fix for pooling seg fault
Make calling SQLSetStmtAttrW call the W function in the driver is its there
Try and fix race condition clearing system odbc.ini file
Remove trailing space from isql/iusql SQL
When setting connection attributes set before connect also check if the W entry poins can be used
Try calling the W error functions first if available in the driver
Add iconvperdriver configure option to allow calling unicode_setup in SQLAllocHandle
iconv handles was being lost when reusing pooled connection
Catch null copy in iniPropertyInsert
Fix some leaks
Update ruby-sequel to 5.36.0.
=== 5.36.0 (2020-09-01)
* Handle passing keyword arguments through class methods defined via
Plugins.def_dataset_method on Ruby 2.7+ (jeremyevans)
* Handle passing keyword arguments through when loading plugins on Ruby 2.7+
(jeremyevans)
* Handle passing keyword arguments through migrations when defining custom
Database methods that accept keywords on Ruby 2.7+ (jeremyevans)
* Handle passing keyword arguments through Dataset#query when using the
query extension on Ruby 2.7+ (jeremyevans)
* Handle passing keyword arguments through the association proxy when using
the association_proxies plugin on Ruby 2.7+ (jeremyevans)
* Handle passing keyword arguments through the class method to a method
defined in dataset_module on Ruby 2.7+ (adam12) (#1713)
* Stream result sets in the odbc adapter for better performance and lower
memory usage (sparrovv) (#1711)
* Add Postgres::JSONBOp#set_lax and #path_*_tz methods to the pg_json_ops
extension for new jsonb functions added in PostgreSQL 13 (jeremyevans)
* Add Dataset#with_ties on PostgreSQL 13+ and Microsoft SQL Server to
include rows with same order as final row (jeremyevans)
* Add a :current_schema option to Database#view_exists? (only defined on
Oracle) to look in the current schema instead of non-system schemas
(jeremyevans) (#1710)
* Recognize another disconnect error in the mysql and mysql2 adapters
(jeremyevans) (#1706)
Update ruby-ldap to 0.9.20.
pkgsrc change: remove redundant "ruby" in CATEGORIES.
Wed Jul 11 21:58:38 UTC 2018 Alexey Chebotar <alexey.chebotar@gmail.com>
* Version 0.9.20
* Added support of LDAP_OPT_X_TLS_NEWCTX. Thanks to Kouhei Sutou.
Mon Jun 20 14:30:52 UTC 2016 Alexey Chebotar <alexey.chebotar@gmail.com>
* Version 0.9.19
* Fixed parsing of LDIF with CR LF line separators (GH-38).
Thanks to doppelreim.
Fri Mar 4 11:17:21 UTC 2016 Alexey Chebotar <alexey.chebotar@gmail.com>
* Version 0.9.18
* backout issue32 to compile for ruby-1.8.x.
Thanks to SUENAGA Hiroki.
Fri Feb 6 08:51:09 UTC 2015 Alexey Chebotar <alexey.chebotar@gmail.com>
* Version 0.9.17
* Use ruby object to keep LDAP search result instead of libldap's data structure.
* Use macro Check_LDAPENTRY for assertion inside native extension codes.
* Remove assertion code from macro GET_LDAPENTRY_DATA.
Thanks to SUENAGA Hiroki.
Update ruby-moneta to 1.4.0.
1.4.0 (2020-08-23)
* Adapters::Mongo - drop support for moped gem (#182)
* Adapters::Redis - use #exists? where available (#189)
* Some reorganisation of code into more separate files (#177)
Update ruby-activeldap to 6.0.3.
## 6.0.3: 2020-08-17 {#release-6-0-3}
### Improvements
* Added support for `save(validate: false)`.
[GitHub#180][Reported by Kevin McCormack]
* jndi: Added support for follow referrals.
[GitHub#182][Patch by Kevin McCormack]
### Fixes
* Fixed a bug that sub base is ignored in DN specified by `new`.
[GitHub#185][Reported by Kevin McCormack]
### Thanks
* Kevin McCormack
Redis 6.0.8
===========
Upgrade urgency HIGH: Anyone who's using Redis 6.0.7 with Sentinel or
CONFIG REWRITE command is affected and should upgrade ASAP.
Bug fixes:
* CONFIG REWRITE after setting oom-score-adj-values either via CONFIG SET or
loading it from a config file, will generate a corrupt config file that will
cause Redis to fail to start
* Fix issue with redis-cli --pipe on MacOS
* Fix RESP3 response for HKEYS/HVALS on non-existing key
* Various small bug fixes
New features / Changes:
* Remove THP warning when set to madvise
* Allow EXEC with read commands on readonly replica in cluster
* Add masters/replicas options to redis-cli --cluster call command
Module API:
* Add RedisModule_ThreadSafeContextTryLock
1.3.19
orm
[orm] [usecase]
Adjusted the workings of the Mapper.all_orm_descriptors() accessor to represent the attributes in the order that they are located in a deterministic way, assuming the use of Python 3.6 or higher which maintains the sorting order of class attributes based on how they were declared. This sorting is not guaranteed to match the declared order of attributes in all cases however; see the method documentation for the exact scheme.
orm declarative
[usecase] [declarative] [orm]
The name of the virtual column used when using the AbstractConcreteBase and ConcreteBase classes can now be customized, to allow for models that have a column that is actually named type. Pull request courtesy Jesse-Bakker.
sql
[sql] [bug]
Repaired an issue where the “ORDER BY” clause rendering a label name rather than a complete expression, which is particularly important for SQL Server, would fail to occur if the expression were enclosed in a parenthesized grouping in some cases. This case has been added to test support. The change additionally adjusts the “automatically add ORDER BY columns when DISTINCT is present” behavior of ORM query, deprecated in 1.4, to more accurately detect column expressions that are already present.
[sql] [bug] [datatypes]
The LookupError message will now provide the user with up to four possible values that a column is constrained to via the Enum. Values longer than 11 characters will be truncated and replaced with ellipses. Pull request courtesy Ramon Williams.
[sql] [bug]
Fixed issue where the Connection.execution_options.schema_translate_map feature would not take effect when the Sequence.next_value() function function for a Sequence were used in the Column.server_default parameter and the create table DDL were emitted.
postgresql
[postgresql] [bug]
Fixed issue where the return type for the various RANGE comparison operators would itself be the same RANGE type rather than BOOLEAN, which would cause an undesirable result in the case that a TypeDecorator that defined result-processing behavior were in use. Pull request courtesy Jim Bosch.
mysql
[mysql] [usecase]
The MySQL dialect will render FROM DUAL for a SELECT statement that has no FROM clause but has a WHERE clause. This allows things like “SELECT 1 WHERE EXISTS (subquery)” kinds of queries to be used as well as other use cases.
[mysql] [bug]
Fixed an issue where CREATE TABLE statements were not specifying the COLLATE keyword correctly.
[mysql] [bug]
Added MariaDB code 1927 to the list of “disconnect” codes, as recent MariaDB versions apparently use this code when the database server was stopped.
sqlite
[sqlite] [bug] [mssql] [reflection]
Applied a sweep through all included dialects to ensure names that contain single or double quotes are properly escaped when querying system tables, for all Inspector methods that accept object names as an argument (e.g. table names, view names, etc). SQLite and MSSQL contained two quoting issues that were repaired.
mssql
[mssql] [bug] [sql]
Fixed bug where the mssql dialect incorrectly escaped object names that contained ‘]’ character(s).
misc
[usecase] [py3k]
Added a **kw argument to the DeclarativeMeta.__init__() method. This allows a class to support the PEP 487 metaclass hook __init_subclass__.
OpenLDAP 2.4.53
Added slapd syncrepl additional SYNC logging
Fixed slapd syncrepl segfault on NULL cookie on REFRESH
Fixed slapd syncrepl to use fresh connection on REFRESH fallback
Fixed slapo-ppolicy race condition for pwdFailureTime
Build
Require OpenSSL 1.0.2 or later
Fixed libldap compilation issue with broken C compilers
Redis 6.0.7
Upgrade urgency MODERATE: several bugs with moderate impact are fixed,
Specifically the first two listed below which cause protocol errors for clients.
Bug fixes:
* CONFIG SET could hung the client when arrives during RDB/ROF loading (When
processed after another command that was also rejected with -LOADING error)
* LPOS command when RANK is greater than matches responded wiht broken protocol
(negative multi-bulk count)
* UNLINK / Lazyfree for stream type key would have never do async freeing
* PERSIST should invalidate WATCH (Like EXPIRE does)
* EXEC with only read commands could have be rejected when OOM
* TLS: relax verification on CONFIG SET (Don't error if some configs are set
and tls isn't enabled)
* TLS: support cluster/replication without tls-port
* Systemd startup after network is online
* Redis-benchmark improvements
* Various small bug fixes
New features:
* Add oom-score-adj configuration option to control Linux OOM killer
* Show IO threads statistics and status in INFO output
* Add optional tls verification mode (see tls-auth-clients)
Module API:
* Add RedisModule_HoldString
* Add loaded keyspace event
* Fix RedisModuleEvent_LoadingProgress
* Fix RedisModuleEvent_MasterLinkChange hook missing on successful psync
* Fix missing RM_CLIENTINFO_FLAG_SSL
* Refactor redismodule.h for use with -fno-common / extern
2.8.1:
- fixed regression in 2.8 for members returned in AD auto-range search
- fixed regression in 2.8 for attribute error in restartable class
- try to use Crypto library if present for hashing NTLM password on python interpreter missing the MD4 OpenSSL algorithm
OpenLDAP 2.4.52 (2020/08/28)
Added libldap LDAP_OPT_X_TLS_REQUIRE_SAN option
Added libldap OpenSSL support for multiple EECDH curves
Added slapd OpenSSL support for multiple EECDH curves
Fixed librewrite malloc/free corruption
Fixed libldap hang when using UDP and server down
Fixed slapd syncrepl rare deadlock due to network issues
Fixed slapd syncrepl regression that could trigger an assert
Fixed slapd-mdb index error with collapsed range
1.08 Sat Jan 18 2020 Todd Rinaldo
Switch testing to github actions
update MANIFEST and .gitignorew
Switch to github issues
1.07 Tue Apr 12 2016 Todd Rinaldo
Stop using vars in favor of ours
Add Travis support
Debian QA tool tidy fix
Apply Perl::Tidy 20150815 and track .perltidyrc
Fixes RT 104338 - prepare fails when a question mark appears in a text field
Add an explicit minimum version of perl supported
Add warnings.
0.819 (06.16.2020) - John Siracusa <siracusa@gmail.com>
* Attempt to fix a failing test by adding a workaround for an undef
return value from crypt().
0.818 (06.08.2020) - John Siracusa <siracusa@gmail.com>
* Fixed tests that were failing due to "future" dates that are
now in the past (RT 132782)
0.817 (04.05.2020) - John Siracusa <siracusa@gmail.com>
* Added missing module load in Rose::DB::Object::Metadata::Util
(RT 132300)
0.816 (04.03.2020) - John Siracusa <siracusa@gmail.com>
* Updated to support DBD::Pg 3.8.0 and later.
0.783 (04.06.2020) - John Siracusa <siracusa@gmail.com>
* Fixed a bug in DBD::Pg version detection.
0.782 (04.03.2020) - John Siracusa <siracusa@gmail.com>
* Added workarounds for changes to the behavior of the TABLE_CAT catalog
name key in DBD::Pg 3.8.0 and later.
0.781 (01.06.2020) - John Siracusa <siracusa@gmail.com>
* Corrected the MANIFEST file. Fixed MariaDB test counts.
0.780 (01.06.2020) - John Siracusa <siracusa@gmail.com>
* Added basic support for MariaDB. (Patch by Peter Karman.)
0.779 (08.09.2019) - John Siracusa <siracusa@gmail.com>
* Added skip_locked support for PostgreSQL. (Patch by fhendrikx.)
1.998 2020-08-18 11:04:12+02:00 Europe/Paris
* remove test expression that is problematic on OpenBSD and NetBSD
1.997 2020-80-17 10:03:00+01:00 Europe/Paris
* various travis fixes
* #112 applied
* enable unix socket tests by enabling them in the local test server
* #144: change exists into defined
* #146: Fix sentinel option typo
1.996 2020-03-05 16:17:21+01:00 Europe/Paris
1.996 2020-03-05 11:56:11+01:00 Europe/Paris
* #139: Fix for "Unexpected error condition 104/linux"
1.995 2019-07-22 11:20:07+02:00 Europe/Paris
* revert #136, remove deps that are in core, as it breaks builds in some setup
1.994 2019-07-22 07:51:57+02:00 Europe/Paris
* Don't send SELECT if current database equals the one being selected (@dallaylaen, #132)
1.993 2019-07-22 07:01:30+02:00 Europe/Paris
* fix missing deps (@manwar, #136 )
1.992 2019-07-21 18:27:23+02:00 Europe/Paris
* relax the check in 04-pipeline.t about unknown command output (#130)
2.036000 2020-03-28 14:16:39-07:00 America/Los_Angeles
- fix remove_columns shortcut to add the 'remove_columns' attribute
in case it is missing (Karen Etheridge, #101)
- Add support for query condition to results_exist() and
results_exist_as_query() in Helper::ResultSet::Shortcut::ResultsExist
(Daniel Böhmer, GH#102)
2.035000 2020-02-21 08:38:42-08:00 America/Los_Angeles
- add remove_columns shortcut (Karen Etheridge, GH#100)
0.082842 2020-06-16 20:10 (UTC)
* New Features
- An on_connect rebase_sqlmaker call allowing experimentation with
non-core SQL generators on a per-$schema-instance basis
https://is.gd/DBIC_rebase_sqlmaker
- Automatically detect and use multi-column IN on recent versions of
libsqlite: ... WHERE ( foo, bar ) IN ( SELECT foo, bar FROM ... )
* Fixes
- Fix silent failure to retrieve a primary key (RT#80283) or worse:
returning an incorrect value (RT#115381) in case a rdbms-side autoinc
column is declared as PK with the is_auto_increment attribute unset
- Fix overly-aggressive condition unrolling, corrupting custom ops with
array arguments (RT#132390)
- Fix docs on how to properly use Moo(se) in ResultSet's, and fix a
corner case of ->count not functioning properly when the old recipe
was being used (GH#105)
- Fix incorrect ::Storage->_ping() behavior under Sybase (RT#114214)
- Work around breakage in Hash::Merge by soft-requiring Clone as part
of the replicated subsystem (RT#124321)
* Misc
- DBIC_TRACE_PROFILE=... now uses a ::Storage::Statistics subclass
DBIx::Class::Storage::Debug::PrettyTrace which properly ships as a
part of this distrinbution
- Switch out SQL::Abstract dependency with a slower moving dist
- Remove Data::Page dependency by inlining its entirety into the core
DBIx::Class::ResultSet::Pager (RT#130686)
This module was inspired by the excellent DBIx::Abstract. However,
in using that module I found that what I really wanted to do was
generate SQL, but still retain complete control over my statement
handles and use the DBI interface. So, I set out to create an
abstract SQL generation module.
11.97
- Add missing dependencies.
- Document some awkward behaviour. RT#21200
11.96_03
- Add options for handling of booleans. RT#53311 (Mike Pomraning)
11.96_02
- Add missing versions to this file. RT#39187
- Be more helpful if DBI::Shell::Spool is missing. RT#24538
- Give every .pm a version identifier.
11.96_01
- Suppress warning in DBI::Format::SQLMinus. RT#123216 (Kent Fredric)
11.96
- Automatically save command history.
- Remove warning message.
- Correct links in POD to work in metacpan.
- Tidy up metadata.
11.95_03
- Correct sense of interactivity check.
11.95_02
- Use IO::Interactive.
11.95_01
- Resolved RT#123215, warning from File::Find.
- Added RT#65253, permit empty passwords.
- Resolved RT#121136, testing without "." in @INC.
- Resolved RT#73873, warning fix.
- Possibly resolved RT#12167, missing dependency on DBI.
- Switch build to Dist::Zilla.
Version 3.14.2 (released August 13, 2020)
- Fix ENV typo in the test suite
[Gregor Herrmann]
- Renamed and enhanced test helper script: dbdpg_test_postgres_versions.pl
[Greg Sabino Mullane]
Version 3.14.1 (released August 12, 2020)
- Force the version string so undefined errors in the "driver" sub go away.
[Greg Sabino Mullane]
(RT ticket #83057)
Version 3.14.0 (released July 19, 2020)
- The $dbh->primary_key_info and $dbh->foreign_key_info methods will now always return
a statement handle, even with no matches. Previously, they returned undef directly.
Callers can check if the returned handle contains any rows.
[Greg Sabino Mullane]
- The $dbh->tables method will always return a list, even if it is empty.
[Greg Sabino Mullane]
- Add pg_lo_tell64, pg_lo_seek64, and pg_lo_truncate64, for anyone dealing
with really, really, really large 'large objects'. Requires Postgres 9.3 or better.
[Greg Sabino Mullane]
(RT ticket #123561)
- Allow test to run again when using a non-superuser to connect
[Greg Sabino Mullane]
(RT ticket #132865)
- Adjust tests to force loading proper version of DBD::Pg every time.
[Greg Sabino Mullane]
- Removed the long-deprecated _pg_use_catalog method.
[Greg Sabino Mullane]
- Many improvements and changes to the test suite.
[Greg Sabino Mullane]
Version 3.13.0 (released June 17, 2020)
- Redo the "last_result" internals in dbdimp.c, which
fixes a memory leak.
[Greg Sabino Mullane]
(RT ticket #132812)
- Fix regression in Perl length() for returned query results
[Jon Jensen]
(Github issue #72)
- Make $sth->finish() do a little less. Notably, even
after calling finish(), pg_error_field will still work
on the last action performed.
[Greg Sabino Mullane]
- Tweak tests so Windows boxes pass
[Greg Sabino Mullane]
Version 3.12.3 (released June 5, 2020)
- Prevent DBI from flipping AutoCommit to 'on' after a failed commit
[Greg Sabino Mullane]
(Github issue #71)
Version 3.12.2 (released June 4, 2020)
- Revert overly aggressive testing shortcut as it can cause installs to fail
[Greg Sabino Mullane, with apologies]
Version 3.12.1 (released June 3, 2020)
- Remove test that assumed '(12,34)' is an invalid entry for type "circle",
as the Postgres source code changed this behavior on April 7, 2020
[Greg Sabino Mullane]
(RT ticket #132740)
Version 3.12.0 (released May 7, 2020)
- Add CONTRIBUTING.md file
- Return the table info row last in statistics_info.
This fixes statistics_info on pre-8.3 servers.
[Dagfinn Ilmari Mannsåker]
- Fix ASC_OR_DESC field in statistics_info
[Dagfinn Ilmari Mannsåker]
- Indicate NULL ordering in statistics_info
[Dagfinn Ilmari Mannsåker]
Version 3.11.1 (released April 28, 2020)
- Adjust Makefile to fix failing 'fulltest' target on BSD systems
[Slaven Rezić]
(RT ticket #132412)
Version 3.11.0 (released April 23, 2020)
- Indicate non-key index columns (INCLUDE) in statistics_info
[Dagfinn Ilmari Mannsåker]
- Return an empty result set instead of undef from statistics_info
when the requested table doesn't exist and $unique_only is false.
[Dagfinn Ilmari Mannsåker]
- Fix segfault during st destroy
[Gregory Oschwald]
(Github pull request #66)
(Github issue #57)
- Improve testing for table_info()
[Greg Sabino Mullane]
(Github issue #67)
- Improve UTF-8 wording in docs
[Felipe Gasper]
(Github pull request #65)
Version 3.10.5 (released March 23, 2020)
- Minor adjustment for Windows build
(RT ticket #131752)
- Allow test suite to work on an EnterpriseDB server
[H.Merijn Brand]
(RT ticket #132203)
- Add small warning regarding ShowErrorStatement
(RT ticket #120268)
Version 3.10.4 (released February 3, 2020)
- Allow localtime from Time::Piece to be used directly as a bind value again.
This applies to all "magical" arrays.
[Greg Sabino Mullane]
(Github issue #63)
- Force tests to NOT run in parallel.
[Greg Sabino Mullane]
(RT ticket #130834)
Version 3.10.3 (released January 20, 2020)
- Set things cleared via PQclear to NULL as soon as possible, to remove race conditions
[Greg Sabino Mullane]
(RT ticket #131522)
Version 3.10.2 (released January 17, 2020)
- Adjust tests to pass on 32-bit machines
[Greg Sabino Mullane]
(RT ticket #131482)
Version 3.10.1 (released January 13, 2020)
- Prevent double-free memory errors
[Greg Sabino Mullane]
(RT ticket #130681)
- Fix crash when pg_error_field is called
[Greg Sabino Mullane]
(RT ticket #130721)
- Update the list of Postgres reserved words in quote.c
Version 3.10.0 (released September 3, 2019)
- Prevent memory leak related to pg_error_field
[Greg Sabino Mullane]
(RT ticket #130430)
- Fix for bug by making sure pg_error_field works properly when switching between
do-with-params and do-without-params.
[Greg Sabino Mullane]
(Github issue #57)
- If a commit or rollback fails, do not set BegunWork
[Greg Sabino Mullane]
(Github issue #40)
- Treat partitioned tables same as regular tables for column_info, table_info,
and foreign_key_info (i.e. support pg_class.relkind = 'p')
[Octavian R. Corlade]
(Github pull request #55)
- Allow last_insert_id() to work against inherited tables
[Greg Sabino Mullane]
(RT ticket #52441)
- Add DBI SQL_BLOB, SQL_BINARY and SQL_LONGVARBINARY types as alias for PG_BYTEA
[Pali]
(Github pull request #58)
1.66 2020-08-30
- Switched to a production version
1.65_03 2020-07-27
- Upgraded SQLite to 3.32.3
1.65_02 2020-02-08
- Upgraded SQLite to 3.31.1
1.65_01 2020-01-18
- Upgraded SQLite to 3.30.1
- Added several SQL_ types as alias (pali++)
- Fixed two initialization issues (ppisar++)
- Allowed create_function to return an array reference
to specify the type of the value
1.61 2020-01-30
[BUG FIXES]
Fix 12blob.t test by pali
Fix searching for ODBC libraries in system by pali (#15)
[ENHANCEMENTS]
use PERL_NO_GET_CONTEXT for more performance by markusbeth (#13)
[MISCELLANEOUS]
Fix travis builds for older Perls by pali
1.55 2019-12-30T14:20:00Z
- Fixed bug rt131264 t/033_table_info.t fails (with older DBI)
1.54 2019-12-23T12:44:22Z
- Added Bernhard Graf's 'Feature: one shot failure' merge request.
- Fixed description of the failure attribute of mock_add_resultset. It
no longer claims to support a hash ref (as it doesn't). Thanks to
Bernhard Graf for both the bug report and a merge request that fixes it.
- Fixed bug where it wasn't possible to replace a regular expression
mock resultset. Thanks to Bernhard Graf for both the bug report and
a merge request that fixes it.
- Fixed bug where the failure attribute wasn't working with regular
expression mock resultsets. Thanks to Bernhard Graf for both the bug
report and a merge request that fixes it.
1.53 2019-12-03T10:50:57Z
- Error handling in mock_add_resultset is no longer experimental
- Attribute Aliasing is no longer experimental
1.52 2019-10-28T11:35:41Z
- Added in callback feature for result sets so that their contents
can be more dynamic.
1.51 2019-10-23T11:43:51Z
- Fixed issue with using attribute aliases alongside a driver DSN
in the DBI->connect call
1.50 2019-10-22T19:37:26Z
- Added attribute aliases support for MariaDB
Version 2.11 - 9 Jul 2020
- Introduction of the barman-cli-cloud package that contains all cloud
related utilities.
- Add barman-cloud-wal-restore to restore a WAL file previously
archived with barman-cloud-wal-archive from an object store
- Add barman-cloud-restore to restore a backup previously taken with
barman-cloud-backup from an object store
- Add barman-cloud-backup-list to list backups taken with
barman-cloud-backup in an object store
- Add support for arbitrary archive size for barman-cloud-backup
- Add support for --endpoint-url option to cloud utilities
- Remove strict superuser requirement for PG 10+ (by Kaarel Moppel)
- Add --log-level runtime option for barman to override default log
level for a specific command
- Support for PostgreSQL 13
- Bug fixes:
- Suppress messages and warning with SSH connections in barman-cli
(GH-257)
- Fix a race condition when retrieving uploaded parts in
barman-cloud-backup (GH-259)
- Close the PostgreSQL connection after a backup (GH-258)
- Check for uninitialized replication slots in receive-wal --reset
(GH-260)
- Ensure that begin_wal is valorised before acting on it (GH-262)
- Fix bug in XLOG/WAL arithmetic with custom segment size (GH-287)
- Fix rsync compatibility error with recent rsync
- Fix PostgreSQLClient version parsing
- Fix PostgreSQL exception handling with non ASCII messages
- Ensure each postgres connection has an empty search_path
- Avoid connecting to PostgreSQL while reading a backup.info file
If you are using already barman-cloud-wal-archive or barman-cloud-backup
installed via RPM/Apt package and you are upgrading your system, you
must install the barman-cli-cloud package. All cloud related tools are
now part of the barman-cli-cloud package, including
barman-cloud-wal-archive and barman-cloud-backup that were previosly
shipped with barman-cli. The reason is complex dependency management of
the boto3 library, which is a requirement for the cloud utilities.
Version 2.10 - 5 Dec 2019
- Pull .partial WAL files with get-wal and barman-wal-restore,
allowing restore_command in a recovery scenario to fetch a partial
WAL file's content from the Barman server. This feature simplifies
and enhances RPO=0 recovery operations.
- Store the PostgreSQL system identifier in the server directory and
inside the backup information file. Improve check command to verify
the consistency of the system identifier with active connections
(standard and replication) and data on disk.
- A new script called barman-cloud-wal-archive has been added to the
barman-cli package to directly ship WAL files from PostgreSQL (using
archive_command) to cloud object storage services that are
compatible with AWS S3. It supports encryption and compression.
- A new script called barman-cloud-backup has been added to the
barman-cli package to directly ship base backups from a local
PostgreSQL server to cloud object storage services that are
compatible with AWS S3. It supports encryption, parallel upload,
compression.
- Automated creation of replication slots through the server/global
option create_slot. When set to auto, Barman creates the replication
slot, in case streaming_archiver is enabled and slot_name is
defined. The default value is manual for back-compatibility.
- Add '-w/--wait' option to backup command, making Barman wait for all
required WAL files to be archived before considering the backup
completed. Add also the --wait-timeout option (default 0, no
timeout).
- Redact passwords from Barman output, in particular from
barman diagnose (InfoSec)
- Improve robustness of receive-wal --reset command, by verifying that
the last partial file is aligned with the current location or, if
present, with replication slot's.
- Documentation improvements
- Bug fixes:
- Wrong string matching operation when excluding tablespaces
inside PGDATA (GH-245)
- Minor fixes in WAL delete hook scripts (GH-240)
- Fix PostgreSQL connection aliveness check (GH-239)
Version 2.9 - 1 Aug 2019
- Transparently support PostgreSQL 12, by supporting the new way of
managing recovery and standby settings through GUC options and
signal files (recovery.signal and standby.signal)
- Add --bwlimit command line option to set bandwidth limitation for
backup and recover commands
- Ignore WAL archive failure for check command in case the latest
backup is WAITING_FOR_WALS
- Add --target-lsn option to set recovery target Log Sequence Number
for recover command with PostgreSQL 10 or higher
- Add --spool-dir option to barman-wal-restore so that users can
change the spool directory location from the default, avoiding
conflicts in case of multiple PostgreSQL instances on the same
server (thanks to Drazen Kacar).
- Rename barman_xlog directory to barman_wal
- JSON output writer to export command output as JSON objects and
facilitate integration with external tools and systems (thanks to
Marcin Onufry Hlybin). Experimental in this release.
Bug fixes:
- replication-status doesn’t show streamers with no slot (GH-222)
- When checking that a connection is alive (“SELECT 1” query),
preserve the status of the PostgreSQL connection (GH-149). This
fixes those cases of connections that were terminated due to
idle-in-transaction timeout, causing concurrent backups to fail.
Version 2.8 - 17 May 2019
- Add support for reuse_backup in geo-redundancy for incremental
backup copy in passive nodes
- Improve performance of rsync based copy by using strptime instead of
the more generic dateutil.parser (#210)
- Add ‘--test’ option to barman-wal-archive and barman-wal-restore to
verify the connection with the Barman server
- Complain if backup_options is not explicitly set, as the future
default value will change from exclusive_backup to concurrent_backup
when PostgreSQL 9.5 will be declared EOL by the PGDG
- Display additional settings in the show-server and diagnose
commands: archive_timeout, data_checksums, hot_standby,
max_wal_senders, max_replication_slots and wal_compression.
- Merge the barman-cli project in Barman
- Bug fixes:
- Fix encoding error in get-wal on Python 3 (Jeff Janes, #221)
- Fix exclude_and_protect_filter (Jeff Janes, #217)
- Remove spurious message when resetting WAL (Jeff Janes, #215)
- Fix sync-wals error if primary has WALs older than the first
backup
- Support for double quotes in synchronous_standby_names setting
- Minor changes:
- Improve messaging of check --nagios for inactive servers
- Log remote SSH command with recover command
- Hide logical decoding connections in replication-status command
This release officially supports Python 3 and deprecates Python 2 (which
might be discontinued in future releases).
PostgreSQL 9.3 and older is deprecated from this release of Barman.
Support for backup from standby is now limited to PostgreSQL 9.4 or
higher and to WAL shipping from the standby (please refer to the
documentation for details).
Version 2.7 - 21 Mar 2019
- Fix error handling during the parallel backup. Previously an
unrecoverable error during the copy could have corrupted the barman
internal state, requiring a manual kill of barman process with
SIGTERM and a manual cleanup of the running backup in PostgreSQL.
(GH#199)
- Fix support of UTF-8 characters in input and output (GH#194 and
GH#196)
- Ignore history/backup/partial files for first sync of geo-redundancy
(GH#198)
- Fix network failure with geo-redundancy causing cron to break
(GH#202)
- Fix backup validation in PostgreSQL older than 9.2
- Various documentation fixes
Version 2.6 - 4 Feb 2019
- Add support for Geographical redundancy, introducing 3 new commands:
sync-info, sync-backup and sync-wals. Geo-redundancy allows a Barman
server to use another Barman server as data source instead of a
PostgreSQL server.
- Add put-wal command that allows Barman to safely receive WAL files
via PostgreSQL's archive_command using the barman-wal-archive script
included in barman-cli
- Add ANSI colour support to check command
- Minor fixes:
- Fix switch-wal on standby with an empty WAL directory
- Honour archiver locking in wait_for_wal method
- Fix WAL compression detection algorithm
- Fix current_action in concurrent stop backup errors
- Do not treat lock file busy as an error when validating a backup
Version 1.18.1 - 2018-10-27
* Fix debian bug 910911
This restores backward compatibility with databases created by version
1.8 (and some later versions, with mmapped I/O disabled).
See https://bugs.debian.org/910911 for a detailed description.
Version 1.18 - 2018-08-21
* Bugfixes:
** Fix directory entry validation
See https://puszcza.gnu.org.ua/bugs/?402
Directory validation function would falsely report corruption after
several directory reallocations.
** Fix improper use of GDBM_DEBUG macro
See https://puszcza.gnu.org.ua/bugs/?401
** Fix spurious error from gdbm_dump and gdbm_export
The functions incorrectly reported as error the GDBM_ITEM_NOT_FOUND
status, which is reported when upon normal termination of iteration
over the database keys.
** Make sure gdbm_sync always returns a meaningful value
See https://puszcza.gnu.org.ua/bugs/?400
Version 1.17 - 2018-07-30
* int gdbm_close and gdbm_sync
Both functions now return 0 on success. On error, they return -1
and set gdbm_errno and errno to the appropriate error codes.
* Fix bug in gdbm_dump function
The function did not clear the GDBM_ITEM_NOT_FOUND error marker, which
is set upon its normal termination.
Version 1.16 - 2018-06-27
* Maintain sorting order of the available block list after coalescing
This is a very long-standing bug, dated back to the time when optional
coalescing of available blocks with the newly released block was
introduced. Merging the released block with an adjacent block of
available space would clobber the sorting order of the available list.
The bug was discovered due to strict database consistency checks,
introduced in version 1.15.
The fix introduced in this version will silently restore the proper
sorting order of available block list before its use.
* Improve block merging algorithm
New implementation of block merging algorithm will correctly handle
both left and right-adjacent blocks.
Version 1.15 - 2018-06-15
* Extensive database consistency checking
GDBM tries to detect inconsistencies in input database files as
early as possible. When an inconcistency is detected, a helpful
diagnostics is returned and the database is marked as needing
recovery. From this moment on, any GDBM function trying to access
the database will immediately return error code (instead of
eventually segfaulting as previous versions did). In order to
reconstruct the database and return it to healthy state, the
gdbm_recover function should be used.
Special thanks to Lionel Debroux and Craig Young for investing
their time and efforts in testing and providing valuable feedback.
* Improved error checking
* Removed gdbm-1.8.3 compatibility layer
* Commands can be given to gdbmtool in the command line
The syntax is:
gdbmtool DBNAME COMMAND [ARGS...]
Multiple commands are separated by semicolon (take care to escape it),
e.g.:
gdbmtool t.db count\; avail
* Fixed data conversion bugs in storing structured keys or content
* New member in the gdbm_recovery structure: duplicate_keys.
Upon return from gdbm_recover, this member holds the number of keys
that has not been recovered, because the same key had already been stored
in the database. The actual number of stored keys is thus
recovered_keys - duplicate_keys.
* New error codes.
GDBM_BAD_BUCKET "Malformed bucket header"
GDBM_BAD_HEADER "Malformed database file header"
GDBM_BAD_AVAIL "Malformed avail_block"
GDBM_BAD_HASH_TABLE "Malformed hash table"
GDBM_BAD_DIR_ENTRY "Invalid directory entry"
redis does not look in a particular path but wants the config file
path passed on the command line. The SMF script already did this,
but the rc.d script passed configuration on the command line,
causing redis to neither write a log file nor a database by default.
Bump PKGREVISION.
SQLite Release 3.33.0
Support for UPDATE FROM following the PostgreSQL syntax.
Increase the maximum size of database files to 281 TB.
Extended the PRAGMA integrity_check statement so that it can optionally be limited to verifying just a single table and its indexes, rather than the entire database file.
Added the decimal extension for doing arbitrary-precision decimal arithmetic.
Enhancements to the ieee754 extension for working with IEEE 754 binary64 numbers.
CLI enhancements:
Added four new output modes: "box", "json", "markdown", and "table".
The "column" output mode automatically expands columns to contain the longest output row and automatically turns ".header" on if it has not been previously set.
The "quote" output mode honors ".separator"
The decimal extension and the ieee754 extension are built-in to the CLI
Query planner improvements:
Add the ability to find a full-index-scan query plan for queries using INDEXED BY which previously would fail with "no query solution".
Do a better job of detecting missing, incomplete, and/or dodgy sqlite_stat1 data and generates good query plans in spite of the misinformation.
Improved performance of queries like "SELECT min(x) FROM t WHERE y IN (?,?,?)" assuming an index on t(x,y).
In WAL mode, if a writer crashes and leaves the shm file in an inconsistent state, subsequent transactions are now able to recover the shm file even if there are active read transactions. Before this enhancement, shm file recovery that scenario would result in an SQLITE_PROTOCOL error.
PostgreSQL 12.4, 11.9, 10.14, 9.6.19, 9.5.23
Security Issues
CVE-2020-14349: Uncontrolled search path element in logical replication.
Versions Affected: 10 - 12.
The PostgreSQL search_path setting determines schemas searched for tables, functions, operators, etc. The CVE-2018-1058 fix caused most PostgreSQL-provided client applications to sanitize search_path, but logical replication continued to leave search_path unchanged. Users of a replication publisher or subscriber database can create objects in the public schema and harness them to execute arbitrary SQL functions under the identity running replication, often a superuser. Installations having adopted a documented secure schema usage pattern are not vulnerable.
The PostgreSQL project thanks Noah Misch for reporting this problem.
CVE-2020-14350: Uncontrolled search path element in CREATE EXTENSION.
Versions Affected: 9.5 - 12. The security team typically does not test unsupported versions, but this problem is quite old.
When a superuser runs certain CREATE EXTENSION statements, users may be able to execute arbitrary SQL functions under the identity of that superuser. The attacker must have permission to create objects in the new extension's schema or a schema of a prerequisite extension. Not all extensions are vulnerable.
In addition to correcting the extensions provided with PostgreSQL, the PostgreSQL Global Development Group is issuing guidance for third-party extension authors to secure their own work.
Bug Fixes and Improvements
This update also fixes over 50 bugs that were reported in the last several months. Some of these issues affect only version 12, but many affect all supported versions.
Some of these fixes include:
Fix edge cases in partition pruning involving multiple partition key columns with multiple or no constraining WHERE clauses.
Several fixes for query planning and execution involving partitions.
Fix for determining when to execute a column-specific UPDATE trigger on a logical replication subscriber.
pg_replication_slot_advance() now updates the oldest xmin and LSN values, as the failure to do this could prevent resources (e.g. WAL files) from being cleaned up.
Fix a performance regression in ts_headline().
Ensure that pg_read_file() and related functions read until EOF is reached, which fixes compatibility with pipes and other virtual files.
Forbid numeric NaN values in jsonpath computations, which do not exist in SQL nor JSON.
Several fixes for NaN inputs with aggregate functions. This fixes a change in PostgreSQL 12 where NaN values caused the following aggregates to emit values of 0 instead of NaN: corr(), covar_pop(), regr_intercept(), regr_r2(), regr_slope(), regr_sxx(), regr_sxy(), regr_syy(), stddev_pop(), and var_pop().
time and timetz values fractionally greater than 24:00:00 are now rejected.
Several fixes for EXPLAIN, including a fix for reporting resource usage when a plan uses parallel workers with "Gather Merge" nodes.
Fix timing of constraint revalidation in ALTER TABLE that could lead to odd errors.
Fix for REINDEX CONCURRENTLY that could prevent old values from being included in future logical decoding output.
Fix for LATERAL references that could potentially cause crashes during query execution.
Use the collation specified for a query when estimating operator costs
Fix conflict-checking anomalies in SERIALIZABLE transaction isolation mode.
Ensure checkpointer process discards file sync requests when fsync is off
Fix issue where pg_control could be written out with an inconsistent checksum, which could lead to the inability to restart the database if it crashed before the next pg_control update.
Ensure that libpq continues to try to read from the database connection socket after a write failure, as this allows the connection to collect any final error messages from the server.
Report out-of-disk-space errors properly in pg_dump and pg_basebackup
Several fixes for pg_restore, including a fix for parallel restore on tables that have both table-level and column-level privileges.
Fix for pg_upgrade to ensure it runs with vacuum_defer_cleanup_age set to 0.
Fix how pg_rewind handles just-deleted files in the source data directory
Fix failure to initialize local state correctly in contrib/dblink, which could lead to dblink_close() issuing an unexpected COMMIT on the remote server.
Change contrib/amcheck to not report about deleted index pages that are empty, as this is normal during WAL replay.
2.8:
- new feature: SafeSync strategy (SAFE_SYNC) for using a synchronous Connection object in a multi-threading program
- new feature: LDIF_LINE_LENGTH for specifying line length wrapping in ldif-content output (default to 78 as per RFC 2849)
- fixed requirements for pyasn1
- fixed regression for ldapi connections
- fixed issue with lazy connection requesting server info on every operation
- fixed searching by objectGUID in hex format (thanks Matt)
- added iso_format parameter to utils.format_json to return dates in ISO format (thanks Hugh)
- fixed issue with Referral attributes not returned by the referral server (thanks Nazarii)
- fixed lost error message in auto_bind (thanks cfelder)
- fixed delete_old_dn in mock connections (thanks kpinc)
- fixed a ResourceWarning with lazy connections
- fixed entry_to_json() that in python2 modified the original entry value (thanks Dirk-Jan)
- tests desnt' raise Exception if real server is not present
asyncpg v0.21.0
Improvements
Add support for password functions (useful for RDS IAM auth)
Add support for connection termination listeners
Update CI matrix, aarch64 builds
Fixes
Fix possible uninitalized pointer access on unexpected array
message data (CVE-2020-17446)
Fix Connection class _copy_in private method
Bump pgproto to fix compilation issues
Improve pool documentation examples
Update usage.rst
Fix links in connection documentation
Fix usage documentation for hstore
Fix compiler warnings
Update ruby-sequel to 5.35.0.
=== 5.35.0 (2020-08-01)
* Recognize another disconnect error in the oracle adapter (sterlzbd) (#1705)
* Consider all associations with :dataset options as instance-specific associations (jeremyevans)
* Make Model.finalize_associations not break with instance-specific associations (jeremyevans)
* Make association placeholder loader consider block if instance_specific: false association option is used (jeremyevans)
* Copy composite unique constraints when emulating alter table operations on SQLite (jeremyevans) (#1704)
* Add instance_specific_default plugin for setting default association :instance_specific value, or warning/raising for cases where it is not specified (jeremyevans)
* Make Model.plugin issue deprecation warning if loading plugin with arguments and block if plugin does not accept arguments/block (jeremyevans)
* Make validation_class_methods consider all :if, :allow_missing, :allow_nil, and :allow_blank settings, instead of just the first (jeremyevans)
* Include hash entries with nil keys in Dataset#to_dot output in to_dot extension (jeremyevans)
* Remove unneeded conditionals from plugins and extensions (jeremyevans)
* Fix exception class in run_transaction_hooks extension if calling run_after_{commit,rollback}_hooks outside of a transaction (jeremyevans)
=== 5.34.0 (2020-07-01)
* Make eager_graph work correctly if called with no associations (jeremyevans)
* Make :ruby eager limit strategy handle cases where there is no limit or
offset (jeremyevans)
* Do not keep a reference to a Sequel::Database instance that raises an
exception during initialization (jeremyevans)
* Make Database#pool.all_connections not yield for a single connection pool
in disconnected state (jeremyevans)
* Raise an exception if trying to disconnect a server that doesn't exist in
the sharded connection pools (jeremyevans)
* Support :refresh option when calling *_pks getter method in the
association_pks plugin (jeremyevans)
* Support caching of repeated calls to *_pks getter method in the association_pks plugin using :cache_pks association option (jeremyevans)
* Add *_pks_dataset methods for one_to_many and many_to_many associations
when using the association_pks plugin (jeremyevans)
0.36.8
- Don't connect to 'postgres' data base for database existence check
0.36.7
- Fix dynamic relationships for observables
0.36.6
- Reverted 426 and added support for Legacy Encrypted Type
- Added psycopg2cffi support for create_database and drop_database
v0.10.0
This version is the last version supporting Python 2.7.
* MariaDB ed25519 auth is supported.
* Python 3.4 support is dropped.
* Context manager interface is removed from `Connection`. It will be added
with different meaning.
* MySQL warnings are not shown by default because many user report issue to
PyMySQL issue tracker when they see warning. You need to call "SHOW WARNINGS"
explicitly when you want to see warnings.
* Formatting of float object is changed from "3.14" to "3.14e0".
* Use cp1252 codec for latin1 charset.
* Fix decimal literal.
* TRUNCATED_WRONG_VALUE_FOR_FIELD, and ILLEGAL_VALUE_FOR_TYPE are now
DataError instead of InternalError.
Changes in MySQL 5.7.31
Configuration Notes
tcmalloc is no longer a permitted value for the mysqld_safe --malloc-lib option.
Packaging Notes
The libevent library bundled with MySQL was upgraded to version 2.1.11. In addition, for the WITH_LIBEVENT CMake option, the following two changes were made:
yes is no longer permitted as a synonym for system. Use system instead.
If system is specified but no system libevent is found, the bundled version is no longer used in place of the missing system library, and an error occurs instead.
Security Notes
Incompatible Change: Access to the INFORMATION_SCHEMA.FILES table now requires the PROCESS privilege.
This change affects users of the mysqldump command, which accesses tablespace information in the FILES table, and thus now requires the PROCESS privilege as well. Users who do not need to dump tablespace information can work around this requirement by invoking mysqldump with the --no-tablespaces option.
The linked OpenSSL library for MySQL Server has been updated to version 1.1.1g. Issues fixed in the new OpenSSL version are described at https://www.openssl.org/news/cl111.txt and https://www.openssl.org/news/vulnerabilities.html.
Bugs Fixed
InnoDB: The INNODB_METRICS table AVG_COUNT_RESET value for a counter defined as a module owner reported NULL. The METRIC_AVG_VALUE_RESET field was incorrectly marked as NULL.
InnoDB: Purge thread activity was excessive when the history list length approached zero, wasting CPU resource and causing mutex contention.
InnoDB: The server failed intermittently with an “ibuf cursor restoration fails” error.
InnoDB: A fatal “page still fixed or dirty” error occurred during shutdown.
Partitioning: A query against a partitioned table, which used an ORDER BY, returned unordered results under the following conditions:
The table had a composite index with a prefix on one of the columns.
The query's WHERE clause contained an equality condition on the prefixed column.
The column with the prefix was the leftmost column in the index.
The column used in the ORDER BY was the rightmost column in the index.
The index was used for handling the ORDER BY.
Our thanks to Quanan Han for the contribution.
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 notifies replicas that the table must be emptied by writing a DELETE statement for that table to the binary log. Previously, the generated DELETE statement was written to the binary log statement cache for the current session, which could result in it being logged together with other statements under the same GTID, or logged without BEGIN and COMMIT statements. Also, in some situations, the generated DELETE statement could consume the GTID intended for the transaction that triggered it. The generated DELETE statement is now logged with accompanying BEGIN and COMMIT statements, and the resulting transaction is flushed to the binary log immediately after it is written to the statement cache, so that it always receives its own GTID and is kept separate from other transactions.
Replication: Internal queries from Group Replication to the Performance Schema for statistics on local group members failed if they occurred simultaneously with changes to the group's membership. Locking for the internal queries has been improved to fix the issue.
Replication: A fix made in MySQL 8.0.14 and MySQL 5.7.25 for a deadlock scenario involving the system variables binlog_transaction_dependency_tracking and binlog_transaction_dependency_history_size had the side effect of leaving the writeset history used for transaction dependency tracking unprotected from concurrent update. The writeset history and tracking mode are now locked correctly whenever they are accessed.
Configuring with -DWITH_EDITLINE=system resulted in compilation failures for older library versions.
The upgrade of the bundled libedit library in the previous MySQL distribution caused a problem for builds using that library such that CTRL+C (SIGINT) in the mysql client required a following Enter to take effect in some circumstances.
Assigning CONCAT('') or CONCAT_WS('') to a variable set the variable to NULL, not the empty string.
The gen_range() user-defined function could mishandle its arguments, causing a server exit.
During UPDATE processing, conversion of an internal in-memory table to InnoDB could result in a key-length error.
It is possible to define a column named * (single asterisk character), but SELECT `*` was treated identically to SELECT *, making it impossible to select only this column in a query; in other words, the asterisk character was expanded to a list of all table columns even when it was surrounded by backticks.
An internal packet-length function returned values of the wrong integer type.
Calculations by mysqldump for the length of INSERT statements did not take into account the _binary character set introducer used for VARBINARY strings.
mysql_store_result() could fail to detect invalid data packets.
In a multiple-table UPDATE that updated the key of the first table, if a temporary table strategy was used, duplicate entries could be written to the temporary table, followed by occurrence of a Can't find record error.
The optimizer could attempt to access a pseudo table as a table, resulting in unexpected server behavior.
The server sometimes mistakenly removed a subquery with a GROUP BY when optimizing a query, even in some cases when this subquery was used by an outer select. This could occur when the subquery also used an aggregate function.
Coercibility of the NAME_CONST() function was assessed incorrectly.
Incorrect results could occur when the optimizer chose an index on a generated column to fetch values.
Changes in MySQL 5.6.49
Configuration Notes
tcmalloc is no longer a permitted value for the mysqld_safe --malloc-lib option.
Security Notes
Incompatible Change: Access to the INFORMATION_SCHEMA.FILES table now requires the PROCESS privilege.
This change affects users of the mysqldump command, which accesses tablespace information in the FILES table, and thus now requires the PROCESS privilege as well. Users who do not need to dump tablespace information can work around this requirement by invoking mysqldump with the --no-tablespaces option.
The linked OpenSSL library for MySQL Server has been updated to version 1.1.1g. Issues fixed in the new OpenSSL version are described at https://www.openssl.org/news/cl111.txt and https://www.openssl.org/news/vulnerabilities.html.
Bugs Fixed
Partitioning: A query against a partitioned table, which used an ORDER BY, returned unordered results under the following conditions:
The table had a composite index with a prefix on one of the columns.
The query's WHERE clause contained an equality condition on the prefixed column.
The column with the prefix was the leftmost column in the index.
The column used in the ORDER BY was the rightmost column in the index.
The index was used for handling the ORDER BY.
Our thanks to Quanan Han for the contribution.
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 notifies replicas that the table must be emptied by writing a DELETE statement for that table to the binary log. Previously, the generated DELETE statement was written to the binary log statement cache for the current session, which could result in it being logged together with other statements under the same GTID, or logged without BEGIN and COMMIT statements. Also, in some situations, the generated DELETE statement could consume the GTID intended for the transaction that triggered it. The generated DELETE statement is now logged with accompanying BEGIN and COMMIT statements, and the resulting transaction is flushed to the binary log immediately after it is written to the statement cache, so that it always receives its own GTID and is kept separate from other transactions.
mysql_store_result() could fail to detect invalid data packets.
The server sometimes mistakenly removed a subquery with a GROUP BY when optimizing a query, even in some cases when this subquery was used by an outer select. This could occur when the subquery also used an aggregate function.
2.20.0 / 2020-07-22
This release changes WAL compression from opt-in to default. WAL compression will prevent a downgrade to v2.10 or earlier without deleting the WAL. Disable WAL compression explicitly by setting the command line flag --no-storage.tsdb.wal-compression if you require downgrading to v2.10 or earlier.
[CHANGE] promtool: Changed rule numbering from 0-based to 1-based when reporting rule errors.
[CHANGE] Remote read: Added prometheus_remote_storage_read_queries_total counter and prometheus_remote_storage_read_request_duration_seconds histogram, removed prometheus_remote_storage_remote_read_queries_total counter.
[CHANGE] Remote write: Added buckets for longer durations to prometheus_remote_storage_sent_batch_duration_seconds histogram.
[CHANGE] TSDB: WAL compression is enabled by default.
[FEATURE] PromQL: Added group() aggregator.
[FEATURE] SD: Added Docker Swarm SD.
[FEATURE] SD: Added DigitalOcean SD.
[FEATURE] SD: Added Openstack config option to query alternative endpoints.
[ENHANCEMENT] Configuration: Exit early on invalid config file and signal it with exit code 2.
[ENHANCEMENT] PromQL: without is now a valid metric identifier.
[ENHANCEMENT] PromQL: Optimized regex label matching for literals within the pattern or as prefix/suffix.
[ENHANCEMENT] promtool: Added time range parameters for labels API in promtool.
[ENHANCEMENT] Remote write: Include samples waiting in channel in pending samples metric. Log number of dropped samples on hard shutdown.
[ENHANCEMENT] Scrape: Ingest synthetic scrape report metrics atomically with the corresponding scraped metrics.
[ENHANCEMENT] SD: Reduce timeouts for Openstack SD.
[ENHANCEMENT] SD: Use 10m timeout for Consul watches.
[ENHANCEMENT] SD: Added AMI meta label for EC2 SD.
[ENHANCEMENT] TSDB: Increment WAL corruption metric also on WAL corruption during checkpointing.
[ENHANCEMENT] TSDB: Improved query performance for high-cardinality labels.
[ENHANCEMENT] UI: Display dates as well as timestamps in status page.
[ENHANCEMENT] UI: Improved scrolling when following hash-fragment links.
[ENHANCEMENT] UI: React UI renders numbers in alerts in a more human-readable way.
[BUGFIX] API: Fixed error status code in the query API.
[BUGFIX] PromQL: Fixed avg and avg_over_time for NaN, Inf, and float64 overflows.
[BUGFIX] PromQL: Fixed off-by-one error in histogram_quantile.
[BUGFIX] promtool: Support extended durations in rules unit tests.
[BUGFIX] Scrape: Fix undercounting for scrape_samples_post_metric_relabeling in case of errors.
[BUGFIX] TSDB: Don't panic on WAL corruptions.
[BUGFIX] TSDB: Avoid leaving behind empty files in chunks_head, causing startup failures.
[BUGFIX] TSDB: Fixed race between compact (gc, populate) and head append causing unknown symbol error.
[BUGFIX] TSDB: Fixed unknown symbol error during head compaction.
[BUGFIX] TSDB: Fixed panic during TSDB metric registration.
[BUGFIX] TSDB: Fixed --limit command line flag in tsdb tool
0.16.14
Make F expression work with QuerySet.filter().
Include py.typed in source distribution.
Added datetime parsing from int for fields.DatetimeField.
get_or_create passes the using_db= on if provided.
Allow custom loop and connection_class parameters to be passed on to asyncpg.
Upstream changes:
1.02 - Todd Rinaldo <toddr@cpan.org> 2020-01-29
- Invoke new as a class method in docs and practice.
- Add support for COW PVs when returning key values. This will hopefully
deduplicate returned strings where possible.
- Adjust tests to skip exists tests on 5.8.1, not 5.6.2
- Optimize cdb_hashadd as a inline macro
- Croak if atomic re-write from the temp to the final file fails.
1.01 - Todd Rinaldo <toddr@cpan.org> 2020-01-27
- Fix MANIFEST so Changelog is shpped.
- Address file descriptor leak in CDB_File.
1.00 - Todd Rinaldo <toddr@cpan.org> 2020-01-19
- Enable github actions for automated testing
- Switch to github issues.
Redis 6.0.6
===========
Upgrade urgency MODERATE: several bugs with moderate impact are fixed here.
The most important issues are listed here:
* Fix crash when enabling CLIENT TRACKING with prefix
* EXEC always fails with EXECABORT and multi-state is cleared
* RESTORE ABSTTL won't store expired keys into the db
* redis-cli better handling of non-pritable key names
* TLS: Ignore client cert when tls-auth-clients off
* Tracking: fix invalidation message on flush
* Notify systemd on Sentinel startup
* Fix crash on a misuse of STRALGO
* Few fixes in module API
* Fix a few rare leaks (STRALGO error misuse, Sentinel)
* Fix a possible invalid access in defrag of scripts (unlikely to cause real harm)
New features:
* LPOS command to search in a list
* Use user+pass for MIGRATE in redis-cli and redis-benchmark in cluster mode
* redis-cli support TLS for --pipe, --rdb and --replica options
* TLS: Session caching configuration support
v3.12.0
All Enhancements
Make use of the enhanced ALTER TABLE features in SQLite 3.25.0
Allow specifying an ON CONFLICT strategy in the Import CSV dialog
Add option to remember last location per action type when saving and loading
Add conditional formats to the Browse Data tab
Show current database action and add a cancel button in status bar
Save read-only state in the project file
Add support for filtering by regular expressions using the /regexp/ syntax
More efficient table editing. When editing the schema, do all changes in one go at the end
Add comment/uncomment feature to the SQL editor
Add option to find and replace in the selection in the SQL editor
Execute SQL statements in a different thread, allowing long-running queries to be cancelled
When editing a cell with a foreign-key, show a list of possible values in a dropdown list
Many small performance improvements
Lots of UI reworking, allowing more flexibility, adding new shortcuts, fixing glitches, and making it more responsive. Some of the new settings are stored in the project file while the handling of project files itself is improved too
New Save Project As menu item
Ask the user whether to save modified SQL tabs when closing, add a new button to save changes in all open tabs, prompt to save changes in the project when closing the database or the application
Allow custom display formats
Add new log to the SQL log dock which prints the SQLite error log
New setting allowing to set a dark style using a style-sheet
Add support for sorting by multiple columns in the Browse Data tab and add a button to clear sort orders
Add support for inserting rows into views with appropriate triggers
Enable build against external QCustomPlot
Improved text editor in the Edit Cell dock
New command-line argument for saving settings
Show some information about the selected data when selecting cells in the Browse Data tab
Detect changes in SQL files made by other programs
Add a full find dialog to all text editors
Add constraint editing to the Edit Table dialog
Include a built-in certificate which allows out-of-the-box read-only access to dbhub.io
Support all Unicode quote and escape characters in the Import CSV dialog
Add proxy support to dbhub.io functionality
Add "Browse Table" action to the context menu of the DB Structure dock
Remember read-only flag for recent files list
Extended regular expression support in the find dialogs
Add duplicate tab feature to Execute SQL area
Prompt user for options after dropping files
Allow changing the collation of columns in the Edit Table dialog
Add global filter field to Browse Data tab
Support inline preview of image data in cells
Add move field to top/bottom buttons to Edit Table dialog
Add a find and replace toolbars to the Browse Data tab
Add a toolbar for direct formatting of columns, rows, and single cells in the Browse Data tab
Support custom SQLCipher cipher_plaintext_header_size
Add support for parsing, browsing, and editing tables with GENERATED ALWAYS AS columns
Use the column type affinity for the default text alignment in the Browse Data tab
Resize columns according to contents
Allow opening of URLs or filenames from database cells and add a button to insert a link to the file into the cell
Allow editing of the contents of database cells in external applications
Add support for a secondary Y-axis to the plot area
Drop close buttons on every Execute SQL tab(x)
Show a useful icon in SQL tabs
Open SQL tabs for modifying views and triggers
Fix logo issues
Install the AppStream file to the canonical location
Open a set of SQL-Files
Consistent naming of DB Browser for SQLite
Minor: Change "Filter in all columns" => "Filter in any column"
Avoid unchanged translation of keyboard shortcuts to work around problems
Rearrange preferences database
Use port 443 for DBHub.io traffic, to be more enterprise firewall friendly
Application icon cleanup
Update to Windows Icon Generation script
All Bug fixes
Avoid setting the database dirty with some trailing whitespace and comments
Use native and localised names for shortcuts in the tool-tips
Add macOS .dylib extension to the extension selector dialog
Do not show more than 512 characters in DB Structure tooltips
Load all pending data when select all is requested
Make the Edit Cell Dock to update with the selected cell in SQL results
Fix selecting columns in Browse Data tab instead of sorting them
Fix detection of XML data, some types of text data, and large numbers in the Edit Cell dock
Fix default collations and callbacks when creating a new database
Lots of bug fixes in the SQL parser
Always set sort direction to ascending when sorting a different column
Fix problems with the JSON export
Fix problems after closing a database
Fix syntax highlighting to exactly match the SQLite keywords
Fix deleting from WITHOUT ROWID table
Fix editing data in WITHOUT ROWID tables with multiple primary key columns
Silence some unnecessary warning messages
Fix licence list in dbhub.io push dialog
Fix loading last used settings in the Import CSV dialog
Fix setting last modified date when cloning a dbhub.io database
Fix possible crash when loading a corrupt project file
Include transaction statements in the SQL log
Fixes for editing cells with RTL texts
When updating a field try to respect the affinity data type if possible
Fix value in size column of dbhub.io panel for very large databases
Fix plotting data with NULL values by leaving gaps in the graph
Fix importing CSV files with quote characters and no final line break and with only one column and no final line break
Escape filepath when attaching database
Fix foreign-key editor not working correctly in Edit Table dialog
Fix issues with resizing and with hiding a column
Fix editing in tables with custom display formats
Fix problems with greediness in the DB4S implementation of the SQLite REGEXP operator
Check if some column has a NOT NULL constraint in "Set to NULL"
Fix error indication and savepoint handling after failed statements
Make SQL editor in Edit Table dialog read-only
Fix some problems with view editing in Browse Data tab
Fix handling of databases with a view and a trigger with the same name
Never mark the DB dirty if it is read-only
Fix the recordset numbers in the Browse Data tab
Fix some typos and translation problems
Fix dotenv not working for databases encrypted using SQLCipher 3
Fix dotenv not working when not specifying the plaintext header size
Crash when -t option specifies missing table
Translations
Add Japanese translation
Update Russian translation
Update Chinese translation
Update Polish translation
Update Portuguese translation
Update French translation
Update Spanish translation
Update Turkish translation
Update Italian translation
Update German translation
Update Arabic translation
Update Simplified Chinese translation
Update German translation for v3.12.x
Updates the Brazilian Portuguese files for 3.12.0
Portuguese updates for 3.12
Update Japanese Translation for v3.12.x
Update zh translation
v0.15.0
Feature release
- Support for accessing connections from multiple event loops
- Fixed type annotations for connection methods returning cursors
- Move cursors into separate module from connections
- Deprecated `loop` parameter to `connect()` and `Connection`
v0.14.0
- `Connection.backup()` now supported
- PEP 561 support added to mark the package as type annotated
- Better/fixed type annotations for context managers
LuaDBI is a database interface library for Lua. It is designed to provide
a RDBMS agnostic API for handling database operations. LuaDBI also provides
support for prepared statement handles, placeholders and bind parameters
for all database operations.
Currently LuaDBI supports DB2, Oracle, MySQL, PostgreSQL and SQLite databases
with native database drivers.
lsqlite3 is a thin wrapper around the public domain SQLite3 database engine.
The lsqlite3 module supports the creation and manipulation of SQLite3
databases.
After a require('lsqlite3') the exported functions are called with prefix
sqlite3. However, most sqlite3 functions are called via an object-oriented
interface to either database or SQL statement objects.
1.3.18
orm
[orm] [usecase]
Improve error message when using Query.filter_by() in a query where the first entity is not a mapped class.
[orm] [usecase]
Added a new parameter query_expression.default_expr to the query_expression() construct, which will be appled to queries automatically if the with_expression() option is not used. Pull request courtesy Haoyu Sun.
engine
[engine] [bug]
Further refinements to the fixes to the “reset” agent fixed in 5326, which now emits a warning when it is not being correctly invoked and corrects for the behavior. Additional scenarios have been identified and fixed where this warning was being emitted.
[engine] [bug]
Fixed issue in URL object where stringifying the object would not URL encode special characters, preventing the URL from being re-consumable as a real URL. Pull request courtesy Miguel Grinberg.
sql
[sql] [usecase]
Added a “.schema” parameter to the table() construct, allowing ad-hoc table expressions to also include a schema name. Pull request courtesy Dylan Modesitt.
[sql] [bug]
Correctly apply self_group in type_coerce element.
The type coerce element did not correctly apply grouping rules when using in an expression
[sql] [bug]
Added Select.with_hint() output to the generic SQL string that is produced when calling str() on a statement. Previously, this clause would be omitted under the assumption that it was dialect specific. The hint text is presented within brackets to indicate the rendering of such hints varies among backends.
[sql] [schema]
Introduce IdentityOptions to store common parameters for sequences and identity columns.
[sql] [change] [sybase]
Added .offset support to sybase dialect. Pull request courtesy Alan D. Snow.
schema
[schema] [bug]
Fixed issue where dialect_options were omitted when a database object (e.g., Table) was copied using tometadata().
mysql
[mysql] [usecase]
Implemented row-level locking support for mysql. Pull request courtesy Quentin Somerville.
sqlite
[sqlite] [usecase]
SQLite 3.31 added support for computed column. This change enables their support in SQLAlchemy when targeting SQLite.
[sqlite] [bug]
Added “exists” to the list of reserved words for SQLite so that this word will be quoted when used as a label or column name. Pull request courtesy Thodoris Sotiropoulos.
mssql
[mssql] [bug]
Refined the logic used by the SQL Server dialect to interpret multi-part schema names that contain many dots, to not actually lose any dots if the name does not have bracking or quoting used, and additionally to support a “dbname” token that has many parts including that it may have multiple, independently-bracketed sections.
[mssql] [bug] [pyodbc]
Fixed an issue in the pyodbc connector such that a warning about pyodbc “drivername” would be emitted when using a totally empty URL. Empty URLs are normal when producing a non-connected dialect object or when using the “creator” argument to create_engine(). The warning now only emits if the driver name is missing but other parameters are still present.
[mssql] [bug]
Fixed issue with assembling the ODBC connection string for the pyodbc DBAPI. Tokens containing semicolons and/or braces “{}” were not being correctly escaped, causing the ODBC driver to misinterpret the connection string attributes.
[mssql] [bug]
Fixed issue where datetime.time parameters were being converted to datetime.datetime, making them incompatible with comparisons like >= against an actual TIME column.
[mssql] [bug]
Fixed an issue where the is_disconnect function in the SQL Server pyodbc dialect was incorrectly reporting the disconnect state when the exception messsage had a substring that matched a SQL Server ODBC error code.
[mssql] [change]
Moved the supports_sane_rowcount_returning = False requirement from the PyODBCConnector level to the MSDialect_pyodbc since pyodbc does work properly in some circumstances.
oracle
[oracle] [bug] [reflection]
Fixed bug in Oracle dialect where indexes that contain the full set of primary key columns would be mistaken as the primary key index itself, which is omitted, even if there were multiples. The check has been refined to compare the name of the primary key constraint against the index name itself, rather than trying to guess based on the columns present in the index.
misc
[change] [examples]
Added new option --raw to the examples.performance suite which will dump the raw profile test for consumption by any number of profiling visualizer tools. Removed the “runsnake” option as runsnake is very hard to build at this point;
Changes in MySQL 5.6.48
Bugs Fixed
InnoDB: A tablespace import operation that failed due to the source and destination tables being defined with different DATA DIRECTORY clauses reported an insufficiently descriptive schema mismatch error. Moreover, if a .cfg file was not present, the same operation would raise an assertion failure. A more informative error message is now reported in both cases before the import operation is terminated due to the data directory mismatch.
InnoDB: Updating certain InnoDB system variables that take string values raised invalid read errors during Valgrind testing.
Replication: In the event of an unplanned disconnection of a replication slave from the master, the reference to the master's dump thread might not be removed from the list of registered slaves, in which case statements that accessed the list of slaves would fail. The issue has now been fixed.
Replication: With the settings binlog_format=MIXED, tx_isolation=READ-COMMITTED, and binlog_row_image=FULL, an INSERT ... SELECT query involving a transactional storage engine omitted any columns with a null value from the row image written to the binary log. This happened because when processing INSERT ... SELECT statements, the columns were marked for inserts before the binary logging format was selected. The issue has now been fixed.
The Event Scheduler had a memory leak.
Under certain circumstances, a memcached command could result in reading an uninitialized memory buffer, causing a failure.
CONCAT() and CONCAT_WS() could produce incorrect results in rare cases due to incorrect substring handling.
Scheduling of events could be disturbed by removing events.
Client programs could load authentication plugins from outside the plugin library.
A query with a WHERE clause whose predicate contained a numeric value in scientific notation was not handled correctly.
In addition, attempting to insert a particular integer specified as a string caused a server exit when the string-to-integer conversion was not successful.
The client library could dereference a null pointer while fetching result set metadata from the server.
Changes 3.3.1:
* On MacOS, remove option to make LDAP connections from a file descriptor
when built wit the system libldap (which lacks the underlying function,
``ldap_init_fd``)
- Fixed Perl Pod errors, thanks to a pull request from Mohammad S Anwar
(#470).
- Fixed test failures when running with the localization set to German
or Italian. Thanks to Slaven Rezić for the report (#472).
- Fixed an issue when the full name of the current user is not set, so
that it properly falls back on the username. Thanks to Slaven Rezić and
Matthieu Foucault for the report and testing various fixes (#473).
- Eliminated an error when using the `-t` option to specify a target, due
to a missing dependency declaration in the Target class. Thanks to
Clinton Adams for the fix (#509)!
- Updated the IPC::System::Simple Win32 workaround added in 0.9999 to
properly support released versions of IPC::System::Simple. This fixes
errors running the database command-line clients on Windows (#503).
- Sqitch now only passes the `--password` option to the MySQL client if
it was not read from the `.my.cnf` file, as it's more secure to let
the client use `.my.cnf`, and it eliminates a warning from recent
versions of the client. Thanks to Kiel R Stirling for the fix (#484)!
- Added a note to the tutorials to skip setting the `engine.$engine.client`
config when using the Docker image.
- Added the new `check` command, which compares the SHA1 hashes of the
deploy scripts to the database, and reports if any have been modified
since they were deployed. Thanks to Matthieu Foucault for the pull
request and diligent work on this feature (#477)!
- Added the `--modified` option to the `rebase` and `revert` commands, to
revert to the earliest change with a modified deploy script. Handy for
rapid rebasing during iterative development cycles. Thanks to Matthieu
Foucault for this feature (#477)!
- Fixed an issue where the Snowflake engine would complain about not
finding the account name even for commands that don't need them, such
as `init`. Thanks to Stack Overflow user vbp13 for the report (#502).
Berkeley DB is an embeddable database system that supports keyed access to
data. The software is distributed in source code form, and developers can
compile and link the source code into a single library for inclusion
directly in their applications.
Developers may choose to store data in any of several different storage
structures to satisfy the requirements of a particular application. In
database terminology, these storage structures and the code that operates on
them are called access methods. The library includes support for the
following access methods:
* B+tree: Stores keys in sorted order, using either a programmer-supplied
ordering function or a default function that does lexicographical
ordering of keys. Applications may perform equality or range searches.
* Hashing: Stores records in a hash table for fast searches based on
strict equality. Extended Linear Hashing modifies the hash function
used by the table as new records are inserted, in order to keep buckets
underfull in the steady state.
* Fixed and Variable-Length Records: Stores fixed- or variable-length
records in sequential order. Record numbers may be immutable or
mutable, i.e., permitting new records to be inserted between existing
records or requiring that new records be added only at the end of the
database.
This package privides Berkeley DB 18 released under GNU AGPL3.
* Suggested by Jesus Cea.
* Remove patch for FreeBSD 10 or later.
Changelog:
Changes between version 12.1.6.2.23 and version 12.1.6.2.32
Modified the ex_rep_base example to accept IPv6 addresses.
[#24371]
Fixed a bug where SQL authentication APIs might raise assertion
failures. [#24598]
The SQLite user authentication extension now always requires
encryption. To build with the authentication extension, encryption
must be enabled. Otherwise, it results in a compiler error. To
convert a database to require authentication, the database must
be encrypted. sqlite3_user_authenticate() now always returns
SQLITE_AUTH if called on a database that does not require
authentication. [#24598]
Fixed a bug where an application might hang because it could
not obtain a TAS lock when running Linux on Sparc architecture.
[#24805]
Added tests memp009 and mut004. [#24974]
When the number of free mutexes is low, removed databases and
closed unnamed in-memory databases are purged from the memory
pool to free mutexes. [#24974]
Fixed a bug where built-in atomic functions are used only when
--enable-cxx is specified. [#24974]
Fixed a possible crash when using the Java API and slices.
[#24988]
Added cross-compile support for detecting built-in atomic
functions. [#25055]
Fixed undefined symbol errors for configurations including
--enable-dtrace and -enable-perfmon_statistics when replication
is also enabled. [#25061]
Added the db_convert utility program which converts the byte
order of all databases in database files. [#25086]
Increased the number of instances in which failchk can successfully
clean the environment without requiring full recovery after a
thread crashes while using Berkeley DB. [#25087]
Added DPL APIs to BDB Java client driver. [#25089]
Attempting to open an environment while it is being recovered
now returns a new error message, which includes the time.
[#25204]
Improved db_verify's handling of corrupted database files.
[#25239]
Adjusted configure scripts to handle FreeBSD 10 or greater.
[#25251]
Fixed a bug where setting the absolute path of a file on Windows
could result in the file being created on the wrong disk.
[#25284]
Syncing a database with external files will now also sync the
meta database associated with the external files. [#25284]
Add support for -with-mutex=BSD/OSSpinLockTry, to avoid using
the undocumented spin_lock_try function, which is not permitted
on iOS. [#25342]
Fixed a bug preventing some changes to external files performed
through the DB_STREAM API from replicating to the clients.
[#25432]
Fixed a bug where automatic log removal did not work on Windows
Mobile 6.5. [#25449]
Fixed bugs where printed statistics might contain "unknown"
flags. [#25461]
Fixed a bug where hot backup of queue extent files did not
follow the original directory structure. [#25545]
Fixed a bug where ADO .Net package had debug pre-processors
for release configurations. [#25549]
Added PRAGMA statistics, which prints out statistics about the
database and its environment. [#25550]
Added PRAGMA statistics_files, which redirects output from the
statistics PRAGMA to a file. [#25550]
Internal Berkeley DB messages are now redirected to the same
file where internal Berkeley DB error messages are redirected.
[#25568]
Fixed a bug that could cause a client undergoing internal
initialization to fail to request all the necessary logs for
a correct recovery. The major symptom of this bug was that some
client database files were left with empty pages that would
later cause log sequence errors or other failures. [#25624]
Added a new field in the per-thread statistics output: the
number of locked mutexes. [#25690]
The -c option of db_hotbackup can now work with replication
manager applications. The -c option cannot be used with base
replication applications. [#25702]
Fixed a bug where the configure script may fail to find the
JNI include directories on Mac OS X. [#25713]
Fixed a bug where mutexes could not be acquired on arm64-v8a
Android systems. [#25752]
Fixed a bug where the JAVACFLAGS environment variable was not
passed to the JDBC driver. [#25752]
Fixed a bug where clients in the replication group might panic
during synchronization with the master. [#25800]
Fixed possible segfaults when running db_verify with external
files. [#25920]
Added Visual Studio 2015 solution files to the SQL ADO.NET
package. [#25946]
Fixed a bug where setting initial number of lockers might cause
segfault. [#26085]
Fixed a bug where client specific log records resulted in
incorrect calculation of subsequent log offset. This would
later result in a DB panic on master. [#26090]
Instead:
1. Package makefiles including their own options.mk
2. Packages say "SUBST_CLASSES+=djberrno" to get the hack, if needed
3. Packages adjust SUBST_FILES.djberrno, if needed
Should fix bulk build failures due to multiple inclusions of options.mk
and/or incorrect definitions of DJB_ERRNO_HACK.
Approved during the freeze by wiz@.
Changelog picked from https://notabug.org/guile-sqlite3/guile-sqlite3/releases
0.1.2:
Allow sqlite-finalize to be called twice on the same statement.
0.1.1:
sqlite-finalize: Reset statement when called on cached statement.
Fix memory management of retrieved blob values.
Packaging changes: depend on protobuf-c and json-c
PostGIS 3.0.1
2020/02/20
* Breaking Changes *
- #4637 svn number replaced by git hash in version output
(Sandro Santilli, Regina Obe, Bas Couwenberg)
* New Features *
- #4617, Add configure switch `--without-phony-revision` (Raúl Marín)
Use to prevent postgis_revision.h from rebuilding
(when building from tar ball) and building in a gitted folder.
* Bug Fixes and Enhancements *
[many, see NEWS]
PostGIS 3.0.0
2019/10/20
This version requires PostgreSQL 9.5+-12 and GEOS >= 3.6+
Additional features enabled if you are running Proj6+, PostgreSQL 12
and GEOS 3.8.0
* Breaking Changes *
- #4267, Bump minimum GEOS version to 3.6 (Regina Obe, Darafei Praliaskouski)
- #3888, Raster support now available as a separate extension
(Sandro Santilli)
- #3807, Extension library files no longer include the minor version.
Use New configure switch --with-library-minor-version
if you need the old behavior (Regina Obe)
- #4230, ND box operators (overlaps, contains, within, equals) now
don't look on dimensions that aren't present in both operands.
Please REINDEX your ND indexes after upgrade. (Darafei Praliaskouski)
- #4229, Dropped support for PostgreSQL < 9.5. (Darafei Praliaskouski)
- #4260, liblwgeom headers are not installed anymore.
If your project depends on them available, please use
librttopo instead. (Darafei Praliaskouski)
- #4258, Remove SFCGAL support for ST_Area, ST_Distance, ST_Intersection,
ST_Difference, ST_Union, ST_Intersects, ST_3DIntersects, ST_3DDistance
and postgis.backend switch (Darafei Praliaskouski)
- #4267, Enable Proj 6 deprecated APIs (Darafei Praliaskouski, Raúl Marín)
- #4268, Bump minimum SFCGAL version to 1.3.1 (Darafei Praliaskouski)
- #4331, ST_3DMakeBox now returns error instead of a miniscule box (Regina Obe)
- #4342, Removed "versioned" variants of ST_AsGeoJSON and ST_AsKML (Paul Ramsey)
- #4356, ST_Accum removed. Use array_agg instead. (Darafei Praliaskouski)
- #4414, Include version number in address_standardizer lib (Raúl Marín)
- #4334, Fix upgrade issues related to renamed function parameters (Raúl Marín)
- #4442, raster2pgsql now skips NODATA tiles. Use -k option if you still want
them in database for some reason. (Darafei Praliaskouski)
- #4433, 32-bit hash fix (requires reindexing hash(geometry) indexes) (Raúl Marín)
- #3383, Sorting now uses Hilbert curve and Postgres Abbreviated Compare.
You need to REINDEX your btree indexes if you had them.
(Darafei Praliaskouski)
* New Features *
- #2902, postgis_geos_noop (Sandro Santilli)
- #4128, ST_AsMVT support for Feature ID (Stepan Kuzmin)
- #4230, SP-GiST and GiST support for ND box operators overlaps, contains,
within, equals (Esteban Zimányi and Arthur Lesuisse from Université
Libre de Bruxelles (ULB), Darafei Praliaskouski)
- #4171, ST_3DLineInterpolatePoint (Julien Cabieces, Vincent Mora)
- #4311, Introduce WAGYU to validate MVT polygons. This option requires a C++11
compiler and will use CXXFLAGS (not CFLAGS). Add `--without-wagyu`
to disable this option and keep the behaviour from 2.5 (Raúl Marín)
- #1833, ST_AsGeoJSON(row) generates full GeoJSON Features (Joe Conway)
- #3687, Casts json(geometry) and jsonb(geometry) for implicit GeoJSON
generation (Paul Ramsey)
- #4198, Add ST_ConstrainedDelaunayTriangles SFCGAL function (Darafei
Praliaskouski)
* Enhancements *
- #4322, Support for Proj 6+ API, bringing more accurate datum transforms
and support for WKT projections
[many more; see NEWS]
Release 3.3.0:
Highlights:
* ``LDAPError`` now contains additional fields, such as ctrls, result, msgid
* ``passwd_s`` can now extract the newly generated password
* LDAP connections can now be made from a file descriptor
This release is tested on Python 3.8, and the beta of Python 3.9.
The following undocumented functions are deprecated and scheduled for removal:
- ``ldap.cidict.strlist_intersection``
- ``ldap.cidict.strlist_minus``
- ``ldap.cidict.strlist_union``
Modules/
* Ensure ReconnectLDAPObject is not left in an inconsistent state after
a reconnection timeout
* Syncrepl now correctly parses SyncInfoMessage when the message is a syncIdSet
* Release GIL around global get/set option call
* Do not leak serverctrls in result functions
* Don't overallocate memory in attrs_from_List()
* Fix thread support check for Python 3
* With OpenLDAP 2.4.48, use the new header openldap.h
Lib/
* Fix some edge cases regarding quoting in the schema tokenizer
* Fix escaping a single space in ldap.escape_dn_chars
* Fix string formatting in ldap.compare_ext_s
* Prefer iterating dict instead of calling dict.keys()
Doc/
* Clarify the relationship between initialize() and LDAPObject()
* Improve documentation of TLS options
* Update FAQ to include Samba AD-DC error message
"Operation unavailable without authentication"
* Fix several incorrect examples and demos
(but note that these are not yet tested)
* Update Debian installation instructions for Debian Buster
* Typo fixes in docs and docstrings
Test/
* Test and document error cases in ldap.compare_s
* Test if reconnection is done after connection loss
* Make test certificates valid for the far future
* Use slapd -Tt instead of slaptest
Infrastructure:
* Mark the LICENCE file as a license for setuptools
* Use "unittest discover" rather than "setup.py test" to run tests
