=== 4.5.0 (2013-12-02)
* Support :on_commit=>(:drop|:delete_rows|:preserve_rows) options when creating temp tables on PostgreSQL (rosenfeld) (#737)
* Make Dataset#insert work on PostgreSQL if the table name is a SQL::PlaceholderLiteralString (jeremyevans) (#736)
* Copy unique constraints when emulating alter_table operations on SQLite (jeremyevans) (#735)
* Don't return clob column values as SQL::Blob instances in the db2 and ibmdb adapters unless use_clob_as_blob is true (jeremyevans)
* Make use_clob_as_blob false by default on DB2 (jeremyevans)
* Fix usage of Sequel::SQL::Blob objects as prepared statement arguments in jdbc/db2 adapter when use_clob_as_blob is false (jeremyevans)
* Add mssql_optimistic_locking plugin, using a timestamp/rowversion column to protect against concurrent updates (pinx, jeremyevans) (#731)
* Make Model.primary_key array immutable for composite keys (chanks) (#730)
=== 4.4.0 (2013-11-01)
* Make Database#tables not show tables in the recycle bin on Oracle (jeremyevans) (#728)
* Don't automatically order on all columns when emulating offsets for unordered datasets on DB2 (jeremyevans)
* Improve PostgreSQL type support in the jdbc/postgresql adapter (jeremyevans)
* Make offset emulation on Oracle work when using columns that can't be ordered (jeremyevans, sdeming) (#724, #725)
* Make filter by associations support handle associations with :conditions or block (jeremyevans)
* Make association cloning handle :block correctly for clones of clones (jeremyevans)
* Make association cloning handle :eager_block option correctly (jeremyevans)
* Make add_primary_key work on h2 (jeremyevans)
* Add support for foreign key parsing on Oracle (jeremyevans)
* Add support for foreign key parsing to the jdbc adapter (jeremyevans)
* Make add_foreign_key work on HSQLDB (jeremyevans)
* Add table_select plugin for selecting table.* instead of * for model datasets (jeremyevans)
* Issue constraint_validation table deletes before inserts, so modifying constraint via drop/add in same alter_table block works (jeremyevans)
* Support add_*/remove_*/remove_all_* pg_array_to_many association methods on unsaved model objects (jeremyevans)
* Add Sybase SQLAnywhere support via new sqlanywhere and jdbc/sqlanywhere adapters (gditrick, jeremyevans)
* Add Dataset#offset for setting the offset separately from the limit (Paul Henry, jeremyevans) (#717)
=== 4.3.0 (2013-10-02)
* Fix literalization of empty blobs on MySQL (jeremyevans) (#715)
* Ensure Dataset#page_count in pagination extension is at least one
(jeremyevans) (#714)
* Recognize another disconnect error in the jdbc/as400 adapter (jeremyevans)
* Make Dataset#qualify and Sequel.delay work together (jeremyevans)
* Recognize citext type as string on PostgreSQL (isc) (#710)
* Support composite keys in the rcte_tree plugin (jeremyevans)
* Support composite keys in the tree plugin (jeremyevans)
* Make Migrator.migrator_class public (robertjpayne, jeremyevans) (#708)
* Make PostgreSQL empty array literalization work correctly on PostgreSQL <8.4
(jeremyevans)
* Add Sequel extensions guide (jeremyevans)
* Add model plugins guide (jeremyevans)
* Add error_sql Database extension, allowing DatabaseError#sql to return SQL
query that caused underlying exception (jeremyevans)
* Make Dataset#each_page in pagination extension return enumerator if no block
is given (justinj) (#702)
== v0.17.0 [2013-09-15] Michael Granger <ged@FaerieMUD.org>
Bugfixes:
- Fix crash by calling PQsend* and PQisBusy without GVL (#171).
Enhancements:
- Add method PG::Connection#copy_data.
- Add a Gemfile to allow installation of dependencies with bundler.
- Add compatibility with rake-compiler-dev-box.
- Return self from PG::Result#check instead of nil. This allows
to stack method calls.
Changed the defined behavior for the CAST expression when floating point values greater than +9223372036854775807 are cast into into integers so that the result is the largest possible integer, +9223372036854775807, instead of the smallest possible integer, -9223372036854775808. After this change, CAST(9223372036854775809.0 as INT) yields +9223372036854775807 instead of -9223372036854775808. ← Potentially Incompatible Change!
Added support for WITHOUT ROWID tables.
Added the skip-scan optimization to the query planner.
Extended the virtual table interface, and in particular the sqlite3_index_info object to allow a virtual table to report its estimate on the number of rows that will be returned by a query.
Update the R-Tree extension to make use of the enhanced virtual table interface.
Add the SQLITE_ENABLE_EXPLAIN_COMMENTS compile-time option.
Enhanced the comments that are inserted into EXPLAIN output when the SQLITE_ENABLE_EXPLAIN_COMMENTS compile-time option is enabled.
Performance enhancements in the VDBE, especially to the OP_Column opcode.
Factor constant subexpressions in inner loops out to the initialization code in prepared statements.
Enhanced the ".explain" output formatting of the command-line shell so that loops are indented to better show the structure of the program.
Enhanced the ".timer" feature of the command-line shell so that it shows wall-clock time in addition to system and user times.
fixed since version 4.0.9:
- bug #4150 Clicking database name in query window opens a new tab
- bug #4141 Wrong page is shown after editing; also, do not show a modal
dialog for multi-row edit
- bug #3939 PHP NavigationTree error when paging through list
- bug #4075 Support A10 Networks load balancer
- bug #4083 row deleting isn't binlogs friendly
- bug #4163 Setup script does not recognize manually-configured server
- bug #4158 Events page says no privileges with ALL PRIVILEGES
FoxPro, Clipper, xBase) files. It can also be used to create DBF files and
populate them from your data. It is written for the Linux/Unix environment,
but relies only on standard C libraries and functions.
* Previously, MySQL Server distributions included the MySQL Reference Manual in Info format (the Docs/mysql.info file). Because the license for the manual restricts redistribution, its inclusion in Community packages caused problems for downstream redistributors, such as those who create Linux distributions. Community distributions of MySQL Server no longer include the mysql.info file, to make the repackaging and redistribution process easier (for example, the source tarball and its checksum can be used directly). This change applies to all source and binary Community packaging formats. Commercial (Enterprise) distributions are unchanged.
* Incompatible Change: Several statement instruments in the setup_instruments table are used by the Performance Schema during the early stages of statement classification before the exact statement type is known.
* The Performance Schema now instruments the read/write lock Delegate::lock
* A new CMake option, WITH_ASAN, permits enabling address sanitization for compilers that support it.
* The hash function used for metadata locking was modified to reduce overhead.
* Bugs Fixed
* Previously, MySQL Server distributions included the MySQL Reference Manual in Info format (the Docs/mysql.info file). Because the license for the manual restricts redistribution, its inclusion in Community packages caused problems for downstream redistributors, such as those who create Linux distributions. Community distributions of MySQL Server no longer include the mysql.info file, to make the repackaging and redistribution process easier (for example, the source tarball and its checksum can be used directly). This change applies to all source and binary Community packaging formats. Commercial (Enterprise) distributions are unchanged.
* A new CMake option, WITH_ASAN, permits enabling address sanitization for compilers that support it.
* Attempts to use the thread_concurrency system variable (which has an effect only for Solaris 8 and earlier) now indicate that it has no effect when that is the case.
* Bugs Fixed
I have no idea why the extended regexp does not catch the unsetenv declaration
but the check is redundant anyway (there is another unsetenv check below in
configure) so I don't care that much.
The build does not create all those unnecessary shlib symlinks on MirBSD
(I believe this is due to a patch I sent in years ago), so add separate
PLIST.MirBSD files that do not contain these files.
(BTW, I would be grateful to learn how I can achieve the same effect
without copying PLISTs, but this works.)
Fixed liblmdb nordahead flag
Fixed liblmdb to check cursor index before cursor_del
Fixed liblmdb wasted space on split
Fixed slapd for certs with a NULL issuerDN
Fixed slapd cn=config with empty nested includes
Fixed slapd syncrepl memory leak with delta-sync MMR
Fixed slapd-bdb/hdb to stop processing on dn not found
Fixed slapd-bdb/hdb with indexed ANDed filters
Fixed slapd-mdb to stop processing on dn not found
Fixed slapd-mdb dangling reader
Fixed slapd-mdb matching rule for OlcDbEnvFlags
Fixed slapd-mdb with indexed ANDed filters
Fixed slapd-meta from blocking other threads
Fixed slapo-syncprov assert with findbase
The following bugs were fixed since the release of version 4.0.8:
- bug #4104 Can't edit updatable view when searching
- bug #4108 Missing refresh by deleting databases
- bug #3995 Drizzle server charset notice
- bug #3911 Filtering database names includes empty groupings
- bug #3678 Does not display or manipulate bit(64) fields appropriately
- bug #4129 Unneeded navi panel refresh
- bug #4120 SSL redirects to port 80
- bug #4144 DROP DATABASE displays wrong database name
- bug #4059 Running delete query asks for confirmation but says it was
already executed
- bug #4147 Accessibility: Images without Alt nor title attribute
Release 0.1.10 (Nov 02, 2013)
-----------------------------
Bug Fixes
* Removed buffered reading again, it obviously causes wrong parsing in some rare
cases (issue114).
* Fix regression in setup.py introduced 10 months ago (issue115).
Enhancements
* Improved support for JOINs, by Alexander Beedie.
Upstream changes:
Fixed err for new drh to be undef not to 0 [Martin J. Evans]
Fixed RT#83132 - moved DBIstcf* constants to util
export tag [Martin J. Evans]
PrintWarn is now triggered by warnings recorded in methods like STORE
that don't clear err RT#89015 [Tim Bunce]
Changed tracing to no longer show quote and quote_identifier calls
at trace level 1.
Changed DBD::Gofer ping while disconnected set_err from warn to info.
Clarified wording of log message when err is cleared.
Changed bootstrap to use $XS_VERSION RT#89618 [Andreas Koenig]
Added connect_cached.connected Callback P R # 3 [David E. Wheeler]
Clarified effect of refs in connect_cached attributes [David E. Wheeler]
Extended ReadOnly attribute docs for when the driver cannot
ensure read only [Martin J. Evans]
Corrected SQL_BIGINT docs to say ODBC value is used P R # 5 [ilmari]
Added liblmdb nordahead environment flag
Fixed client tools CLDAP with IPv6
Fixed libldap CLDAP with IPv6
Fixed libldap lock ordering with abandon op
Fixed liblmdb segfault with mdb_cursor_del
Fixed liblmdb when converting to writemap
Fixed liblmdb assert on MDB_NEXT with delete
Fixed liblmdb wasted space on split
Fixed slapd cn=config with olcTLSProtocolMin
Fixed slapd-bdb/hdb optimize index updates
Fixed slapd-ldap chaining with cn=config
Fixed slapd-ldap chaning with controls
Fixed slapd-mdb optimize index updates
Fixed slapd-meta chaining with cn=config
Fixed slapo-constraint to no-op on nonexistent entries
Fixed slapo-dds assert on startup
Fixed slapo-memberof to not replicate internal ops
Fixed slapo-refint to not replicate internal ops
Build Environment
Fixed slapd-mdb ptr arithmetic on void *s
Documentation
ldapsearch(1) minor typo fix
slapd-passwd(5) minor typo fix
Changes since 1.4.46:
* tcadb.cc (tcadbmisc): compilation warnings ware supressed.
* tchdb.cc (tchdbfbpmerge): size checking was added.
* tcbdb.cc (tcbdbrangeimpl): a bug of dead locking was fixed.
6.0.0:
* Support Berkeley DB 6.0.x.
* HEADS UP: If you are using "bsddb3._bsddb" in your code,
for example for exceptions, change it to "bsddb3._db".
* Print test working directory when running the testsuite.
You can control it using "TMPDIR" environment variable.
Defaults to "/tmp/z-Berkeley_DB/".
* Support for "DB_EVENT_REP_AUTOTAKEOVER_FAILED" event.
* Support for "DB_REPMGR_ISVIEW", "DB_DBT_BLOB", "DB_LOG_BLOB",
"DB_STREAM_READ", "DB_STREAM_WRITE" and "DB_STREAM_SYNC_WRITE" flags.
* Some DB_SEQUENCE function signatures changed in Berkeley DB 6.0.x.
* Erratic behaviour of "DBEnv->rep_elect()" because a typo.
* The testsuite prints Python bitness (32/64).
* Tests compatible with hash randomization, default
in Python 3.3. See http://bugs.python.org/issue13703 .
* Errors when trying to calculate the length of a DB were
masked, and an unuseful and unrelated exception was raised.
* Code cleanup since pybsddb is not in the Python 3.x stdlib
anymore, and the version in Python 2.6/2.7 is being
maintained separately.
* Improvements to documentation generation.
Release 0.1.9 (Sep 28, 2013)
----------------------------
Bug Fixes
* Fix an regression introduced in 0.1.5 where sqlparse didn't properly
distinguished between single and double quoted strings when tagging
identifier (issue111).
Enhancements
* New option to truncate long string literals when formatting.
* Scientific numbers are pares correctly (issue107).
* Support for arithmetic expressions (issue109, issue106; by prudhvi).
Added the unlikely() and likelihood() SQL functions to be used as hints to the query planner.
Enhancements to the query planner:
Take into account the fact WHERE clause terms that cannot be used with indices still probably reduce the number of output rows.
Estimate the sizes of table and index rows and use the smallest applicable B-Tree for full scans and "count(*)" operations.
Added the soft_heap_limit pragma.
Added support for SQLITE_ENABLE_STAT4
Added support for "sz=NNN" parameters at the end of sqlite_stat1.stat fields used to specify the average length in bytes for table and index rows.
Avoid running foreign-key constraint checks on an UPDATE if none of the modified columns are associated with foreign keys.
Added the SQLITE_MINIMUM_FILE_DESCRIPTOR compile-time option
Added the win32-longpath VFS on windows, permitting filenames up to 32K characters in length.
The Date And Time Functions are enhanced so that the current time (ex: julianday('now')) is always the same for multiple function invocations within the same sqlite3_step() call.
Add the "totype.c" extension, implementing the tointeger() and toreal() SQL functions.
FTS4 queries are better able to make use of docid<$limit constraints to limit the amount of I/O required.
Added the hidden fts4aux languageid column to the fts4aux virtual table.
The VACUUM command packs the database about 1% tighter.
The sqlite3_analyzer utility program is updated to provide better descriptions and to compute a more accurate estimate for "Non-sequential pages"
Refactor the implementation of PRAGMA statements to improve parsing performance.
The directory used to hold temporary files on unix can now be set using the SQLITE_TMPDIR environment variable, which takes precedence over the TMPDIR environment variable. The sqlite3_temp_directory global variable still has higher precedence than both environment variables, however.
Added the PRAGMA stats statement.
Bug fix: Return the correct answer for "SELECT count(*) FROM table" even if there is a partial index on the table.
## Rails 3.2.15 (Oct 16, 2013) ##
* When calling the method .find_or_initialize_by_* from a collection_proxy it
should set the inverse_of relation even when the entry was found on the db.
*arthurnn*
* Callbacks on has_many should access the in memory parent if a inverse_of is
set.
*arthurnn*
* Fix `FinderMethods#last` unscoped primary key.
Fixes#11917.
*Eugene Kalenkovich*
* Load fixtures from linked folders.
*Kassio Borges*
* When using optimistic locking, `update` was not passing the column to
`quote_value` to allow the connection adapter to properly determine how to
quote the value. This was affecting certain databases that use specific
colmn types.
Fixes: #6763
*Alfred Wong*
pax -rw, the destination directory must exist. pax in NetBSD creates it if
not, pax in MirBSD complains. I read through all pkgsrc Makefiles that use
pax and added an entry to INSTALLATION_DIRS, or an INSTALL_DATA_DIR
invocation.
I did not test all the changes but they should be fairly safe. If you notice
any breakage because of this change, please contact me.
Changes since 0.7.10:
- Compatibility for Python 2.4 is being dropped.
- The primaryjoin argument is no longer needed when constructing a
relationship() against a class that has multiple foreign key paths to the
target.
- Relationships against self-referential, composite foreign keys where a
column points to itself are now supported.
- Previously difficult custom join conditions, like those involving
functions and/or CASTing of types, will now function as expected in most
cases.
- New Class/Object Inspection System.
- A new enhancement to the aliased() construct has been added called
with_polymorphic() which allows any entity to be “aliased” into a
“polymorphic” version of itself, freely usable anywhere.
- The PropComparator.of_type() method can now be used to target any number
of target subtypes, by combining it with the new with_polymorphic()
function.
- Mapper and instance events can now be associated with an unmapped
superclass, where those events will be propagated to subclasses as those
subclasses are mapped. The propagate=True flag should be used.
- The registry of class names is now sensitive to the owning module and
package of a given class. The classes can be referred to via dotted name
in expressions.
- The “deferred reflection” feature allows the construction of declarative
mapped classes with only placeholder Table metadata, until a prepare()
step is called, given an Engine with which to reflect fully all tables
and establish actual mappings. The system supports overriding of columns,
single and joined inheritance, as well as distinct bases-per-engine.
- A new SQL registration system allows a mapped class to be accepted as a
FROM clause within the core.
- The new UPDATE..FROM mechanics work in query.update().
- Upon rollback(), only those objects that were made dirty since the last
flush will be expired, the rest of the Session remains intact.
- Caching Example now uses dogpile.cache.
- The new operator system in Core associates new and overridden operators
with types.
- SQL expressions can now be associated with types.
- The inspect() function introduced in New Class/Object Inspection System
also applies to the core.
- select() now has a method Select.correlate_except() which specifies
“correlate on all FROM clauses except those specified”.
- Support for Postgresql’s HSTORE type is now available as
postgresql.HSTORE. This type makes great usage of the new operator system
to provide a full range of operators for HSTORE types, including index
access, concatenation, and containment methods such as has_key(),
has_any(), and matrix().
- The postgresql.ARRAY type will accept an optional “dimension” argument,
pinning it to a fixed number of dimensions and greatly improving
efficiency when retrieving results.
- SQLite has no built-in DATE, TIME, or DATETIME types, and instead
provides some support for storage of date and time values either as
strings or integers.
- The “collate” keyword, long accepted by the MySQL dialect, is now
established on all String types and will render on any backend, including
when features such as MetaData.create_all() and cast() is used.
- Geared towards MySQL, a “prefix” can be rendered within any of these
constructs.
- The consideration of a “pending” object as an “orphan” has been made more
aggressive.
- The after_attach event fires after the item is associated with the
Session instead of before; before_attach added.
- Query now auto-correlates like a select() does.
- Correlation is now always context-specific.
- create_all() and drop_all() will now honor an empty list as such.
- Repaired the Event Targeting of InstrumentationEvents.
- No more magic coercion of “=” to IN when comparing to subquery in
MS-SQL.
- The Session.is_modified() method accepts an argument passive which
basically should not be necessary, the argument in all cases should be
the value True - when left at its default of False it would have the
effect of hitting the database, and often triggering autoflush which
would itself change the results. In 0.8 the passive argument will have no
effect, and unloaded attributes will never be checked for history since
by definition there can be no pending state change on an unloaded
attribute.
- Column.key is honored in the Select.c attribute of select() with
Select.apply_labels().
- A relationship() that is many-to-one or many-to-many and specifies
“cascade=’all, delete-orphan’”, which is an awkward but nonetheless
supported use case (with restrictions) will now raise an error if the
relationship does not specify the single_parent=True option.
- Adding the inspector argument to the column_reflect event.
- The MySQL dialect does two calls, one very expensive, to load all
possible collations from the database as well as information on casing,
the first time an Engine connects. Neither of these collections are used
for any SQLAlchemy functions, so these calls will be changed to no longer
be emitted automatically. Applications that might have relied on these
collections being present on engine.dialect will need to call upon
_detect_collations() and _detect_casing() directly.
- Inspector.get_primary_keys() is deprecated, use
Inspector.get_pk_constraint.
- Case-insensitive result row names will be disabled in most cases. It will
be available only optionally, by passing the flag `case_sensitive=False`
to `create_engine()`, but otherwise column names requested from the row
must match as far as casing.
- The sqlalchemy.orm.interfaces.InstrumentationManager class is moved to
sqlalchemy.ext.instrumentation.InstrumentationManager.
- SQLSoup is now moved into its own project and documented/released
separately; see https://bitbucket.org/zzzeek/sqlsoup.
- The older “mutable” system within the SQLAlchemy ORM has been removed.
- We had left in an alias sqlalchemy.exceptions to attempt to make it
slightly easier for some very old libraries that hadn’t yet been upgraded
to use sqlalchemy.exc. Some users are still being confused by it however
so in 0.8 we’re taking it out entirely to eliminate any of that confusion.
From the release announcement:
This is a bug fix release which includes the following fixes:
* Allow the dump of pg schemas [Guillaume Lelarge]]
* Prevent a crash on Windows when dropping a column or a constraint on
a table [Dhiraj Chawla]
* Ensure DDLScript will work with Slony 2.2+ which has a new SQL level
API [Neel Patel]
* Fix ordering of object types in the display options and add Event
Triggers which were missing [Dhiraj Chawla].
* Ensure the debugger can cope with functions that have an OUT
parameter as the first. [Ashesh Vashi]
* Fix the quoting of user mapping objects [Dinesh Kumar]
* Ensure that materialised views are available as targets for synonyms
[Neel Patel]
* Fix the query used to find tables in a Slony replication set [Neel Patel]
* Prevent a crash if a user starts an external process such as a
backup, and then immediately hits cancel [Neel Patel].
* Fix a memory leak in the Event Trigger code [Dinesh Kumar].
For more information or to download, please visit the website at
http://www.pgadmin.org/.
Guarantee transmission of all WAL files before replica failover
Prevent downcasing of non-ASCII identifiers
Fix several minor memory leaks
Correct overcommit behavior when using more than 24GB of work memory
Improve planner cost estimates for choosing generic plans
Fix estimates of NULL rows in boolean columns
Make UNION ALL and inheritance query plans recheck parameterized paths
Correct pg_dump bugs for foreign tables, views, and extensions
Prevent a parallel pg_restore failure on certain indexes
Make REINDEX revalidate constraints
Prevent two deadlock issues in SP-GIST and REINDEX CONCURRENTLY
Prevent GiST index lookup crash
Fix several regular expression failures
Allow ALTER DEFAULT PRIVILEGES to work on all schemas
Loosen restrictions on keywords
Allow various spellings of infinity
Expand ability to compare rows to records and arrays
Prevent psql client crash on bad PSQLRC file
Add spinlock support for ARM64
Guarantee transmission of all WAL files before replica failover
Prevent downcasing of non-ASCII identifiers
Fix several minor memory leaks
Correct overcommit behavior when using more than 24GB of work memory
Improve planner cost estimates for choosing generic plans
Fix estimates of NULL rows in boolean columns
Make UNION ALL and inheritance query plans recheck parameterized paths
Correct pg_dump bugs for foreign tables, views, and extensions
Prevent a parallel pg_restore failure on certain indexes
Make REINDEX revalidate constraints
Prevent two deadlock issues in SP-GIST and REINDEX CONCURRENTLY
Prevent GiST index lookup crash
Fix several regular expression failures
Allow ALTER DEFAULT PRIVILEGES to work on all schemas
Loosen restrictions on keywords
Allow various spellings of infinity
Expand ability to compare rows to records and arrays
Prevent psql client crash on bad PSQLRC file
Add spinlock support for ARM64
The following bugs were fixed since the release of version 4.0.7:
- bug #3988 Rename view is not working
- bug #4041 Interaction between linkified fields and grid editing
- bug #3975 Table grouping isn't implemented properly
- bug #4060 Browser tries to remember wrong password when creating new user
- bug #4002 Edit Index on big table doesn't show "Loading" or any message
- bug #4098 Default table tab is ignored
- bug #4099 Server/library difference warning: setting is ignored
- bug #4100 table tree group strategy
- bug #4102 ALTER TABLE ORDER BY and InnoDB
- bug #4103 Tracking report: cannot delete a statement
- bug #3996 Drizzle navigation doesn't expand
- bug #4074 GIS column editor: point not displayed
- bug #4109 Drizzle tables in navigation are shown as views
- bug #4095 NUL symbols added to the end of database dump file
- bug #4105 More disappears in table Structure
- bug #3992 Multi-row edit doesn't clear values when checking NULL
shared-mime-info 1.2 (2013-09-30)
* Mime-type changes:
- Use IANA registered application/sql type for SQL
- Add test for text/x-python
- Added *.pyx as Pyrex/Cython variant of text/x-python
- Lower the priority of the *png glob on Apple PNGs
- Add magic for Kobo e-book reader
- Add another magic for EPub books
- Add missing globs and tests for OpenPGP files
- Add MIME types for raw disk images
- Add video/x-matroska-3d mime-type
- Use application/vnd.adobe.flash.movie for SWF
- Use application/vnd.nintendo.snes.rom for SNES ROMs, associate *.sfc with them
- Fix shebang matches for shell scripts
- Remove *.ogv as a glob for Theora videos as they might not be Theora
- Improve detection of Perl scripts
- Add more aliases for Photoshop images
- Add Microsoft Publisher mime-type
- Correct JPEG2000 definition
* Check for errors when saving files, and ensure that files
are saved to disk before carrying on.
* Don't use access() to check for writability
* Rename configure.in to configure.ac
HSQLDB (HyperSQL DataBase) is the leading SQL relational database
engine written in Java. It offers a small, fast multithreaded and
transactional database engine with in-memory and disk-based tables
and supports embedded and server modes.
This package contains library file (hsqldb.jar) only, and it is
old and should be used only for LibreOffice package.
* InnoDB: The row_sel_sec_rec_is_for_clust_rec function would incorrectly prepare to compare a NULL column prefix in a secondary index with a non-NULL column in a clustered index.
* InnoDB: An incorrect purge would occur when rolling back an update to a delete-marked record.
* InnoDB: InnoDB would rename a user-defined foreign key constraint containing the string “_ibfk_” in its name, resulting in a duplicate constraint.
* InnoDB: Rolling back an INSERT after a failed BLOB write would result in an assertion failure. The assertion has been modified to allow NULL BLOB pointers if an error occurs during a BLOB write.
* InnoDB: The srv_master_thread background thread, which monitors server activity and performs activities such as page flushing when the server is inactive or in a shutdown state, runs on a one second delay loop. srv_master_thread would fail to check if the server is in a shutdown state before sleeping.
* InnoDB: An infinite loop could occur in buf_page_get_gen when handling compressed-only pages.
* Within a stored program, comparison of the value of a scalar subquery with an IN clause resulted in an error for the first execution and raised an assertion for the second execution.
* The my_strtoll10() function could incorrectly convert some long string-format numbers to numeric values and fail to set the overflow flag.
* For queries that accessed an INFORMATION_SCHEMA table in a subquery, and attempt to lock a mutex that had already been locked could cause a server crash.
* For DIV expressions, assignment of the result to multiple variables could cause a server crash.
* mysqldump wrote SET statements as SET OPTION, which failed when reloaded because the deprecated OPTION keyword has been removed from SET syntax.
* If one connection changed its default database and simultaneously another connection executed SHOW PROCESSLIST, the second connection could access invalid memory when attempting to display the first connection's default database. memory.
* MySQL 5.7 changed audit log file output to a new format that has better compatibility with Oracle Audit Vault. This format has been backported to MySQL 5.6 and it is possible to select either the old or new format using the new audit_log_format system variable, which has permitted values of OLD and NEW (default OLD). For details about each format, see The Audit Log File.
* Important Change; Replication: START SLAVE UNTIL SQL_AFTER_GTIDS did not cause the slave to stop until the next GTID event was received following execution of the transaction having the indicated GTID, which could cause issues in the case when the next GTID event is delayed, or does not exist. Now the slave stops after completing the transaction with that GTID.
* InnoDB; Partitioning: Following any query on the INFORMATION_SCHEMA.PARTITIONS table, InnoDB index statistics as shown in the output of statements such as SELECT * FROM INFORMATION_SCHEMA.STATISTICS were read from the last partition, instead of from the partition containing the greatest number of rows.
* InnoDB: When logging the delete-marking of a record during online ALTER TABLE...ADD PRIMARY KEY, InnoDB writes the transaction ID to the log as it was before the deletion or delete-marking of the record. When doing this, InnoDB would overwrite the DB_TRX_ID field in the original table, which could result in locking issues.
* InnoDB: The row_sel_sec_rec_is_for_clust_rec function would incorrectly prepare to compare a NULL column prefix in a secondary index with a non-NULL column in a clustered index.
* InnoDB: An incorrect purge would occur when rolling back an update to a delete-marked record.
* InnoDB: An assertion would be raised in fil_node_open_file due to a missing .ibd file. Instead of asserting, InnoDB should return false and the caller of fil_node_open_file should handle the return message.
* InnoDB: The assertion ut_ad(oldest_lsn <= cur_lsn) in file buf0flu.cc would fail because the current max LSN would be retrieved from the buffer pool before the oldest LSN.
* InnoDB: InnoDB memcached add and set operations would perform more slowly than SQL INSERT operations.
* InnoDB: The InnoDB memcached plugin could be initialized to insert into an InnoDB table with an INTEGER primary key.
More...
* MySQL 5.7 changed audit log file output to a new format that has better compatibility with Oracle Audit Vault. This format has been backported to MySQL 5.5 and it is possible to select either the old or new format using the new audit_log_format system variable, which has permitted values of OLD and NEW (default OLD). For details about each format, see The Audit Log File.
* InnoDB; Partitioning: Following any query on the INFORMATION_SCHEMA.PARTITIONS table, InnoDB index statistics as shown in the output of statements such as SELECT * FROM INFORMATION_SCHEMA.STATISTICS were read from the last partition, instead of from the partition containing the greatest number of rows.
* InnoDB: The row_sel_sec_rec_is_for_clust_rec function would incorrectly prepare to compare a NULL column prefix in a secondary index with a non-NULL column in a clustered index.
* InnoDB: An incorrect purge would occur when rolling back an update to a delete-marked record.
* InnoDB: InnoDB would rename a user-defined foreign key constraint containing the string “_ibfk_” in its name, resulting in a duplicate constraint.
* InnoDB: Rolling back an INSERT after a failed BLOB write would result in an assertion failure. The assertion has been modified to allow NULL BLOB pointers if an error occurs during a BLOB write.
* InnoDB: A regression introduced with the fix for Bug 11762038 would cause InnoDB to raise an incorrect error message. The message stated that, “InnoDB cannot delete/update rows with cascading foreign key constraints that exceed max depth of 20”. The error message would occur when killing connections reading from InnoDB tables that did not have foreign key constraints.
* InnoDB: The documentation incorrectly stated that START TRANSACTION WITH CONSISTENT SNAPSHOT provides a consistent snapshot only if the current isolation level is REPEATABLE READ or SERIALIZABLE. START TRANSACTION WITH CONSISTENT SNAPSHOT only works with REPEATABLE READ. All other isolation levels are ignored. The documentation has been revised and a warning is now generated whenever the WITH CONSISTENT SNAPSHOT clause is ignored.
* InnoDB: The srv_master_thread background thread, which monitors server activity and performs activities such as page flushing when the server is inactive or in a shutdown state, runs on a one second delay loop. srv_master_thread would fail to check if the server is in a shutdown state before sleeping.
more...
- bug #3993 Sorting in database overview with statistics doesn't work
- bug Handle the situation where PHP_SELF is not set
- bug #4080 Overwrite existing file not obeyed
- bug #3929 Database-specific privileges are not copied when cloning user
- bug #3997 Error handling in case MySQL extension is missing
- bug #4089 Moving Columns will alter column definition
- bug #4091 Insert ignore option does not work
- bug #4090 Downloading BLOB downloads page template
- bug #4092 Clicking on table name in view of information_schema redirects to wrong page
- bug #4079 Copy Table Add AUTO_INCREMENT value checkbox not working
- bug #4088 MySQL server version at index.php incorrect w/ controlhost
- bug #4001 Import error: Class 'ImportOds' not found
- bug #3986 Missing DROP VIEW button
Approved by Thomas Klausner.
The major changes since version 3.5.* are:
- HTML frames are gone.
- The navigation panel now presents a tree.
- Javascript now required
- Documentation has a new look.
- Many bug fixes and smaller new features
This update also fixes the security vulnerability reported in PMASA-2013-10.
Approved by Thomas Klausner.
No changelog, but at least, buildable with recent MySQL.
while here:
* removed OpenSSL related stuffs, no reason is found.
* set LICENSE=gnu-gpl-v2 (or later).
* drop needless definitions.
v0.22.0
- Add new composite API to resolve ambiguity between unpacking a composite and packing a composite with one element (issue #196, courtesy @kevinkehl)
- Breaking change: schema change methods no longer catch exceptions internally. They work the same as everything else.
v0.21.0
- Add 1.2 libs to gem
v0.19.0
- Fixed windows build by disabling native extensions (issue #188, courtesy @jacek99)
- Speed improvement to native composite column extension (issue #186, courtesy @muirmanders)
- Fix OrderedHash iterator return values (issue #185, courtesy @fester)
- Native support for dynamic composite decoding (issue #184, courtesy @muirmanders)
v0.18.0
- Cassandra 1.2 support (issue #175, courtesy @brainopia)
- drop_keyspace defaults to current keyspace (issue #176, courtesy @brianopia)
- Easier flush_batch interface (issue #182, courtesy @brianopia)
- Support for removing multiple columns (issue #183, courtesy @brianopia)
MySQL and InnoDB transaction/status monitor. Like 'top' for MySQL. Displays
queries, InnoDB transactions, lock waits, deadlocks, foreign key errors, open
tables, replication status, buffer information, row operations, logs, I/O
operations, load graph, and more. You can monitor many servers at once with
innotop.
