UPGRADE URGENCY: HIGH because of the following two issues:
* Lua scripting + Replication + AOF in slaves problem (see Issue 1164).
* AOF + expires possible race condition (see Issue 1079).
* [FIX] AOF bug: expire could be removed from key on AOF rewrite.
* [FIX] Allow writes from scripts called by AOF loading in read-only slaves.
* [FIX] Sentinel: parse new verison of INFO replication output correctly.
* [NEW] Reset masterauth if an empty string is configured.
Functionality Added or Changed
* comp_err now checks to make sure that new errors are not being added to MySQL 5.1 or 5.5 because the set of errors for these series is frozen.
Bugs Fixed
* InnoDB: During an insert buffer merge, InnoDB would invoke lock_rec_restore_from_page_infimum() on a potentially invalid record pointer.
* InnoDB: The page_zip_validate() consistency check would fail after compressing a page, in page_zip_compress(). This problem was caused by page_zip_decompress(), which would fail to set heap_no correctly when a record contained no user data bytes. A record with no user data bytes occurs when, for example, a primary key is an empty string and all secondary index fields are NULL or an empty string.
* InnoDB: The pthread_mutex, commit_threads_m, which was initialized but never used, has been removed from the code base.
* Partitioning: When dropping a partitioned table, the table's .par file was deleted first, before the table definition or data. This meant that, if the server failed during the drop operation, the table could be left in an inconsistent state in which it could neither be accessed nor dropped.
* Shared-compatibility conflict errors occurred for RPM install operations, even if no shared-compatibility RPMs were already installed.
* A user variable referenced during execution of a prepared statement is set to memory that is freed at the end of execution. A second execution of the statement could result in Valgrind warnings when accessing this memory.
* Misoptimization of left expressions in prepared statements could cause a server exit.
* Subsequent to Prepared statement needs to be re-prepared errors, inserts into DECIMAL columns caused a server exit.
* Assigning the result of a subquery to a user variable raised an assertion when the outer query included DISTINCT and GROUP BY.
* Previously, program options could be specified in full or as any unambiguous prefix. For example, the --compress option could be given to mysqldump as --compr, but not as --comp because the latter is ambiguous. Option prefixes now are deprecated. They can cause problems when new options are implemented for programs. A prefix that is currently unambiguous might become ambiguous in the future. If an unambiguous prefix is given, a warning now occurs to provide feedback. For example:
Warning: Using unique option prefix compr instead of compress is
deprecated and will be removed in a future release. Please use the
full name instead.
Option prefixes are no longer supported in MySQL 5.7; only full options are accepted.
* comp_err now checks to make sure that new errors are not being added to MySQL 5.1 or 5.5 because the set of errors for these series is frozen.
* Bugs Fixed
* Important Change; Replication: By default, when promoting integers from a smaller type on the master to a larger type on the slave (for example, from a SMALLINT column on the master to a BIGINT column on the slave), the promoted values are treated as though they are signed. Now in such cases it is possible to modify or override this behavior using one or both of ALL_SIGNED, ALL_UNSIGNED in the set of values specified for the slave_type_conversions server system variable. For more information, see Row-based replication: attribute promotion and demotion, as well as the description of the variable.
* Previously, program options could be specified in full or as any unambiguous prefix. For example, the --compress option could be given to mysqldump as --compr, but not as --comp because the latter is ambiguous. Option prefixes now are deprecated. They can cause problems when new options are implemented for programs. A prefix that is currently unambiguous might become ambiguous in the future. If an unambiguous prefix is given, a warning now occurs to provide feedback. For example:
Warning: Using unique option prefix compr instead of compress is
deprecated and will be removed in a future release. Please use the
full name instead.
Option prefixes are no longer supported in MySQL 5.7; only full options are accepted.
* The C API libmysqlclient shared-library .so files now have version 18.1.0 (up from version 18.0.0 used in MySQL 5.5).
* In batch mode, mysql formatted result status messages such as “"Query OK, 1 row affected"” but did not print them. Now these messages are not formatted.
* Bugs Fixed
- [security] Fix self-XSS in "Showing rows", see PMASA-2013-8
- [security] Fix self-XSS in Display chart, see PMASA-2013-9
- [security] Fix stored XSS in Server status monitor, see PMASA-2013-9
- [security] Fix stored XSS in navigation panel logo link, see PMASA-2013-9
- [security] Fix self-XSS in setup, trusted proxies validation, see PMASA-2013-9
+ [security] JSON content type header for version_check.php, see PMASA-2013-9
+ [security] Backport fix for jQuery issue #9521 from jQuery 1.6.3, see PMASA-2013-9
+ [security] Fix full path disclosure, see PMASA-2013-12
+ [security] Fix control user SQL injection in pmd_pdf.php, see PMASA-2013-15
+ [security] Fix control user SQL injection in schema_export.php, see PMASA-2013-15
- [security] Fix self-XSS in schema export, see PMASA-2013-14
- [security] Fix unencoded json object, see PMASA-2013-11
tarballs with the same name, as found by obache@ in:
http://bugs.mysql.com/bug.php?id=69598
adam@ already fixed version 5.5, so this should complete the fix
for PR pkg/48056. (Also replaced the 5.6 tarball on ftp.netbsd.org)
The list of bug fixes is available in the CHANGELOG.
The following are the recent Changes
------------------------------------
Date Dev Ver Change details
---------- --- ------ --------------
2012-12-03 DP 1.16.1 Prevent a crash that could happen if further changes
were made on a dialogue after using the Apply button.
[Akshay Joshi]
2012-11-29 GL 1.16.1 Save new comments on already existing columns when
editing a table. Per a report from Jeff Janes.
2012-11-29 GL 1.16.1 Fix the query editor behaviour when executing COPY TO
stdout and COPY FROM stdin [Heikki Linnakangas]
2012-11-28 AV 1.16.1 Date picker controls returns a full timestamp by
default, which can cause inadvertent date changes
on jobs and role validty dates. Ignore the time part.
2012-11-26 MH 1.16.1 Fix query for database descriptions
2012-11-15 DP 1.16.1 Avoid querying the catalogs for toast table settings
for every table in the database. This gives a huge
performance gain with large schemas.
2012-11-08 DP 1.16.1 Prevent a crash when refreshing a node which has a
child with an open dialogue [Dhiraj Chawla]
2012-11-08 DP 1.16.1 Fix dropping/renaming of indexes [Akshay Joshi]
2012-11-08 DP 1.16.1 Avoid updating the GQB model on every key press in
the query tool [Dhiraj Chawla]
2012-11-02 DP 1.16.1 Fix a crash that can occur when renaming objects.
[Ashesh Vashi/Sachin Srivastava]
2012-11-01 DP 1.16.1 Fix dropping of constraints [Akshay Joshi]
2012-10-31 DP 1.16.1 Fix the "blocked by" column in the server status
dialogue on 9.2 servers [Sachin Srivastava]
2012-10-11 DP 1.16.1 Prevent a crash if the query tool is closed whilst a
file is loading [Akshay Joshi]
2012-10-09 AV 1.16.1 Fix setting of comments on PPAS procedures.
2012-10-08 DP 1.16.1 Don't autosize the search results columns if no
results are found [Akshay Joshi]
2012-10-08 AV 1.16.1 Prevent a crash if opening a second config file in
the editor.
2012-10-08 DP 1.16.1 Prevent the SSL options combo box displaying
duplicate options if the server dialogue is
reopened [Akshay Joshi]
2012-09-14 GL 1.16.1 Fix trigger query when connected to PostgreSQL 8.2 or
lower, per a report from Jon Roberts.
2012-09-12 GL 1.16.1 Fix message when executing an empty query, per Marc
Mamin.
are replaced with .include "../../devel/readline/buildlink3.mk", and
USE_GNU_READLINE are removed,
* .include "../../devel/readline/buildlink3.mk" without USE_GNU_READLINE
are replaced with .include "../../mk/readline.buildlink3.mk".
copy isn't as portable as what's in databases/sqlite3. Instead of
trying to fix the copy, declare a buildlink dependency on 3.7.17,
and let pkgsrc figure out how to fulfill it. Bump PKGREVISION.
- OpenBSD doesn't like the previous _XOPEN_SOURCE hack (ISHIGAKI)
- Disabled a unicode-related test for older perls (ISHIGAKI)
- Tentatively defined _XOPEN_SOURCE under *BSD systems to see
if it solves a compilation issue for threaded perls (ISHIGAKI)
- As of SQLite 3.7.15, SQLite's query optimizer was enhanced
and the result order of a SELECT statement without an ORDER
BY clause may be different from the one of the previous
versions. If your applications or tests mistakenly depend
on the arbitrary output order, they may be broken with this
enhancement.
- Updated to SQLite 3.7.17 (ISHIGAKI)
- Fixed tests that mistakenly made invalid assumptions about
the result order (ISHIGAKI)
- Added a brief note on useful pragmata. (ISHIGAKI)
- Resolved#85302: type fixes (ISHIGAKI)
- Updated to SQLite 3.7.16.1 (ISHIGAKI)
- Removed two obsolete pragma calls at login time (ISHIGAKI)
- Resolved#80344: Set SQLITE_DISABLE_DIRSYNC on AIX (suggested
by Steve Barnsley) (ISHIGAKI)
- Resolved#81536: primary_key_info returns the wrong KEY_SEQ
(VLYON)
- Resolved#84027: Finalizer() not called in (D. Richard Hipp)
- Resolved#84372: -Wpointer-sign warnings with utf8_hop
(RURBAN)
- Resolved#84373: Add test for RT #26775 "name)" key with
DISTINCT (RURBAN/ISHIGAKI)
- Resolved#70815: DBD::SQLite 1.33 build is broken under
Solaris using Sun C (RURBAN)
- Resolved#84380: Fix WINLIKE for mingw/msys (RURBAN)
- Added a note on DBD::SQLite and File::Temp (suggested by
TOKUHIROM) (ISHIGAKI)
- Resolved#56444: immediate transaction should be on by
default, and the doc be updated.
If you really need the deferred transaction (which had long
been the default), set sqlite_use_immediate_transaction
to false explicitly. (ISHIGAKI)
- Updated to SQLite 3.7.14 (ISHIGAKI)
- Added support for foreign_key_info (DAMI/ISHIGAKI)
- Added several methods to retrieve internal information such as
table_column_metadata/db_filename/*_status (ISHIGAKI/VOVKASM)
- Added sqlite_load_extension so that extensions can add
functions internally (ISHIGAKI)
- Resolved#77617: atoll () sometimes just is atol () (GAAS)
- Resolved#48084: improper "require utf8" in tests (ISHIGAKI)
- Resolved#77724: bug in primary_key_info with regard to column
names containing whitespace (ISHIGAKI)
- Resolved#79364: variance example of the doc (ISHIGAKI)
- Resolved#78833: utf8 flag for column names (JAMADAM)
(This hopefully resolved#72418 as well)
- Resolved#64177: ping() wipes out the errstr (ISHIGAKI)
- Resolved#79576: (patch) bind_param don't work with PADTMP
scalars (VOVKASM)
- Refactored primary_key_info to support attached databases
(ISHIGAKI)
* make realclean: removing all files
RT #68214
* Documented the issue where the error below
BDB0588 At least one secondary cursor must be specified to DB->join
* DB_File installs to wrong place for CPAN version
RT #70420
Makefile.PL prevents INSTALLDIRS on command line.
RT #68287: Makefile.PL prevents INSTALLDIRS on command line.
* typo fix
RT #85335
* Minor change to build with Berkeley DB 6.x
Class::DBI::BaseDSN acts as a placeholder for a base class which will be
switched for a specific Class::DBI extension when you specify the dsn of the
database to connect to. For example in this case, the Class::DBI::BaseDSN will
replace itself with Class::DBI::mysql when the set_db call is executed.
SOCI is a database access libary for C++. It provides a natural
interface with extensive STL integration. A number of major database
servers are accessable.
Lua-Sqlite3 is unique in contrast to other database bindings that it consists
of two layers. The first layer translates the SQLite 3 implementation's C API
to Lua. The first layer is called the backend. The second layers are frontend
layers, written in Lua. These layers provide a nice and smart view of the
database
Currently, Lua-Sqlite3 implements two frontends:
* A specialiced frontend which provides all sqlite3 capabilities.
* A LuaSQL compatible frontend as used on the Kepler Project.
What's new in psycopg 2.5.1
---------------------------
- Fixed build on Solaris 10 and 11 where the round() function is already
declared (🎫`#146`).
- Fixed comparison of `Range` with non-range objects (🎫`#164`).
Thanks to Chris Withers for the patch.
- Fixed double-free on connection dealloc (🎫`#166`). Thanks to
Gangadharan S.A. for the report and fix suggestion.
databases/p5-DBIx-Class-InflateColumn-IP from 0.02001nb5 to 0.02003.
pkgsrc changes:
- add license conditions
Upstream changes:
0.02003 Fri Nov 2 11:52:11 GMT 2012
- Perl 5.8.1 is now required (as it is for DBIC itelf).
- Use and declare UTF-8 encoding in POD
- Add repository metadata
0.02002
- Use numeric format for bigint columns.
- Use bigint column in test to cope with DBD::SQLite bind type changes.
databases/p5-DBIx-Class-Fixtures from 1.001013nb3 to 1.001018.
pkgsrc changes:
- adjust dependencies
Upstream changes:
1.001018
- Reduced the size of a PK in the fixtures to stop (hopefully) some occasional
error reports
1.001017
- POD fixes (justin hunter++)
- Changed the test suite so it doesn't mindlessly break with the changes
introduced by DBIC 0.08200 (nerox++ for bug report).
1.001016
- Support more Postgresql types for datetime_relative (added TIME, DATE,
INTERVAL, TIMESTAMP)
- If $result_source->column_info defines a sequence, make sure we properly
set that sequence to whatever the max value currently is.
1.001015
- ::External::File makes the path if its missing
1.001014
- Allow you to perform value substitutions inside config-sets
- Added a framework to allow you to backup / restore data external to the
database as part of your fixtures. Added an external handler for File
based data, and docs and tests for this.
0.01007 into databases/p5-DBIx-Class-InflateColumn-FS.
Provides inflation to a Path::Class::File object allowing file system
storage of BLOBS.
The storage path is specified with fs_column_path. Each file receives
a unique name, so the storage for all FS columns can share the same path.
Within the path specified by fs_column_path, files are stored in
sub-directories based on the first 2 characters of the unique file names.
Up to 256 sub-directories will be created, as needed. Override
_fs_column_dirs in a derived class to change this behavior.
fs_new_on_update will create a new file name if the file has been updated.
databases/p5-DBIx-Class-DynamicDefault from 0.03nb5 to 0.04.
pkgsrc changes:
- add license conditions
- adjust dependencies
Upstream changes:
0.04 Sat, 14 Apr 2012 10:09:00 +0100
Matt S Trout:
Fix a massive pessimisation causing repeated ->result_source_instance
invocations resulting in get_inherited from C::A::Grouped being the
biggest thing in a startup profile.
databases/p5-Dancer-Plugin-DBIC from 0.1601nb1 to 0.1802.
Upstream changes (since 1.1601):
0.1802 2013-01-22
Updated version requirement for Dancer. A newer Dancer is required to
use the plugin_args() function.
0.1801 2013-01-21
Fixed tests to pass on Dancer 2.
Thanks Yanick Champoux (https://github.com/yanick)!
0.1800 2013-01-18
Added the resultset and rset keywords.
0.1700 2013-01-01
Added support for Dancer 2.
Thanks Steven Humphrey (https://github.com/shumphrey)!
databases/p5-SQL-Abstract from 1.73nb2 to 1.74.
Upstream changes:
revision 1.74 2013-06-04
----------------------------
- Fix insufficient parenthesis unroll during operator comparison
- 'ORDER BY foo' and 'ORDER BY foo ASC' are now considered equal
by default (with a switch to reenable old behavior when necessary)
- Change parser to not eagerly slurp RHS expressions it doesn't recognize
databases/p5-DBIx-Class-Schema-Loader from 0.07033nb2 to 0.07035.
pkgsrc changes:
- adjust dependencies
Upstream changes:
0.07035 2013-02-26
- Release 0.07034_01 with a stable version number. 0.07034 is
skipped due to the improper dev release versioning.
0.07034_01 2013-01-21
- Fix fixture generation helper to work with older DBD::SQLite versions
0.07034_01 2013-01-16
- MSSQL: on > 2000 use schema_name() instead of user_name() to detect
current schema and query sys.schemas instead of sysusers.
- SQL Anywhere: introspect ON DELETE/UPDATE rules, default is now
RESTRICT. is_deferrable still defaults to 1
- rewrite pg fk introspection to use catalog views instead of
information_schema as information_schema does not work for readonly
users
- add rel_type param for relationship_attrs coderef
- pass link table details to rel_name_map for many_to_many bridges
(RT#81091)
implementation of an SQL engine.
pkgsrc changes:
- killing DBI build dependency - was an error introduced by the author
for better test coverage, leads easily to circular dependency, bad stuff
==> kicking
- since 5.10.1 a suitable test framework is distributed with Perl5 core
==> no reason to mention it explicitely
- Bumping conflict DBI version to 1.622 (with 1.623 DBI::DBD::SqlEngine
received great improve - and forces a lot of fixes in SQL::Statement
and vice versa)
Upstream changes since 1.402:
Version 1.405, released June 17, 2013
-------------------------------------------------
[Bug fixes]
* INSERT now expands incomplete rows (Thanks to H.Merijn Brand)
Version 1.404, released May 23, 2013
-------------------------------------------------
[Bug fixes]
* re-enable cleanup test_output* after test done
* recommend Text::Soundex and do soundex-test only when have it,
because it's going to be removed from core for Perl 5.19 (thank Merijn)
Version 1.403, released May 22, 2013
-------------------------------------------------
[Bug fixes]
* fix documentation (rt#84889 - thanks Xavier Guimard and Florian,
rt#85257 - thanks Andreas Koenig)
