Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
PyPika is a Python API for building SQL queries. The motivation behind PyPika
is to provide a simple interface for building SQL queries without limiting the
flexibility of handwritten SQL. Designed with data analysis in mind, PyPika
leverages the builder design pattern to construct queries to avoid messy string
formatting and concatenation. It is also easily extended to take full advantage
of specific features of SQL database vendors.
|
|
|
|
|
|
|
|
Tortoise ORM is an easy-to-use asyncio ORM (Object Relational Mapper) inspired
by Django.
Tortoise ORM was build with relations in mind and admiration for the excellent
and popular Django ORM. It's engraved in it's design that you are working not
with just tables, you work with relational data.
|
|
AsyncIO bridge to the standard sqlite3 module for Python 3.5+.
|
|
SQLite Release 3.32.0:
Added support for approximate ANALYZE using the PRAGMA analysis_limit command.
Added the bytecode virtual table.
Add the checksum VFS shim to the set of run-time loadable extensions included in the source tree.
Added the iif() SQL function.
INSERT and UPDATE statements now always apply column affinity before computing CHECK constraints. This bug fix could, in theory, cause problems for legacy databases with unorthodox CHECK constraints the require the input type for an INSERT is different from the declared column type. See ticket 86ba67afafded936 for more information.
Added the sqlite3_create_filename(), sqlite3_free_filename(), and sqlite3_database_file_object() interfaces to better support of VFS shim implementations.
Increase the default upper bound on the number of parameters from 999 to 32766.
Added code for the UINT collating sequence as an optional loadable extension.
Enhancements to the CLI:
Add options to the .import command: --csv, --ascii, --skip
The .dump command now accepts multiple LIKE-pattern arguments and outputs the union of all matching tables.
Add the .oom command in debugging builds
Add the --bom option to the .excel, .output, and .once commands.
Enhance the .filectrl command to support the --schema option.
The UINT collating sequence extension is automatically loaded
The ESCAPE clause of a LIKE operator now overrides wildcard characters, so that the behavior now matches what PostgreSQL does.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Update ruby-activeldap to 6.0.2.
pkgsrc change: remove RUBY_VERSIONS_INCOMPATIBLE for ruby24.
6.0.2: 2020-05-19 {#release-6-0-2}
Improvements
* Added options to {ActiveLdap::Persistance#reload}.
[GitHub#176][Reported by Kevin McCormack]
* jndi: Improved DN escaping. [GitHub#178][Patch by Kevin McCormack]
Thanks
* Kevin McCormack
|
|
|
|
|
|
Update ruby-activerecord60 to 6.0.3.1.
## Rails 6.0.3.1 (May 18, 2020) ##
* No changes.
|
|
Changes 4.12.3:
* BUG 14301: Fix smbd panic on force-close share during async io.
* BUG 14343: s3: vfs_full_audit: Add missing fcntl entry in vfs_op_names[]
array.
* BUG 14361: vfs_io_uring: Fix data corruption with Windows clients.
* BUG 14372: Fix smbd crashes when MacOS Catalina connects if iconv
initialization fails.
* BUG 14150: Exporting from macOS Adobe Illustrator creates multiple copies.
* BUG 14256: smbd does a chdir() twice per request.
* BUG 14320: smbd mistakenly updates a file's write-time on close.
* BUG 14350: vfs_shadow_copy2: implement case canonicalisation in
shadow_copy2_get_real_filename().
* BUG 14375: Fix Windows 7 clients problem after upgrading samba file server.
* BUG 14359: s3: Pass DCE RPC handle type to create_policy_hnd.
* BUG 14155: Fix uxsuccess test with new MIT krb5 library 1.18.
* BUG 14342: mit-kdc: Explicitly reject S4U requests.
* BUG 14352: dbwrap_watch: Set rec->value_valid while returning nested
share_mode_do_locked().
* BUG 14345: lib:util: Fix smbclient -l basename dir.
* BUG 14336: s3:libads: Fix ads_get_upn().
* BUG 14348: ctdb: Fix a memleak.
* BUG 14366: Malicous SMB1 server can crash libsmbclient.
* BUG 14330: ldb: Bump version to 2.1.3, LMDB databases can grow without
bounds
* BUG 14361: vfs_io_uring: Fix data corruption with Windows clients.
* BUG 14344: s3/librpc/crypto: Fix double free with unresolved credential
cache.
* BUG 14358: docs-xml: Fix usernames in pam_winbind manpages.
|
|
Update ruby-activerecord52 to 5.2.4.3.
## Rails 5.2.4.3 (May 18, 2020) ##
* No changes.
|
|
5.1.0
repmgr: remove BDR 2.x support
repmgr: don't query upstream's data directory
repmgr: rename --recovery-conf-only to --replication-conf-only
repmgr: ensure postgresql.auto.conf is created with correct permissions
repmgr: minimize requirement to check upstream data directory location
during "standby clone"
repmgr: warn about missing pg_rewind prerequisites when excuting
"standby clone"
repmgr: add --upstream option to "node check"
repmgr: report error code on follow/rejoin failure due to non-available
replication slot
repmgr: ensure "node rejoin" checks for available replication slots
repmgr: improve "standby switchover" completion checks
repmgr: add replication configuration file ownership check to
"standby switchover"
repmgr: check the demotion candidate's registered repmgr.conf file can
be found
repmgr: consolidate replication connection code
repmgr: check permissions for "pg_promote()" and fall back to pg_ctl
if necessary
repmgr: in --dry-run mode, display promote command which will be used
repmgr: enable "service_promote_command" in PostgreSQL 12
repmgr: accept option -S/--superuser for "node check"
|
|
Redis 6.0.3:
Upgrade urgency CRITICAL: a crash introduced in 6.0.2 is now fixed.
Redis 6.0.2:
Upgrade urgency MODERATE: many not critical bugfixes in different areas.
Critical fix to client side caching when
keys are evicted from the tracking table but
no notifications are sent.
The following are the most serious fix:
* XPENDING should not update consumer's seen-time
* optimize memory usage of deferred replies - fixed
* Fix CRC64 initialization outside the Redis server itself.
* stringmatchlen() should not expect null terminated strings.
* Cluster nodes availability checks improved when there is
high Pub/Sub load on the cluster bus.
* Redis Benchmark: Fix coredump because of double free
* Tracking: send eviction messages when evicting entries.
* rax.c updated from upstream antirez/rax.
* fix redis 6.0 not freeing closed connections during loading.
New features:
dd
* Support setcpuaffinity on linux/bsd
* Client Side Caching: Add Tracking Prefix Number Stats in Server Info
* Add --user argument to redis-benchmark.c (ACL)
|
|
|
|
|
|
installed, anyway, resulting in a PLIST error.
ldb's snazzy little build system has no official configuration option
for this, so we reach in and flick the switch by hand.
|
|
|
|
0.36.5:
- Added support for dictionary input in CompositeType
- Added new EnrichedDateTime and EnrichedDate types
- Using String instead of LargeBinary for impl of EncryptedType
- Added support for JSONType in EncryptedType
0.36.4:
- Added jsonb_sql function
- Drop py27 support
|
|
1.3.17
orm
[orm] [usecase]
Added an accessor Comparator.expressions which provides access to the group of columns mapped under a multi-column ColumnProperty attribute.
[orm] [usecase]
Introduce relationship.sync_backref flag in a relationship to control if the synchronization events that mutate the in-Python attributes are added. This supersedes the previous change 5149, which warned that viewonly=True relationship target of a back_populates or backref configuration would be disallowed.
[orm] [bug]
Fixed bug where using with_polymorphic() as the target of a join via RelationshipComparator.of_type() on a mapper that already has a subquery-based with_polymorphic setting that’s equivalent to the one requested would not correctly alias the ON clause in the join.
[orm] [bug]
Fixed issue in the area of where loader options such as selectinload() interact with the baked query system, such that the caching of a query is not supposed to occur if the loader options themselves have elements such as with_polymorphic() objects in them that currently are not cache-compatible. The baked loader could sometimes not fully invalidate itself in these some of these scenarios leading to missed eager loads.
[orm] [bug]
Modified the internal “identity set” implementation, which is a set that hashes objects on their id() rather than their hash values, to not actually call the __hash__() method of the objects, which are typically user-mapped objects. Some methods were calling this method as a side effect of the implementation.
[orm] [bug]
An informative error message is raised when an ORM many-to-one comparison is attempted against an object that is not an actual mapped instance. Comparisons such as those to scalar subqueries aren’t supported; generalized comparison with subqueries is better achieved using Comparator.has().
engine
[engine] [bug]
Fixed fairly critical issue where the DBAPI connection could be returned to the connection pool while still in an un-rolled-back state. The reset agent responsible for rolling back the connection could be corrupted in the case that the transaction was “closed” without being rolled back or committed, which can occur in some scenarios when using ORM sessions and emitting .close() in a certain pattern involving savepoints. The fix ensures that the reset agent is always active.
schema
[schema] [bug]
Fixed issue where an Index that is deferred in being associated with a table, such as as when it contains a Column that is not associated with any Table yet, would fail to attach correctly if it also contained a non table-oriented expession.
[schema] [bug]
A warning is emitted when making use of the MetaData.sorted_tables attribute as well as the sort_tables() function, and the given tables cannot be correctly sorted due to a cyclic dependency between foreign key constraints. In this case, the functions will no longer sort the involved tables by foreign key, and a warning will be emitted. Other tables that are not part of the cycle will still be returned in dependency order. Previously, the sorted_table routines would return a collection that would unconditionally omit all foreign keys when a cycle was detected, and no warning was emitted.
[schema]
Add comment attribute to Column __repr__ method.
postgresql
[postgresql] [usecase]
Added support for columns or type ARRAY of Enum, JSON or JSONB in PostgreSQL. Previously a workaround was required in these use cases.
[postgresql] [usecase]
Raise an explicit CompileError when adding a table with a column of type ARRAY of Enum configured with Enum.native_enum set to False when Enum.create_constraint is not set to False
mssql
[mssql] [bug] [reflection]
Fix a regression introduced by the reflection of computed column in MSSQL when using the legacy TDS version 4.2. The dialect will try to detect the protocol version of first connect and run in compatibility mode if it cannot detect it.
[mssql] [bug] [reflection]
Fix a regression introduced by the reflection of computed column in MSSQL when using SQL server versions before 2012, which does not support the concat function.
oracle
[oracle] [bug]
Some modifications to how the cx_oracle dialect sets up per-column outputtype handlers for LOB and numeric datatypes to adjust for potential changes coming in cx_Oracle 8.
[oracle] [bug] [performance]
Changed the implementation of fetching CLOB and BLOB objects to use cx_Oracle’s native implementation which fetches CLOB/BLOB objects inline with other result columns, rather than performing a separate fetch. As always, this can be disabled by setting auto_convert_lobs to False.
As part of this change, the behavior of a CLOB that was given a blank string on INSERT now returns None on SELECT, which is now consistent with that of VARCHAR on Oracle.
firebird
[firebird] [change]
Adjusted dialect loading for firebird:// URIs so the external sqlalchemy-firebird dialect will be used if it has been installed, otherwise fall back to the (now deprecated) internal Firebird dialect.
|
|
|
|
|
|
|
|
Upstream changes:
Changes in DBI 1.643 - ...
Fix memory corruption in XS functions when Perl stack is reallocated
thanks to Pali
Fix calling dbd_db_do6 API function
thanks to Pali
Fix potentially calling newSV(0) in malloc_using_sv()
thanks to Pali
Fix order of XS preparse() ps_accept and ps_return argument names
thanks to Petr Písař
Fix a potential NULL profile dereference in dbi_profile()
thanks to Petr Písař
Fix a buffer overflow on an overlong DBD class name
thanks to Petr Písař
Remove remnants of support for perl <= v5.8.0
thanks to Pali and H.Merijn Brand
Update Devel::PPPort and remove redundant compatibility macros
thanks to Pali and H.Merijn Brand
Correct minor typo in documentation
thanks to Mohammad Anwar
Correct documentation introducing $dbh->selectall_array()
thanks to Pali
Introduce select and do wrappers earlier in the documentation
thanks to Dan Book
Mark as deprecated old API functions which overflow or are affected by
Unicode issues, thanks to Pali
Add new attribute RaiseWarn, similar to RaiseError,
thanks to Pali
|
|
|
|
Update ruby-activerecord60 to 6.0.3.
## Rails 6.0.3 (May 06, 2020) ##
* Recommend applications don't use the `database` kwarg in `connected_to`
The database kwarg in `connected_to` was meant to be used for one-off scripts but is often used in requests. This is really dangerous because it re-establishes a connection every time. It's deprecated in 6.1 and will be removed in 6.2 without replacement. This change soft deprecates it in 6.0 by removing documentation.
*Eileen M. Uchitelle*
* Fix support for PostgreSQL 11+ partitioned indexes.
*Sebastián Palma*
* Add support for beginless ranges, introduced in Ruby 2.7.
*Josh Goodall*
* Fix insert_all with enum values
Fixes #38716.
*Joel Blum*
* Regexp-escape table name for MS SQL
Add `Regexp.escape` to one method in ActiveRecord, so that table names with regular expression characters in them work as expected. Since MS SQL Server uses "[" and "]" to quote table and column names, and those characters are regular expression characters, methods like `pluck` and `select` fail in certain cases when used with the MS SQL Server adapter.
*Larry Reid*
* Store advisory locks on their own named connection.
Previously advisory locks were taken out against a connection when a migration started. This works fine in single database applications but doesn't work well when migrations need to open new connections which results in the lock getting dropped.
In order to fix this we are storing the advisory lock on a new connection with the connection specification name `AdisoryLockBase`. The caveat is that we need to maintain at least 2 connections to a database while migrations are running in order to do this.
*Eileen M. Uchitelle*, *John Crepezzi*
* Ensure `:reading` connections always raise if a write is attempted.
Now Rails will raise an `ActiveRecord::ReadOnlyError` if any connection on the reading handler attempts to make a write. If your reading role needs to write you should name the role something other than `:reading`.
*Eileen M. Uchitelle*
* Enforce fresh ETag header after a collection's contents change by adding
ActiveRecord::Relation#cache_key_with_version. This method will be used by
ActionController::ConditionalGet to ensure that when collection cache versioning
is enabled, requests using ConditionalGet don't return the same ETag header
after a collection is modified. Fixes #38078.
*Aaron Lipman*
* A database URL can now contain a querystring value that contains an equal sign. This is needed to support passing PostgresSQL `options`.
*Joshua Flanagan*
* Retain explicit selections on the base model after applying `includes` and `joins`.
Resolves #34889.
*Patrick Rebsch*
|
|
The mentioned files don't contain any placeholder, and they are not
installed either.
|
|
This should have been PGSQL_VERSIONS_INCOMPATIBLE from the beginning, as
the comment above that line clearly said.
|
|
|
|
|
|
|
|
|
|
|
|
3.5.2:
* Tune the locking in ConnectionPool.get_connection so that the lock is
not held while waiting for the socket to establish and validate the
TCP connection.
|
|
|
|
|
|
|
|
PostgreSQL 12.3, 11.8, 10.13, 9.6.18, and 9.5.22 Released!
Posted on 2020-05-14 by PostgreSQL Global Development Group
The PostgreSQL Global Development Group has released an update to all supported versions of our database system, including 12.3, 11.8, 10.13, 9.6.18, and 9.5.22. This release fixes one security issue found in the PostgreSQL server and over 75 bugs reported over the last three months.
Please plan to update at your earliest convenience.
Security Issues
CVE-2020-10733: Windows installer runs executables from uncontrolled directories.
Versions Affected: 9.5 - 12. The security team does not test unsupported versions, but this issue existed before PostgreSQL 9.5.
The Windows installer for PostgreSQL invokes system-provided executables that do not have fully-qualified paths. Executables in the directory where the installer loads or the current working directory take precedence over the intended executables. An attacker having permission to add files into one of those directories can use this to execute arbitrary code with the installer's administrative rights.
The PostgreSQL project thanks Hou JingYi (@hjy79425575) for reporting this problem.
Bug Fixes and Improvements
This update also fixes over 75 bugs that were reported in the last several months. Some of these issues affect only version 12, but may also affect all supported versions.
Some of these fixes include:
Several fixes for GENERATED columns, including an issue where it was possible to crash or corrupt data in a table when the output of the generated column was the exact copy of a physical column on the table, e.g. if the expression called a function which could return its own input.
Several fixes for ALTER TABLE, including ensuring the SET STORAGE directive is propagated to a table's indexes.
Fix a potential race condition when using DROP OWNED BY while another session is deleting the same objects.
Allow for a partition to be detached when it has inherited ROW triggers.
Several fixes for REINDEX CONCURRENTLY, particularly with issues when a REINDEX CONCURRENTLY operation fails.
Fix crash when COLLATE is applied to an uncollatable type in a partition bound expression.
Fix performance regression in floating point overflow/underflow detection.
Several fixes for full text search, particularly with phrase searching.
Fix query-lifespan memory leak for a set-returning function used in a query's FROM clause.
Several reporting fixes for the output of VACUUM VERBOSE.
Allow input of type circle to accept the format (x,y),r, which is specified in the documentation.
Allow for the get_bit() and set_bit() functions to not fail on bytea strings longer than 256MB.
Avoid premature recycling of WAL segments during crash recovery, which could lead to WAL segments being recycled before being archived.
Avoid attempting to fetch nonexistent WAL files from archive storage during recovery by skipping irrelevant timelines.
Several fixes for logical replication and replication slots.
Fix several race conditions in synchronous standby management, including one that occurred when changing the synchronous_standby_names setting.
Several fixes for GSSAPI support, include a fix for a memory leak that occurred when using GSSAPI encryption.
Ensure that members of the pg_read_all_stats role can read all statistics views.
Fix performance regression in information_schema.triggers view.
Fix memory leak in libpq when using sslmode=verify-full.
Fix crash in psql when attempting to re-establish a failed connection.
Allow tab-completion of the filename argument to \gx command in psql.
Add pg_dump support for ALTER ... DEPENDS ON EXTENSION.
Several other fixes for pg_dump, which include dumping comments on RLS policies and postponing restore of event triggers until the end.
Ensure pg_basebackup generates valid tar files.
pg_checksums skips tablespace subdirectories that belong to a different PostgreSQL major version
Several Windows compatibility fixes
This update also contains tzdata release 2020a for DST law changes in Morocco and the Canadian Yukon, plus historical corrections for Shanghai. The America/Godthab zone has been renamed to America/Nuuk to reflect current English usage ; however, the old name remains available as a compatibility link. This also updates initdb's list of known Windows time zone names to include recent additions.
|
|
4.7.6:
Bugfixes
- Fixed an issue with some versions of the ``wheel`` dist
failing because of being unable to detect the license file.
|
|
|
|
|