Version 3.2.7 (2014-02-13)
--------------------------
### Fixed
Fix another weakness in the `Input` class and further harden the `deserialize()`
function. Thanks to Martin Auswöger for his input.
Version 2.11.16 (2014-02-13)
----------------------------
### Fixed
Fix another weakness in the `Input` class and further harden the `deserialize()`
function. Thanks to Martin Auswöger for his input.
- many new opcodes
- many opcodes have fixes
- a few new API functions (now at 2.1)
- general bug fixes
- support for MusicXML v2 files
- new parser
port-forward most of the netbsd/dfbsd changes. some are obsolete now.
Functionality Added or Changed
* InnoDB: New global configuration parameters, innodb_status_output and innodb_status_output_locks, allow you to dynamically enable and disable the standard InnoDB Monitor and InnoDB Lock Monitor for periodic output. Enabling and disabling monitors for periodic output by creating and dropping specially named tables is deprecated and may be removed in a future release.
* Previously, ALTER TABLE in MySQL 5.6 could alter a table such that the result had temporal columns in both 5.5 and 5.6 format. Now ALTER TABLE upgrades old temporal columns to 5.6 format for ADD COLUMN, CHANGE COLUMN, MODIFY COLUMN, ADD INDEX, and FORCE operations. This conversion cannot be done using the INPLACE algorithm, so specifying ALGORITHM=INPLACE in these cases results in an error.
* CMake now supports a -DTMPDIR=dir_name option to specify the default tmpdir value. If unspecified, the value defaults to P_tmpdir in <stdio.h>.
Bugs Fixed
* InnoDB; Replication: Using the InnoDB memcached plugin (see InnoDB Integration with memcached) with innodb_api_enable_binlog set to 1 caused the server to leak memory.
* InnoDB: A boolean mode full-text search query would result in a memory access violation during parsing.
* InnoDB: When new indexes are added by an ALTER TABLE operation, instead of only saving table-level statistics and statistics for the new indexes, InnoDB would save statistics for the entire table, including the table's other indexes. This behavior slowed ALTER TABLE performance.
* InnoDB: Due to a parser error, full-text search queries that include a sub-expression could return the wrong result.
* InnoDB: The innochecksum tool did not use a Windows-specific API to retrieve file size information, which resulted in an incorrect error message (Error: ibdata1 cannot be found) when the MySQL 5.6 innochecksum 2GB file size limit was exceeded. innochecksum now provides support for files larger than 2GB in both MySQL 5.6 and MySQL 5.7.
* InnoDB: Due to a regression introduced by the fix for Bug17371537, memory was not allocated for the default memcached engine when using the default memcached engine as the backstore for data instead of InnoDB.
* InnoDB: InnoDB would report an incorrect operating system error code after failing to initialize.
* InnoDB: Manipulating a table after discarding its tablespace using ALTER TABLE ... DISCARD TABLESPACE could result in a serious error.
* InnoDB: Persistent optimizer statistics would cause stalls due to latch contention.
* InnoDB: MATCH() ... AGAINST queries that use a long string as an argument for AGAINST() could result in an error when run on an InnoDB table with a full-text search index.
* InnoDB: An InnoDB full-text search failure would occur due to an “unended” token. The string and string length should be passed for string comparison.
* InnoDB: In debug builds, a merge insert buffer during a page read would cause a memory access violation.
* InnoDB: Truncating a memcached InnoDB table while memcached is performing DML operations would result in a serious error.
* InnoDB: In sync0rw.ic, rw_lock_x_lock_func_nowait would needlessly call os_thread_get_curr_id.
* InnoDB: Attempting to rename a table to a missing database would result in a serious error.
more...
Fix a bug (ticket 4c86b126f2) that causes rows to go missing on some queries with OR clauses and IS NOT NULL operators in the WHERE clause, when the SQLITE_ENABLE_STAT3 or SQLITE_ENABLE_STAT4 compile-time options are used.
Fix a harmless compiler warning that was causing problems for VS2013.
Acora is 'fgrep' for Python, a fast multi-keyword text search engine.
Based on a set of keywords, it generates a search automaton (DFA) and runs it
over string input, either unicode or bytes.
It is based on the Aho-Corasick algorithm and an NFA-to-DFA powerset
construction.
Acora comes with both a pure Python implementation and a fast binary module
written in Cython. However, note that the current construction algorithm is not
suitable for really large sets of keywords (i.e. more than a couple of
thousand).
1.) OpenSSL 0.9.8* doesn't support TLS 1.2, Elliptic curve cryptography
and other modern TLS features.
2.) Supporting OpenSSL 0.9.8* causes extra maintenance overhead.
As a result NetBSD 5.*, all versions of Mac OS X and possibly other
platforms will now use OpenSSL from "pkgsrc".
Overview of Changes in GTK+ 3.10.6 to 3.10.7
============================================
* Bugs fixed:
386569 GtkFileChooser enters first file name into the entry...
709491 dark theme setting not propagated to vertical spinbu...
711298 "Edit Scheduled Transaction" window way too modal
719314 gdk_property_change segfault on multiple X protocol...
719970 Fails to build: gdkevents-quartz.c:1692:58: error: ...
719977 Can not use GtkFileChooserDialog: assertion failure
721700 invalid callback prototypes leads to test issues
win32: add more width to the slider to not cut it w...
win32: add margin to scale trough
win32: set color for scale marks
win32: scale slider with marks was off by 2 pixels
win32: handle again gtk-font-name
* Translation updates:
Czech
German
Greek
Hungarian
Punjabi
Russian
Simplified Chinese
Slovenian
Changes:
Addressed 31 bugs in 3.8, including various fixes and improvements for the new
dashboard design and new themes admin screen.
More info at http://codex.wordpress.org/Version_3.8.1
otherwise it has no effect
-in buildlink3.mk, also add PYTHON_VERSIONS_INCOMPATIBLE to avoid
picking up the default Python version (XXX we need a way to express
major version restrictions, otherwise this doesn't scale)
should not keep a runtime dependency on a specific Python version.
Make Python a build-time dependency for py-gobject3-common (not really
needed, just to satisfy the "configure" script) and move some
dependencies into py-gobject3/Makefile
Release 0.1.11 (Feb 07, 2014)
-----------------------------
Bug Fixes
* Fix incorrect parsing of string literals containing line breaks (issue118).
* Fix typo in keywords, add MERGE, COLLECT keywords (issue122/124,
by Cristian Orellana).
* Improve parsing of string literals in columns.
* Fix parsing and formatting of statements containing EXCEPT keyword.
* Fix Function.get_parameters() (issue126/127, by spigwitmer).
Enhancements
* Classify DML keywords (issue116, by Victor Hahn).
* Add missing FOREACH keyword.
* Grouping of BEGIN/END blocks.
Other
* Python 2.5 isn't automatically tested anymore, neither Travis nor Tox
still support it out of the box.
---
2.2
---
* Issue #141: Restored fix for allowing setup_requires dependencies to
override installed dependencies during setup.
* Issue #128: Fixed issue where only the first dependency link was honored
in a distribution where multiple dependency links were supplied.
