Age | Commit message (Collapse) | Author | Files | Lines |
|
+BUILD_DEPENDS+= p5-DBD-SQLite2-[0-9]*:../../databases/p5-DBD-SQLite2
+BUILD_DEPENDS+= p5-Test-Deep-[0-9]*:../../devel/p5-Test-Deep
+BUILD_DEPENDS+= p5-Test-Differences-[0-9]*:../../devel/p5-Test-Differences
+BUILD_DEPENDS+= p5-Text-Diff-[0-9]*:../../textproc/p5-Text-Diff
|
|
+BUILD_DEPENDS+= p5-Test-Deep-[0-9]*:../../devel/p5-Test-Deep
|
|
Fix a backwards compatibility problem in version 3.12.0 and 3.12.1: Columns declared as "INTEGER" PRIMARY KEY (with quotes around the datatype keyword) where not being recognized as an INTEGER PRIMARY KEY, which resulted in an incompatible database file.
Fix a bug (present since version 3.9.0) that can cause the DELETE operation to miss rows if PRAGMA reverse_unordered_selects is turned on.
Fix a bug in the code generator that can causes incorrect results if two or more virtual tables are joined and the virtual table used in outer loop of the join has an IN operator constraint.
Correctly interpret negative "PRAGMA cache_size" values when determining the cache size used for sorting large amounts of data.
|
|
Fix dependencies.
Changes in 3.2.1:
- Introduced an update to allow deserializer compilation with
recently released Cython 0.24
|
|
Security Notes
--------------
The linked OpenSSL library for the MySQL Commercial Server has been updated to version 1.0.1s. Issues fixed in the new version are described at http://www.openssl.org/news/vulnerabilities.html.
This change does not affect the Oracle-produced MySQL Community build of MySQL Server, which uses the yaSSL library instead.
MySQL client programs now support an --ssl-mode option that enables you to specify the security state of the connection to the server. The default value is DISABLED (establish an unencrypted connection). --ssl-mode=REQUIRED) can be specified to require a secure connection, or fail if a secure connection cannot be obtained.
These clients support --ssl-mode: mysql, mysqladmin, mysqlcheck, mysqldump, mysqlimport, mysqlshow, mysqlpump, mysqlslap, mysqltest, mysql_upgrade.
For more information, see Command Options for Secure Connections.
Bugs Fixed
|
|
Security Notes
--------------
MySQL client programs now support an --ssl-mode option that enables you to specify the security state of the connection to the server. The default value is DISABLED (establish an unencrypted connection). --ssl-mode=REQUIRED) can be specified to require a secure connection, or fail if a secure connection cannot be obtained.
These clients support --ssl-mode: mysql, mysqladmin, mysqlcheck, mysqldump, mysqlimport, mysqlshow, mysqlpump, mysqlslap, mysqltest, mysql_upgrade.
For more information, see Command Options for Secure Connections.
Bugs Fixed
|
|
Upstream changes:
2.032001 2016-04-13 22:01:03-07:00 America/Los_Angeles
- Fix simple deletion and updates for ::DateMethods1
(Thanks for the report Wes Malone and Erland Injerd, and the help to fix the
actual bug ribasushi!)
|
|
Upstream changes:
1.001036 2016-03-21 14:59:55+00:00 UTC
- releasing as stable
1.00103_5 2016-03-11 20:39:49+00:00 UTC (TRIAL RELEASE)
- Will completely ignore sequences in Oracle due to having to drop and recreate them
1.001034 2016-01-05 15:05:26+00:00 UTC
1.00103_3 2015-12-08 16:33:56+00:00 UTC (TRIAL RELEASE)
- RT#108017 bugfix ( hatorikibble++ )
- added File::Temp to deps ( hatorikibble++ )
|
|
Upstream changes:
0.56 2016-03-16T17:07:05Z
- Added Firebird support, thanks to Stefan Suciu.
- Fixed SQLite savepoint support to properly detect SQlite versions 3.9
and higher.
- Restored MySQL savepoint testing when the DBICTEST_* environment
variables are set.
0.55 2016-02-05T18:59:24Z
- Added versions to the RollbackError exception classes to make PAUSE
happy.
0.54 2016-02-05T18:52:44Z
- Removeed the Pod tests from the distribution.
- Fixed the example code for handling `rollback_error` exceptions in the
documentation to properly wrap the transaction in an exception
handler. Patch from Perlover (issue #32).
- Improved handling of connection failures when RaiseError (or
HandleError) is not set. Thanks to Andreas Huber for the report and
fix.
- Document that `$_` is set locally, not globally, in the methods that
set it. Suggested by William Lindley.
- The disconnect method no longer longer remove entries from the DBI
handle's CachedKids attribute. That behavior appears to be a
workaround for a database we don't (yet) support.
- Fixed a test failure where the test system has the `$DBI_DSN` or
`$DBI_DRIVER` environment variable set. Thanks to Erik Rijkers for the
patch.
- Added recommendation to use DBD::Pg 3.5.0 or later to the Pg driver.
Earlier versions had an incorrect implementation of the `ping()`
method (Issue #41).
|
|
Upstream changes:
1.410 2016-04-11
[Bug fixes]
* Fix RT#113625 - Unnecessary x-bits (Kent Fredric)
[Documentation]
* pod2markdown README.md from lib/SQL/Statement.pm
1.409 2016-04-06
* Release 1.408_001 without further changes as 1.409
1.408_001 2016-03-07
[Bug fixes]
* Fix RT#112530 - t/06virtual.t fails with -Duselongdouble (thanks
Slaven Rezic)
* Fix RT#105852 - dependency installation isn't triggered properly in
cpan (thanks Mithaldu)
* Fix RT#99349 - bind variables are not bound to placeholders in the
correct order (thanks vulpeculus@gmx.de)
[Documentation]
* Update Copyright statements, add where missing (according to records)
* Add license conditions where missing
* bundle copy of license conditions to distribution
|
|
Upstream changes:
0.65 -- Mon Apr 6 19:43:37 CEST 2015
Enhancements:
* t/74matchedvalues.t: more tests
* {ASN,Extension}.pm: update ExtendedResponse to RFC 4511
* Constant.pm: add LDAP_NOTICE_OF_DISCONNECTION
* Control/DontUseCopy.pm: new
* Control/ProxyAuth.pm: make sure criticality does not get changed
* Control/Relax.pm: make sure value & criticality do not get changed
* Control/ManageDsaIT.pm: make sure value never gets set
Bug Fixes
* LDAP.pm: do not set default sslversion for start_tls() & LDAPS
Instead of second-guessing a default sslversion for start_tls() and LDAPS,
rely on the - known to be sane - default value used by IO::Socket::SSL.
* RT#100151: LDAP.pm: localize $SIG{__DIE__} in IPv6 support check
Thanks to Troy Loveday <troyl@ti.com> for the detailed bug report and patch.
* FAQ.pod: fix error in search() example
* RFC.pod: typo fix
0.64 -- Thu Jun 19 17:48:08 CEST 2014
Bug Fixes:
* LDAP.pm: set SSL_cipher_list correctly
* RT#96203: LDAP.pm: use correct length for syswrite
* LDIF.pm: fix next outside loop in _write_one_entry
* Entry.pod: fix typo
|
|
Upstream changes:
2.51, 2014-09-05 Feature enhancements to dbcolmovingstats, dbcolcreate,
dbmapreduce, and new sqlselect_to_db
ENHANCEMENT
dbcolcreate now has a "--no-recreate-fatal" that causes it to
ignore creation of existing columns (instead of failing).
ENHANCEMENT
dbmapreduce once again is robust to reducers that output the key;
"--no-prepend-key" is no longer mandatory.
ENHANCEMENT
dbcolsplittorows can now enumerate the output rows with "-E".
BUG FIX
dbcolmovingstats is more mathematically robust. Previously for
some inputs and some platforms, floating point rounding could
sometimes cause squareroots of negative numbers.
NEW sqlselect_to_db converts the output of the MySQL or MarinaDB select
comment into fsdb format.
INCOMPATIBLE CHANGE
dbfilediff now outputs the second row when doing sloppy numeric
comparisons, to better support test suites.
2.52, 2014-11-03 Fixing the test suite for line number changes.
ENHANCEMENT
Test suites changes to be robust to exact line numbers of failures,
since different Perl releases fail on different lines.
<https://bugzilla.redhat.com/show_bug.cgi?id=1158380>
2.53, 2014-11-26 bug fixes and stability improvements to dbmapreduce
ENHANCEMENT
The dbfilediff how supports a "--quiet" option.
ENHANCEMENT
Better documention of dbpipeline_filter.
BUGFIX
Added groff-base and perl-podlators to the Fedora package spec.
Fixes <https://bugzilla.redhat.com/show_bug.cgi?id=1163149>. (Also
in package 2.52-2.)
BUGFIX
An important stability improvement to dbmapreduce. It, plus
dbmultistats, and dbcolstats now support controlled parallelism
with the "--pararallelism=N" option. They default to run with the
number of available CPUs. dbmapreduce also moderates its level of
parallelism. Previously it would create reducers as needed,
causing CPU thrashing if reducers ran much slower than data
production.
BUGFIX
The combination of dbmapreduce with dbrowenumerate now works as it
should. (The obscure bug was an interaction with dbcolcreate with
non-multi-key reducers that output their own key. dbmapreduce has
too many useful corner cases.)
2.54, 2014-11-28 fix for the test suite to correct failing tests on not-my-
platform
BUGFIX
Sigh, the test suite now has a test suite. Because, yes, I broke
it, causing many incorrect failures at cpantesters. Now fixed.
2.55, 2015-01-05 many spelling fixes and dbcolmovingstats tests are more
robust to different numeric precision
ENHANCEMENT
dbfilediff now can be extra quiet, as I continue to try to track
down a numeric difference on FreeBSD AMD boxes.
ENHANCEMENT
dbcolmovingstats gave different test output (just reflecting
rounding error) when stddev approaches zero. We now detect hand
handle this case. See
<https://rt.cpan.org/Public/Bug/Display.html?id=101220> and thanks
to H. Merijn Brand for the bug report.
BUG FIX
Many, many spelling bugs found by H. Merijn Brand for the bug
report.
INCOMPATBLE CHANGE
A number of programs had misspelled "separator" in
"--fieldseparator" and "--columnseparator" options as "seperator".
These are now correctly spelled.
2.56, 2015-02-03 fix against Getopt::Long-2.43's stricter error checkign
BUG FIX
Internal argument parsing uses Getopt::Long, but mixed pass-through
and <>. Bug reported by Petr Pisar at
<https://bugzilla.redhat.com/show_bug.cgi?id=1188538>.a
BUG FIX
Added missing BuildRequires for "XML::Simple".
|
|
Upstream changes:
0.45 Wed May 6 22:17:33 PDT 2015
- MySQL does not support DEFAULT for TEXT/BLOB columns, closes: CPAN#58505
- doc: Add repository information
- fix SQLite reverse-engineering, closes: CPAN#95961
- fix Pg reverse-engineering of foreign key MATCH/ON DELETE/ON UPDATE
clauses
|
|
Upstream changes:
1.06 Sun Mar 6 20:48:11 CET 2016
Add support for W column type (byte array by Visual FoxPro).
Fixed overload arg warning.
Restore the table_info functionality.
Fix for type B little endian issue, reported by Andres Thomas.
|
|
Features
- cqlengine: Warn on sync_schema type mismatch
- cqlengine: Automatically defer fields with the '=' operator
(and immutable values) in select queries
- cqlengine: support non-equal conditions for LWT
- cqlengine: sync_table should validate the primary key composition
- cqlengine: token-aware routing for mapper statements
Bug Fixes
- Deleting a column in a lightweight transaction raises
a SyntaxException
- cqlengine: make Token function works with named tables/columns
- comparing models with datetime fields fail #79
- cython date deserializer integer math should be aligned
with CPython
- db_field is not always respected with UpdateStatement
- Sync_table fails on column.Set with secondary index
|
|
|
|
PostGIS 2.2.2
2016/03/22
* Bug Fixes *
- #3463, Fix crash on face-collapsing edge change
- #3422, Improve ST_Split robustness on standard precision double
systems (arm64, ppc64el, s390c, powerpc, ...)
- #3427, Update spatial_ref_sys to EPSG version 8.8
- #3433, ST_ClusterIntersecting incorrect for MultiPoints
- #3435, ST_AsX3D fix rendering of concave geometries
- #3436, memory handling mistake in ptarray_clone_deep
- #3437, ST_ClusterIntersecting incorrect for MultiPoints
- #3461, ST_GeomFromKML crashes Postgres when there are
innerBoundaryIs and no outerBoundaryIs
- #3429, upgrading to 2.3 or from 2.1 can cause loop/hang on some
platforms
- #3460, ST_ClusterWithin 'Tolerance not defined' error after upgrade
- #3490, Raster data restore issues, materialized views
Scripts postgis_proc_set_search_path.sql, rtpostgis_proc_set_search_path.sql
refere to http://postgis.net/docs/manual-2.2/RT_FAQ.html#faq_raster_data_not_restore
- #3426, failing POINT EMPTY tests on fun architectures
|
|
in the past few weeks. Primary development continues on the 1.1 series which is slated for initial releases in the spring.
1.0.12 includes relatively minor fixes, including a revision to a fix made for version 1.0.10 where we're attempting to report on the "cause" of an error that is interrupted by a later failure to emit a ROLLBACK on the MySQL platform. While Python 3 solves this problem using exception chaining and cause reporting, on Python 2 we emit a warning so that the cause isn't totally concealed. The condition has been expanded to emit this warning in a much wider range of scenarios.
|
|
Upstream changes:
4.33.0.txt
doc/release_notes/4.33.0.txt
Last Update: 2016-04-01 07:24:12 -0700
New Features
A Sequel::Model.require_valid_table accessor has been added. This setting is false for backwards compatibility, but if set to true, will raise an error you try to create a model class where an invalid table name is used or the schema or columns cannot be determined. This makes it easier to catch bugs, as things will fail fast, but it means that you must change code like:
class Foo < Sequel::Model
set_dataset :my_foos
end
to:
class Foo < Sequel::Model(:my_foos)
end
as otherwise Foo will attempt to use the foos table by default when creating the class, which will raise an error as it is not the correct table name.
Sequel::Database#transaction now supports a :savepoint=>:only option, which will create a savepoint if already inside a transaction, but will yield without creating a transaction if not inside a transaction. The use case for this is when you are running code that may raise an exception, and you don't want to invalidate the current transaction state.
Other Improvements
The graph_each extension now splits results into subhashes when using Sequel::Dataset#first, as it did before Sequel 4.27.0.
On PostgreSQL, Dataset#insert_conflict now accepts an array of columns as the value for the :target option.
You can now pass a Sequel::SQL::Identifier or a Sequel::SQL::QualifiedIdentifer as the table argument when creating a foreign key. Previously, only symbols were supported, and using other values required specifying the :table option. So this will now work to reference a table that includes a double underscore:
foreign_key :foo_id, Sequel.identifier(:fo__oo)
Creating model classes inside a transaction on PostgreSQL where the implicit table name isn't correct no longer causes the transaction to fail.
Similar issues were also fixed in the boolean_readers, boolean_subsets, and class_table_inheritance plugins.
On PostgreSQL, You can now use the :qualify=>true option in the schema dumper, to dump using schema-qualified table names.
On Microsoft SQL Server, the set_column_allow_null and set_column_not_null alter table methods now work on varchar(max), text, and similar columns.
On Oracle, Sequel::Database#sequence_for_table now returns nil if given a table that doesn't exist or that the user does not have access to.
Passing arbitrary objects to a model association method now indicates that the association should be reloaded, which was used to work but was broken in Sequel 4.32.0.
It is now possible to raise Sequel::ValidationFailed and Sequel::HookFailed without an argument.
Backwards Compatibility
Sequel::Model no longer swallows many errors when subclassing or setting datasets. While this should hopefully not affect backwards compatibility, it may break things where the methods were raising exceptions. If this does break backwards compatibility, it is most likely because it is no longer hiding another bug that should be fixed. Specific changes include:
Model.inherited no longer rescues exceptions raised by set_dataset
When subclassing a model that has a dataset, the columns and schema are just copied from the superclass
Only Sequel::Error is rescued in calls to columns and schema, before it would rescue StandardError.
The Sequel.firebird and Sequel.informix adapter methods have been removed, they are no longer needed as the firebird and informix adapters were removed a few versions back.
|
|
supported versions of our database system, including 9.5.2, 9.4.7, 9.3.12, 9.2.16, and 9.1.21. This release fixes two security issues and one index corruption issue in version 9.5. It also contains a variety of bug fixes for earlier versions. Users of PostgreSQL 9.5.0 or 9.5.1 should update as soon as possible.
This release closes security hole CVE-2016-2193, where a query plan might get reused for more than one ROLE in the same session. This could cause the wrong set of Row Level Security (RLS) policies to be used for the query.
The update also fixes CVE-2016-3065, a server crash bug triggered by using pageinspect with BRIN index pages. Since an attacker might be able to expose a few bytes of server memory, this crash is being treated as a security issue.
|
|
Fix a boundary condition error introduced by version 3.12.0 that can result in a crash during heavy SAVEPOINT usage.
Fix views so that they inherit column datatypes from the table that they are defined against, when possible.
Fix the query planner so that IS and IS NULL operators are able to drive an index on a LEFT OUTER JOIN.
|
|
- cqlengine: Fix performance issue related to additional "COUNT"
queries (PYTHON-522)
|
|
Potentially Disruptive Change:
------------------------------
The SQLITE_DEFAULT_PAGE_SIZE is increased from 1024 to 4096. The SQLITE_DEFAULT_CACHE_SIZE is changed from 2000 to -2000 so the same amount of cache memory is used by default. See the application note on the version 3.12.0 page size change for further information.
Performance enhancements:
-------------------------
Enhancements to the Lemon parser generator so that it creates a smaller and faster SQL parser.
Only create master journal files if two or more attached databases are all modified, do not have PRAGMA synchronous set to OFF, and do not have the journal_mode set to OFF, MEMORY, or WAL.
Only create statement journal files when their size exceeds a threshold. Otherwise the journal is held in memory and no I/O occurs. The threshold can be configured at compile-time using SQLITE_STMTJRNL_SPILL or at start-time using sqlite3_config(SQLITE_CONFIG_STMTJRNL_SPILL).
The query planner is able to optimize IN operators on virtual tables even if the xBestIndex method does not set the sqlite3_index_constraint_usage.omit flag of the virtual table column to the left of the IN operator.
The query planner now does a better job of optimizing virtual table accesses in a 3-way or higher join where constraints on the virtual table are split across two or more other tables of the join.
More efficient handling of application-defined SQL functions, especially in cases where the application defines hundreds or thousands of custom functions.
The query planner considers the LIMIT clause when estimating the cost of ORDER BY.
The configure script (on unix) automatically detects pread() and pwrite() and sets compile-time options to use those OS interfaces if they are available.
Reduce the amount of memory needed to hold the schema.
Other miscellaneous micro-optimizations for improved performance and reduced memory usage.
New Features:
-------------
Added the SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER option to sqlite3_db_config() which allows the two-argument version of the fts3_tokenizer() SQL function to be enabled or disabled at run-time.
Added the sqlite3rbu_bp_progress() interface to the RBU extension.
The PRAGMA defer_foreign_keys=ON statement now also disables RESTRICT actions on foreign key.
Added the sqlite3_system_errno() interface.
Added the SQLITE_DEFAULT_SYNCHRONOUS and SQLITE_DEFAULT_WAL_SYNCHRONOUS compile-time options. The SQLITE_DEFAULT_SYNCHRONOUS compile-time option replaces the SQLITE_EXTRA_DURABLE option, which is no longer supported.
Enhanced the ".stats" command in the command-line shell to show more information about I/O performance obtained from /proc, when available.
Bug fixes:
----------
Make sure the sqlite3_set_auxdata() values from multiple triggers within a single statement do not interfere with one another.
Fix the code generator for expressions of the form "x IN (SELECT...)" where the SELECT statement on the RHS is a correlated subquery.
Fix a harmless TSAN warning associated with the sqlite3_db_readonly() interface.
|
|
1.3.5
This release fixes a crash in mongoc_cleanup when an allocator
had been set with bson_mem_set_vtable, and introduces
a configure option MONGOC_NO_AUTOMATIC_GLOBALS which prevents
code built with GCC from automatically calling mongoc_init and
mongoc_cleanup when your code does not.
1.3.4
This release fixes a security vulnerability: when a mongoc_client_t
uses SSL and is disconnected, it failed to re-verify the server
certificate after reconnecting. This flaw affects
single clients, not pooled ones.
|
|
|
|
|
|
|
|
The previous commit replaced the distfile with a new one with the same
name. In pkgsrc, we have rules for that; apply them.
|
|
Bumped PKGREVISION in case anyone already built the wrong one.
|
|
|
|
Mark as ready for python-3.x now that py-postgresql is.
Bump PKGREVISION.
|
|
The biggest change here is Python 3.x compatibility. Other changes are too
numerous to list. See http://www.pygresql.org/ for all the changes.
|
|
|
|
reset maintainer (ok by joerg@)
Recent changes:
Date Dev Ver Change details
---------- --- ------ --------------
2016-01-04 AV 1.22.0 Resolved an issue related to check options selection in
the view properties dialog with the check option.
[Reported by: Sebastian Albert, Patched by: Neel Patel]
2015-12-08 AV 1.22.0 Merged the libssh2 to the latest version.
[Akshay Joshi]
2015-11-19 DP 1.22.0 Properly detect serial columns as such when
identifiers have been truncated.
2015-10-23 AV 1.22.0 Fixes an issue related to the column inheritance
information properly, when one (or, more) common columns
are inherited from multiple tables.
[Reported by: Liu Yuanyuan, Patched by: Akshay Joshi]
2015-10-12 AV 1.22.0 Ensure the correct syntax used for moving the objects
from one tablespace to another. [Sanket Mehta]
2015-10-07 DP 1.22.0 Ensure the correct line endings are used when copying
from the SQL Pane [Nikolai Zhubr]
2015-09-25 AV 1.22.0 Toolbar icons, and menu items for Commit and Rollback
actions. [John Obaterspok]
2015-09-24 DP 1.22.0 Display the connection details for the current browser
object in the status bar [Adam Scott]
2015-09-21 AV 1.22.0 Fixed an issue related to different menus enabling in
the Query Tool on Ubunutu unity.
[Reported by: Vahdet Mert]
2015-09-21 AV 1.22.0 Reset the position (x, y) for dialog(s), and frame(s) to
0 (if found negative), while saving its position and
size. [Reported By: Mark, Patch: Sanket Mehta,
Reworked, and Reviewed: Ashesh]
2015-09-21 AV 1.22.0 Fixes an issue identifying the return type to TABLE in
some cases, using pg_get_function_result(..) for the
same instead of format_type(..)
[Reported By: Guillermo E. Villanueva,
PATCH:Sanket Mehta]
2015-09-21 AV 1.22.0 Honour PGPASSFILE environment variable for saving,
retrieving the password instead of always works with
pgpass.conf (on windows)/.pgpass (on non-windows)
[PATCH: Prasad Somwanshi, Reworked by: Sanket Mehta,
Reviewed by: Ashesh Vashi, Sanket Mehta]
2015-09-14 AV 1.22.0 Fix a segfault occurs while detecting transaction
section requirement, when autocommit has been disabled.
[Reported by John Obaterspok, Patch by Sanket Mehta]
2015-09-14 AV 1.22.0 Format execution time in a more readable manner
[John Obaterspok]
2015-07-27 AV 1.22.0 Improve sorting in Data editor
[J. F. Oster, Reviewed by Sanket Mehta]
2015-07-27 AV 1.22.0 Allow to format the selecte SQL using external tools
in Query Editor [J. F. Oster]
2015-05-22 AV 1.22.0 Allow to set auto-commit mode to on/off in the query
editor [Sanket Mehta]
|
|
Set up a separate user, previous PGUSER/PGGROUP integration didn't
make sense.
2016-02-26 - PgBouncer 1.7.2 - "Finally Airborne"
- Fix crash on stale pidfile removal. Problem introduced in 1.7.1.
- Disable cleanup - it breaks takeover and is not useful for
production loads. Problem introduced in 1.7.1.
- After takeover, wait until pidfile is gone before booting. Slow
shutdown due to memory cleanup exposed existing race. (#113)
- Make build reproducible by dropping DBGVER handling. (#112)
- Antimake: Sort file list from $(wildcard), newer gmake does not
sort it anymore. (#111)
- Show libssl version in log.
- deb: Turn on full hardening.
2016-02-18 - PgBouncer 1.7.1 - "Forward To Five Friends Or Else"
- WARNING: Since version 1.7, server_reset_query is not executed
when database is in transaction-pooling mode. Seems this was not
highlighted enough in 1.7 announcement. If your apps depend on
that happening, use server_reset_query_always to restore previous
behaviour.
- TLS: Rename sslmode "disabled" to "disable" as that is what
PostgreSQL uses.
- TLS: client_tls_sslmode=verify-ca/-full now reject connections
without client certificate. (#104)
- TLS: client_tls_sslmode=allow/require do validate client
certificate if sent. Previously they left cert validation
unconfigured so connections with client cert failed. (#105)
- Fix memleak when freeing database.
- Fix potential memleak in tls_handshake().
- Fix EOF handling in tls_handshake().
- Fix too small memset in asn1_time_parse compat.
- Fix non-TLS (--without-openssl) build. (#101)
- Fix various issues with Windows build. (#100)
- TLS: Use SSL_MODE_RELEASE_BUFFERS to decrease memory usage of
inactive connections.
- Clean allocated memory on exit. Helps to run memory-leak
checkers.
- Improve server_reset_query documentation. (#110)
- Add TLS options to sample config.
2015-12-18 - PgBouncer 1.7 - "Colors Vary After Resurrection"
- Support TLS connections. OpenSSL/LibreSSL is used as backend
implementation.
- Support authentication via TLS client certificate.
- Support "peer" authentication on Unix sockets.
- Support Host Based Access control file, like pg_hba.conf in
Postgres. This allows to configure TLS for network connections
and "peer" authentication for local connections.
- Set query_wait_timeout to 120s by default. Current default (0)
causes infinite queueing, which is not useful. That means if
client has pending query and has not been assigned to server
connection, the client connection will be dropped.
- Disable server_reset_query_always by default. Now reset query is
used only in pools that are in session mode.
- Increase pkt_buf to 4096 bytes. Improves performance with TLS.
The behaviour is probably load-specific, but it should be safe
to do as since v1.2 the packet buffers are split from connections
and used lazily from pool.
- Support pipelining count expected ReadyForQuery packets. This
avoids releasing server too early. Fixes #52.
- Improved sbuf_loopcnt logic - socket is guarateed to be
reprocessed even if there are no event from socket. Required for
TLS as it has it's own buffering.
- Adapt system tests to work with modern BSD and MacOS. (Eric
Radman)
- Remove crypt auth. It's obsolete and not supported by PostgreSQL
since 8.4.
- Fix plain "--with-cares" configure option - without argument it
was broken.
|
|
These should never have made it in. Bump resp. PKGREVISIONs.
|
|
|
|
This package is well beyond obsolete, and is no longer maintained
upstream. It only existed because postgis2 (now at 2.2, 2 major
releases later) was added instead of just updating this one.
|
|
|
|
3.2.4
- mongorestore --noIndexRestore inhibits empty collection creation
3.2.3
- mongoexport chokes on data with quotes
3.2.1
- Add bypassDocumentValidation option to mongorestore and mongoimport
- Missing "from" text in mongorestore status message
3.2.0
- Add bypassDocumentValidation option to mongorestore and mongoimport
- Missing "from" text in mongorestore status message
3.0.8
- bsondump does not keep attribut order
- mongodump issue with temporary map/reduce collections
- Error restoring database "insertion error: EOF"
|
|
- Fixed issue with setting optime when running with journaling
disabled
- Have read concern majority reflect journaled state on
the primary
- Fixed issue where specifying replication.enableMajorityReadConcern
implied true regardless of the actual boolean value
- Fixed issue causing segfault when running aggregation that
includes $lookup
|
|
|
|
Features
- Pass name of server auth class to AuthProvider
- Surface schema agreed flag for DDL statements
- Automatically convert float and int to Decimal on serialization
- Eventlet Reactor IO improvement
- Make pure Python ProtocolHandler available even when Cython is
present
- Optional Cython deserializer for bytes as bytearray
- Add Session.default_serial_consistency_level
- cqlengine: Expose prior state information via cqlengine
LWTException
- cqlengine: Collection datatype "contains" operators support
(Cassandra 2.1)
- cqlengine: Add DISTINCT query operator
- cqlengine: Tuple cqlengine api
- cqlengine: Add support for UPDATE/DELETE ... IF EXISTS statements
- cqlengine: Allow nested container types
- cqlengine: Add ability to set query's fetch_size and limit
- cqlengine: Internalize default keyspace from successive set_session
- cqlengine: Warn when Model.create() on Counters
Bug Fixes
- Bus error (alignment issues) when running cython on some ARM
platforms
- Overflow when decoding large collections (cython)
- Timer heap comparison issue with Python 3
- Cython deserializer date overflow at 2^31 - 1
- Decode error encountered when cython deserializing large map
results
- Don't require Cython for build if compiler or Python header
not present
- Unorderable types in task scheduling with Python 3
- cqlengine: Fix crash when updating a UDT column with a None value
- cqlengine: Race condition in ..connection.execute with lazy_connect
- cqlengine: doesn't support case sensitive column family names
- cqlengine: UserDefinedType mandatory in create or update
- cqlengine: db_field breaks UserType
- cqlengine: UDT badly quoted
- cqlengine: Use of db_field on primary key prevents querying except
while tracing.
- cqlengine: DateType.deserialize being called with one argument
vs two
- cqlengine: Querying without setting up connection now throws
AttributeError and not CQLEngineException
- cqlengine: BatchQuery multiple time executing execute statements.
- cqlengine: Better error for management functions when no connection
set
- cqlengine: Handle None values for UDT attributes in cqlengine
- cqlengine: Fix inserting None for model save
- cqlengine: EQ doesn't map to a QueryOperator (setup race condition)
- cqlengine: class.MultipleObjectsReturned has DoesNotExist as base
class
- cqlengine: Typo in cqlengine UserType __len__ breaks attribute
assignment
Other
- cqlengine: a major improvement on queryset has been introduced.
It is a lot more efficient to iterate large datasets: the rows
are now fetched on demand using the driver pagination.
- cqlengine: the queryset len() and count() behaviors have changed.
It now executes a "SELECT COUNT(*)" of the query rather than
returning the size of the internal result_cache (loaded rows).
On large queryset, you might want to avoid using them due to
the performance cost. Note that trying to access objects using
list index/slicing with negative indices also requires a count
to be executed.
|
|
|
|
pgpool-II is a middleware that works between PostgreSQL servers
and a PostgreSQL database client. It talks PostgreSQL's backend
and frontend protocol, and relays a connection between them.
|
|
v2.2.17 released 2016-03-07
* General compatibility with MySQL 5.7 tools, docs and test suite
* pt-mysql-summary displays incorrect info about Fast Server Restarts
for Percona Server 5.6
* pt-online-schema-change cannot set sql_mode using --set-vars
* pt-online-schema-change added --null-to-non-null option to allow
NULLable columns to be converted to NOT NULL
* pt-online-schema-change doesn't apply underscores to foreign
keys individually
* pt-online-schema Invalid recursion method: t=dsns
* pt-online-schema-change fails when using --no-drop-old-table
after 10 times
* pt-query-digest : Redundant argument in sprintf
* pt-query-digest doc bug with --since and too many colons
* pt-query-digest: Make documentation of --attribute-value-limit
option more clear
* pt-show-grants fails against MySQL-5.7.6
* pt-show-grants doesn't sort column-level privileges
* pt-slave-restart fails on MariaDB 10.0.13 (gtid_mode confusion)
* pt-stalk: new var binlog_error_action causes bug in collect module
* pt-table-checksum has high likelyhood to skip a table when row count
is around chunk-size * chunk-size-limit
* pt-table-checksum redundant argument in printf
v2.2.16 released 2015-11-09
* pt-archiver dies with "MySQL server has gone away" when
innodb_kill_idle_transaction set to low value and bulk
insert/delete process takes too long time
* pt-kill option --filter does not work
* pt-online-schema-change should reconnect to slaves
* pt-online-schema-change, MySQL 5.6, and InnoDB optimizer stats
can cause downtime
* pt-stalk find -warn option is not portable
* Document that pt-table-checksum has high likelihood to skip a table
when row count is around chunk-size * chunk-size-limit
v2.2.15 released 2015-08-28
* pt-archiver checked lag too frequently
* pt-archiver clarified function of --check-interval [DOC]
* pt-archiver now accepts checking lag on multiple slaves
* pt-archiver now checks for PXC flow control via --max-flow-ctl option
* pt-archiver options --no-delete and --purge were not mutually
exclusive
* pt-archiver mysql timed out when innodb_kill_idle_transaction set
to low value and check-slave-lag used
* pt-duplicate-key-checker doesn't support triple quote in column name
* pt-kill enable support for RDS
* pt-mysql-summary lacked an --ask-pass option
* pt-online-schema-change added --sleep option
* pt-online-schema-change core dump on erroneous alter directive
* pt-online-schema-change now checks for PXC flow control via
--max-flow-ctl option
* pt-online-schema-change unstable signal handling
* pt-online-schema-change now controls constraint name length
* pt-online-schema-change --chunk-size-limit=0 inhibited checksumming
of single nibble tables
* pt-sift failed when fetching missing tools
* pt-stalk monitors tokudb status
* pt-table-checksum doesn't reconnect to slaves when timed out
on very long lags
* passsword parameter must escape commas - all tools [DOC]
* changes needed to build packages from git tree
* write-user-docs script stopped working after switching to github
* testing bugs related to newer perl versions
|
|
7.4.10
- A serious regression was inadvertently introduced in MySQL Cluster NDB
7.4.8 whereby local checkpoints and thus restarts often took much longer
than expected.
See more at:
http://dev.mysql.com/doc/relnotes/mysql-cluster/7.4/en/mysql-cluster-news-7-4-10.html
7.4.9
- Important Change: Previously, the NDB scheduler always optimized for
speed against throughput in a predetermined manner (this was hard coded);
this balance can now be set using the SchedulerResponsiveness data node
configuration parameter.
- Added the tc_time_track_stats table to the ndbinfo information database.
- Cluster Replication: Normally, RESET SLAVE causes all entries to be
deleted from the mysql.ndb_apply_status table. This release adds
the ndb_clear_apply_status system variable, which makes it possible
to override this behavior.
See more at:
http://dev.mysql.com/doc/relnotes/mysql-cluster/7.4/en/mysql-cluster-news-7-4-9.html
7.4.8
- Changes have been made in the minimum values for a number of parameters
applying to data buffers for backups and LCPs. These parameters, listed
here, can no longer be set so as to make the system impossible to run:
- BackupDataBufferSize: minimum increased from 0 to 2M.
- BackupLogBufferSize: minimum increased from 0 to 2M.
- BackupWriteSize: minimum increased from 2K to 32K.
- BackupMaxWriteSize: minimum increased from 2K to 256K.
In addition, the BackupMemory data node parameter is now deprecated and
subject to removal in a future version of MySQL Cluster. Use
BackupDataBufferSize and BackupLogBufferSize instead.
- When a backup was unsuccessful due to insufficient resourcesa subsequent
retry worked only for those parts of the backup that worked in the same
thread, since delayed signals are only supported in the same thread.
Delayed signals are no longer sent to other threads in such cases.
- An instance of an internal list object used in searching for queued
scans was not actually destroyed before calls to functions that could
manipulate the base object used to create it.
- ACC scans were queued in the category of range scans, which could lead
to starting an ACC scan when DBACC had no free slots for scans. We fix
this by implementing a separate queue for ACC scans.
- Cluster Replication: Added the create_old_temporals server system
variable to compliment the system variables avoid_temporal_upgrade and
show_old_temporals introduced in MySQL 5.6.24 and available in MySQL
Cluster beginning with NDB 7.3.9 and NDB 7.4.6.
- When the --database option has not been specified for ndb_show_tables,
and no tables are found in the TEST_DB database, an appropriate warning
message is now issued.
- Bug fixes.
See more at
http://dev.mysql.com/doc/relnotes/mysql-cluster/7.4/en/mysql-cluster-news-7-4-8.html
|
|
3.7.0 (09/14/2015)
==================
Enhancements:
Feature request #521 Alias name in SQL History search dialog.
Upgraded to latest RSyntax version (2.5.6).
The new version has a clipboard history which is accessible
through ctrl shift v.
A little drawback of the new version is that background colors
are not supported in syntax styles.
Feature request #485 Execute multiple SQL statements on one
click without selection
The new feature executes all SQLs in the editor.
If there are multiple SQLs in the editor the statement
separator has to be used.
The feature is accessible through a new tool bar button,
tools popup and the alt shift ENTER key combination
Feature request #484 Query output preferences --> Allow table
and text output simultaneously
Note: SQL result output as table or editable table now
includes text output in an extra tab.
That's why there should be only few cases where
choosing text output in Session Properties makes sense
anymore.
Feature request #479 Add option for tab names to contain only
Alias name
The option can be found at menu File --> Global Preferences -->
Tab General --> Bottom of section Appearance
Feature request #487 Show AS label as column header (if present)
If a SQL result contains at least one column whose column name
is not equal to its column label a button is shown at the header
of the tab named "Result".
By this button one can toggle display between column names
and labels.
Note: To configure the default display see menu File ->
Global Preferences -> Tab Data Type Controls -> Top of panel.
WIKI table Plugin: Added support for JIRA/Confluence Markup Style
Thanks to Thomas Hackel for the merge request.
Feature request #501 Overview/Charts Tab: Distinct Counts
- Distinct counts for an Overview as a whole are now displayed
right next to the column name
- Distinct counts of Intervals are available as tool tips
as well as a new details window which is accessible through
the right mouse menu
Sybase dialect support when using jtds
Thanks to Sumit Agarwal for the merge request.
On Mac OS X the SQuirreL now uses the acorn icon instead of the
default java coffee cup icon.
Thanks to Martin W. Kirst for the merge request.
New command line parameter:
Short form: -detectEDT
Long form: --detect-long-running-swing-edt-events
The parameter has no arguments.
The parameter enables SQuirreL to detect long running Swing
Event Dispatch Thread events.
When the dispatch thread is blocked for longer than two seconds
a warning containing a thread dump is written to the logs.
Upgraded to the latest RSyntax version (2.5.3).
Syntax Plugin: Made background color for white spaces affect
the whole SQL editors background, see menu File --> New Session
Properties --> tab Syntax
Note: If you combine this feature with the Metal-Charcoal Look
and Feel you can make SQuirreL appear in "fashionable" black.
Thanks to Duane Redfern for the patch.
When adjusting table column widths a maximum width may now be
defined.
See menu File --> Global Preferences --> Tab General -->
right column
Speeded up reading and writing Alias properties. As result
opening and closing a connections will be much faster for big,
complicated databases.
Thanks to Jaroslaw Jarmolowicz for the patch
Starting and stopping SQuirreL is much faster for big,
complicated databases
Thanks to Jaroslaw Jarmolowicz for the patch
Postgres Plugin:
- For postgres query plans explain was used which is less
accurate than explain analyze so it was changed to use it
instead.
- Previous implementation had limitation of producing query
plans only for SELECT queries. It was changed so query plan can
work for every type of query.
- Query plan executions are wrapped in transaction so they don't
change database state.
Thanks to Jaroslaw Jarmolowicz for the patch
Bug fixes.
|
|
|
|
GA 1.1.7 -
- Add JSON support
- Allow building without server flags (Bug#21391025)
- Correct relative() not seeking after changing position.(Bug#21152054)
|