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).
