2013-05-15
Version 3.4.4 of Gramps! "The Ministry of Silly Names", a maintenance release.
* infinite recursion bug in narrative web generation
* protection on family trees when using version 3.4 and 4.0 on the same PC (road to 4.0)
* merging notes of media with citations now works
* crash during Calculate Preview of a filtered XML export
* fix annoying errors on navigation related to citations gramplet and tag object.
* listing the Family Trees can corrupt them.
* various fix around handling Gedcom file format
* fix citations and sources import on ProGen format
* better date handling and better alternate translation support on some textual reports according to locale under windows
* avoid Errors when setting wrong value as markup for invalid dates (Preferences)
* fix paragraph layout on PDF format or print output
* New: New-Zealand holidays
* Polish and backport code on XML import (road to 4.0)
* Regular expression rules now use search rather than match, fix design issues on regex filter rules
* Disable/Enable indent spouse on descendants tree
* fix regular expressions on Place filter rule
* consistency on cli arguments (road to 4.0)
* fix call of non-existant process on references proxy, enhanced tests on proxy filter
* fix NarWeb creation via cli for some non-english locales
* Various updated translations: ca, de, fr, it, nl, pt_BR, ru, sv, uk
Changes:
2.8.3
* [FIX] Sentinel instance role sampling fixed, the system is now more
reliable during failover and when reconfiguring instances with
non matching configuration.
* [FIX] Inline requests are now handled even when terminated with just LF.
* [FIX] Replication timeout handling greatly improved, now the slave is able
to ping the master while removing the old data from memory, and while
loading the new RDB file. This avoid false timeouts sensed by
masters.
* [FIX] Fixed a replication bug involving 32 bit instances and big datasets
hard to compress that resulted into more than 2GB of RDB file sent.
* [FIX] Return error for inline requests with unbalanced quotes.
* [FIX] Publish the slave replication offset even when disconnected from the
master if there is still a cached master instance.
2.8.2
* [FIX] Sentinel better desynchronization to avoid split-brain elections
where no Sentinel managed to get elected.
* [FIX] Stop accepting writes on "MISCONF" error only if master, not slave.
* [FIX] Reply to PING with an error on "MISCONF" errors.
2.8.1
* [FIX] Fixed a bug in "new Sentinel" config propagation.
* [FIX] Fixed a false positive in Redis tests.
2.8.0
* [FIX] Fixed an error in rdbWriteRaw() that should have no practical impact.
* [NEW] Log the new master when SLAVEOF command is used.
* [NEW] Sentinel code synchronized with the unstable branch, the new Sentinel
is a reimplementation that uses more reliable algorithms.
2.8.0 RC6
* [NEW] SCAN, SSCAN, HSCAN, ZSCAN commands.
2.8.0 RC5
* [FIX] redis-cli: don't crash with --bigkeys when the key no longer exist.
* [FIX] Allow AUTH / PING when disconnected from slave and serve-stale-data
is no.
* [FIX] PSYNC: safer handling of PSYNC requests with offsets in the future.
* [FIX] Replication: Fix master timeout detection.
* [FIX] Replication: Correctly install the write handler after successful
PSYNC.
2.8.0 RC4
* [FIX] Fixed a serious EVAL memory leak in the Lua stack.
* [FIX] Fixed server startup when no IPv6 address exists in any interface.
* [FIX] Send MISCONFIG error when BGSAVE fails because can't fork.
* [FIX] Memory efficiency with large (> a few kbytes) values improved
considerably.
* [NEW] DEBUG SDSLEN for sds memory debugging.
2.8.0 RC3
* [FIX] Improved expired keys collection algorithm. Even under heavy load keys
to be expired can't accumulate because of lack of CPU time.
* [FIX] Replication speed regression fixed (issue #1238).
* [FIX] Fixed an hard to trigger PSYNC bug.
* [FIX] Fixed Issue #1240, ZUNIONSTORE could lead to wrong result.
* [NEW] Add per-db average TTL information in INFO output.
* [NEW] redis-benchmark improvements.
* [NEW] dict.c API wrong usage detection.
2.8.0 RC2
* [FIX] Fixed a critical replication bug, see issue #1221.
* [NEW] The new inline protocol now accepts quoted strings like, for example
you can now type in a telnet session: set 'foo bar' "hello world\n".
2.8.0 RC1
* [NEW] Slaves are now able to partially resynchronize with the master,
so most of the times a full resynchronization with the RDB creation
in the master side is not needed when the master-slave link is
disconnected for a short amount of time.
* [NEW] Experimental IPv6 support.
* [NEW] Slaves explicitly ping masters now, a master is able to detect
a timed out slave independently.
* [NEW] Masters can stop accepting writes if not enough slaves with a given
maximum latency are connected.
* [NEW] Keyspace changes notifications via Pub/Sub.
* [NEW] CONFIG SET maxclients is now available.
* [NEW] Ability to bind multiple IP addresses.
* [NEW] Set process names so that you can recognize, in the "ps" command
output, the listening port of an instance, or if it is a saving child.
* [NEW] Automatic memory check on crash.
* [NEW] CONFIG REWRITE is able to materialize the changes in the configuration
operated using CONFIG SET into the redis.conf file.
* [NEW] More NetBSD friendly code base.
* [NEW] PUBSUB command for Pub/Sub introspection capabilities.
* [NEW] EVALSHA can now be replicated as such, without requiring to be
expanded to a full EVAL for the replication link.
* [NEW] Better Lua scripts error reporting.
* [NEW] SDIFF performance improved.
* [FIX] A number of bugfixes.
2.6.17
* [FIX] redis-cli: fix big keys search when the key no longer exist.
* [FIX] Allow AUTH / PING when disconnected from slave with serve-stale-data
on.
* [FIX] redis-benchmark: update help for new __rand_int__ form.
* [FIX] Fix broken rdbWriteRaw() return value check in rdb.c (harmless).
* [FIX] Log to what master a slave is going to connect to.
* [FIX] Only run the fast active expire cycle if master & enabled.
* [FIX] Fixed a replication bug involving 32 bit instances and big datasets
hard to compress that resulted into more than 2GB of RDB file sent.
Changes since 1.4.0:
- COUCHDB-1781: The official documentation has been overhauled.
- New administration UI, included as an experimental preview.
- COUCHDB-1888: Fixed an issue where admin users would be restricted
by the public_fields feature.
- Fixed an issue with the JavaScript CLI test runner.
- COUCHDB-1867: An experimental plugin feature has been added.
- COUCHDB-1894: An experimental Node.js-based query server runtime added.
- COUCHDB-1901: Better retry mechanism for transferring attachments during
replication.
Fixes to the UPDATE FUNCTIONS for upgrades from releases earlier than 2.2.0
Fixes to the FAILOVER logic
Fixes slon to avoid constant database connection & disconnection
Fixes to CLONE PREPARE processing
(update dependency from py-amkCrypto to py-crypto).
0.7.1 - 2009-11-16
New features:
- Entities can now be declared "abstract" so that they do not create a table,
etc... This allows, among others, an entity to inherit from multiple abstract
classes (patch from Stephane Klein, closes#89).
- Added a new collection which can resolve entities relative to the current
entity, for example "..other_module.Class" (based on patches from Johannes
Janssen, closes#93).
- Added a new entity option "resolve_root", which allows one to specify the
root module where your entities are defined. The string will be prepended
to all "absolute" entity paths. It can also be used on a per-entity basis.
This feature is based on a patch from Johannes Janssen, see #93.
Changes:
- using_options_defaults and using_table_options statements can be used several
times within the same class (closes#70).
Bug fixes:
- Fixed custom base classes and versioned extension when used with zope
interfaces (closes#98, patch from Valentin Lab)
- Fixed having relationships in custom base classes (based on patch
by Stephane Klein)
Upstream changes:
1.68 Mon Aug 6 22:22:22 PDT 2012
Patch fromFileGetTopLines() and fromFileIsHeader(), which are used by fromFile(). Impact: minor.
Improve performance of fromFileGuessOS()
Improve fromFile(), fromCSV(), csv() to support using \r, \n within a CSV field.
join() now supports {matchNULL => 1, NULLasEmpty => 1}, if one would like to treat NULL as empty string, or
treat NULL as equal (however, not equal to empty string). Both are set to 0 by default.
Suggested by Kyle Horton & Wilson Dave.
Remove inheritance from AutoLoader and Exporter.
Thanks to Brian Wightman
Thanks to Nicholas Andonakis for sharing his code, quite a few ideas in his package inspired the improvements below!
Add new shortcut methods: lastRow(), lastCol(), colName($colNumericIndex)
One can now write
foreach my $i (0..$t->lastRow)
instead of
foreach my $i (0..$t->nofRow-1)
Add iterator(), so that one can now write
my $next = $t_product->iterator();
while (my $row = $next->()) {
# have access to a row as a hash reference, access row number by &$next(1);
$t_product->setElm($next->(1), 'ProductName', 'New! '.$row->{ProductName});
}
addCol() can take the default value for the new column (first argument)
addRow() supports {addNewCol => 1}
moveCol() can take a $newColName.
setElm() can set a value for multiple cells, specified by ref to row array and col array
match_string(), match_pattern(), match_pattern_hash() also produce $parentTable->{MATCH}
# match returns all matched row ids in $t_product->{MATCH} (ref to row ID array)
$t_product->match_pattern_hash('$_{UnitPrice} > 20');
# create a new column, with 'No' as the default value
$t_product->addCol('No', 'IsExpensive');
# use $t_product->{MATCH} to set values for multiple Elements
$t_product->setElm($t_product->{MATCH}, 'IsExpensive', 'Yes');
1.67 Wed Jul 25 11:47:23 PDT 2012
Update Change.txt file to point out $keepRestCol defaults to 1 is only for group()
For pivot(), $keepRestCol is still default to 0 as before.
1.66 Wed Jul 25 11:03:29 PDT 2012
Change the default value of keepRestCol in group() to 1, instead of 0 to be compatible with older versions
Thanks to Kyle Horton
6.0.1:
* Clarification of license. Thanks to
Jan Staněk <jstanek@redhat.com> for bringing this issue up.
This work is now explicitly licensed under 3-clause BSD license.
* Fixed a long standing bug (August 2008, rev 9fd52748fa59)
on "dbtables.py". Notified by Maxime Labelle.
* If you want to link with Oracle Berkeley DB 6.0, you will
need to create the environment variable
'YES_I_HAVE_THE_RIGHT_TO_USE_THIS_BERKELEY_DB_VERSION'
to signal to the pybsddb that you are legal. To be legal,
your code MUST be AGPL3 *OR* you have to buy a commercial
license from Oracle.
If you are not legally entitled to use Berkeley DB 6.0 and
you have previous versions of Berkeley DB on your system,
you can a) delete Berkeley DB 6.0 and try again, OR
b) instruct pybsddb to use a previous Berkeley DB version,
using environment variables or command line options.
Sorry for the inconvenience. I am trying to protect you.
Some details:
https://forums.oracle.com/message/11184885http://lists.debian.org/debian-legal/2013/07/
The replication issue affects some users of PostgreSQL binary replication, and can cause minor data loss between the master and the standby. While not all users are affected, it is difficult to predict when the bug will occur, so we urge all users of replication and continuous backup (PITR) to update immediately. Additionally, users who had replication running under PostgreSQL minor versions 9.3.0, 9.3.1, 9.2.5, 9.1.10, or 9.0.14 should plan to take a fresh base backup of each standby after update, in order to ensure no prior data corruption already exists.
This release also fixes two timing issues with VACUUM, which can cause old, overwritten or deleted rows to re-appear at a later date under some circumstances. Users with very high transaction rates, particularly those who experience "transaction ID wraparound" every few weeks or less, are the most at risk for this issue. Those users should set vacuum_freeze_table_age to 0, and run a database-wide VACUUM after the update. The second of the two VACUUM issues affects only 9.3, making it expecially important for 9.3 users to update.
=== 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.
== v0.16.0 [2013-07-22] Michael Granger <ged@FaerieMUD.org>
Bugfixes:
- Avoid warnings about uninitialized instance variables.
- Use a more standard method of adding library and include directories.
This fixes build on AIX (Github #7) and Solaris (#164).
- Cancel the running query, if a thread is about to be killed (e.g. by CTRL-C).
- Fix GVL issue with wait_for_notify/notifies and notice callbacks.
- Set proper encoding on the string returned by quote_ident, escape_literal
and escape_identifier (#163).
- Use nil as PG::Error#result in case of a NULL-result from libpq (#166).
- Recalculate the timeout of conn#wait_for_notify and conn#block in case
of socket events that require re-runs of select().
Documentation fixes:
- Fix non working example for PGresult#error_field.
Enhancements:
- Add unique exception classes for each PostgreSQL error type (#5).
- Return result of the block in conn#transaction instead of nil (#158).
- Allow 'rake compile' and 'rake gem' on non mercurial repos.
- Add support for PG_DIAG_*_NAME error fields of PostgreSQL-9.3 (#161).
pgAdmin III Changelog
=====================
Notes
-----
This is the pgAdmin III changelog. Items are marked with the initials of the
developer responsible for them, and the version of pgAdmin that the change
will first appear in. For convenience, changes during Beta and RC phases may
include an RCx or Bx suffix on the version number, but for simplicity these
will not normally be retained.
A name in square braces [Joe Bloggs] indicates that the change was written by
Joe. The initialed developer was responsible for reviewing the changes in these
cases.
Names shown as "per Joe Bloggs", indicate that Joe reported the problem and may
have provided help debugging it, but did not actually provide the change.
Key to developers
-----------------
- DP Dave Page
- AP Andreas Pflug
- JMP Jean-Michel Poure
- HS Hiroshi Saito
- AHP Adam H. Pendleton
- MP Marc Persuy
- DAP Darko Prenosil
- FGP Florian G. Pflug
- MH Magnus Hagander
- GL Guillaume Lelarge
- AV Ashesh Vashi
Changes
-------
Date Dev Ver Change details
---------- --- ------ --------------
2013-09-06 DP 1.18.1 Fix a memory leak in the Event Trigger code [Dinesh
Kumar].
2013-08-20 AV 1.18.0 Fix a layout bug in the graphical explain renderer that
could render nodes on top of each other.
2013-08-06 DP 1.18.0 Fix Slony's DDL Script support [Akshay Joshi].
2013-07-26 DP 1.18.0 Add support for Event Triggers in 9.3+ [Dinesh Kumar].
2013-07-22 DP 1.18.0 Avoid using a Help cache file that needs to be world
writeable, and ensure sed is happy when post-processing
helpfiles.
2013-07-22 DP 1.18.0 Fix the help path on the import dialogue and improve the
error handling [Akshay Joshi].
2013-07-22 DP 1.18.0 Fix path the the Search Objects help doc [Dhiraj Chawla].
2013-07-18 GL 1.18.0 Fix UTF-8 display for guru hints [Marek Cernocky].
2013-07-08 DP 1.18.0 Prevent a crash when creating a stored procedure in
PPAS [Dinesh Kumar].
2013-06-19 GL 1.18.0 Disable the Favourites menu items if there is no
favourites file path (per a comment from Michael Shapiro).
2013-06-18 GL 1.18.0 Make No the default button on the Truncate confirmation
dialog (per request from Humberto Cereser Ibanez).
2013-06-18 DP 1.18.0 Support Materialized Views [Neel Patel].
2013-06-07 DP 1.18.0 Avoid a possible crash on Linux when using the
"Script" options of the Query Tool [aditsu].
2013-05-26 DP 1.18.0 Fix comments on constraints [Thom Brown].
2013-05-26 DP 1.18.0 Fix schema prefixes in cast definitions in the browser.
2013-05-26 DP 1.18.0 Treat sequences as first class objects in the Grant
Wizard. Support USAGE and remove obsolete RULE
permissions [Dhiraj Chawla].
2013-05-26 DP 1.18.0 Set the default backup type to "Custom".
2013-05-21 DP 1.18.0 Improve the copy handling on the Edit Grid so that
it works more consistently and predictably.
2013-05-20 DP 1.18.0 Fix comments on columns.
2013-05-20 DP 1.18.0 Remove the "Apply" buttons from the function, view
package and external table dialogues. Their use is
discouraged, and the code is fragile, complex and
very buggy.
2013-05-20 DP 1.18.0 Fix a crash that could occur if the browser fails to
detect that an object has been changed by another
session.
2013-05-17 DP 1.18.0 Change the default SQL box font to a slightly smaller
size on GTK based platforms.
2013-05-17 DP 1.18.0 Don't prompt the user for a password if they're using
a client certificate.
2013-05-17 DP 1.18.0 Ensure global backups use the mintenance database to
avoid access issue with postgres or template1.
2013-05-17 DP 1.18.0 Fix SSL certificate authentication.
2013-05-08 DP 1.18.0 Fix renaming and schema changes for stored procedures
in PPAS [Dinesh Kumar].
2013-05-02 DP 1.18.0 Add SSH tunnelling support to allow connections to be
made to hosts via an SSH server [Akshay Joshi].
2013-05-02 DP 1.18.0 Display the index validity in the properties list for
indexes and index-based constraints [Gabrielle Roth].
2013-04-29 DP 1.18.0 Add an option to include column headers when copying
from the query tool results [Jasmin Dizdarevic].
2013-04-29 DP 1.18.0 Allow the decimal mark displayed by the query tool to be
configured as the thousands separator can [Jasmin
Dizdarevic].
2013-04-25 DP 1.18.0 Ensure the Query Tool's maximum column length setting
is honoured.
2013-04-22 DP 1.18.0 Handle default privileges to PUBLIC correctly. [Dhiraj
Chawla].
2013-03-24 GL 1.18.0 Add tab option in the Import dialog. Per a request from
Jeff Janes.
2013-03-17 GL 1.18.0 Add smallserial handling. Per a request from Matthew
Syphus.
2013-03-01 DP 1.18.0 Fix the editing of pg_hba.conf files [Dhiraj Chawla].
2013-02-25 DP 1.18.0 Fix the display of extension owner names.
2013-02-23 GL 1.18.0 Add a title to the backup and restore windows. Per
request from Bastiaan Olij.
2013-02-22 DP 1.18.0 Fix a bug that could cause a NOTICE to be displayed
when rendering FTS Configurations in the tree.
2013-02-07 DP 1.18.0 Don't try to display dependents or dependencies for
pgAgent jobs, schedules or steps.
2013-02-06 DP 1.18.0 Fix the handling of expiry times when modifying roles.
2013-02-04 DP 1.18.0 Prevent foreign keys being recreated unnecessarily when
modifying tables [Michael Banck]
2013-01-24 DP 1.18.0 Prevent Cmd+S adding characters to the Query Tool when
the Save button is disabled.
2013-01-18 DP 1.18.0 Fix handling of Greenplum partitions [Lubomir Petrov]
2013-01-06 GL 1.18.0 Add -V/--version CLI option.
2013-01-06 GL 1.18.0 Add actions menu to the serverstatus tool.
2013-01-06 GL 1.18.0 Fix the database SQL when reseting a configuration
parameter. Per a report from Bartosz Dmytrak.
2013-01-04 GL 1.18.0 Refresh the toolbar buttons when a list has been
updated. Per a report from Evan Martin.
2013-01-04 GL 1.18.0 Fix the "NO INHERIT" query. Report from Thomas Joseph.
2012-12-24 GL 1.18.0 Display default privs. Report from Nathan Alden.
2012-12-24 GL 1.18.0 Sort references by schema name and relation name in
dlgForeignKey. Report from Michal Kozusznik.
2012-12-24 GL 1.18.0 Fix the change of the superuser attribute. Report from
Michal Kozusznik.
2012-12-18 DP 1.18.0 Prevent a crash when using Cmd-A on a file loaded into
the Query Tool when opened with Cmd-E on Mac.
2012-12-07 DP 1.18.0 Fix the queries used to get object comments to allow
for duplicate OIDs that may be present following use
of pg_upgrade.
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.
2012-09-06 DP 1.18.0 Detect serial/bigserial columns from pg_depend, rather
than guessing [Quan Zongliang].
2012-09-05 DP 1.18.0 Display the next expected value for a sequence in the
property list [Quan Zongliang].
2012-07-11 MH 1.18.0 Add optional thousands separator to the query tool
results grid.
2012-07-11 MH 1.18.0 Right-justify numeric values in the query tool results
## Rails 3.2.14 (Jul 22, 2013) ##
* Do not re-create destroyed association when saving the parent object.
Fixes#11450. *Paul Nikitochkin*
* Do not shallow the original exception in `exec_cache` on PostgreSQL adapter.
Fixes#11260. *Rafael Mendon«®a Fran«®a*
* Fix `ActiveRecord::Store` incorrectly tracking changes of its attributes.
Fixes#10373. *Janko Marohni««*
* Fix a bug that prevented the use of the default STI inheritance column
(ActiveRecord::Base.inheritance_column = 'some_column'.)
*chapmajs + Takehiro Adachi*
* Fix mysql2 adapter raises the correct exception when executing a query on a
closed connection. *Yves Senn*
* Fixes bug where `Company.new.contract_ids` would incorrectly load
all non-associated contracts.
Example:
company = Company.new # Company has many :contracts
# before
company.contract_ids # => SELECT ... WHERE `contracts`.`company_id` IS NULL
# after
company.contract_ids # => []
*Jared Armstrong*
* Fix the `:primary_key` option for `has_many` associations.
Fixes#10693. *Yves Senn*
* fixes bug introduced by #3329. Now, when autosaving associations,
deletions happen before inserts and saves. This prevents a 'duplicate
unique value' database error that would occur if a record being created had
the same value on a unique indexed field as that of a record being
destroyed. Backport of #10417
*Johnny Holton*
* Fix that under some conditions, Active Record could produce invalid SQL of
the sort: "SELECT DISTINCT DISTINCT". Backport of #6792. *Ben Woosley*
* Require `ActiveRecord::Base` in railtie hooks for rake_tasks, console and
runner to avoid circular constant loading issues. Backport #7695.
Fixes#7683 and #882
*Ben Holley*
* Maintain context for joins within ActiveRecord::Relation merges.
Backport #10164. *Neeraj Singh + Andrew Horner*
* Make sure the `EXPLAIN` command is never triggered by a `select_db` call.
*Daniel Schierbeck*
* Revert changes on `pluck` that was ignoring the select clause when the
relation already has one. This caused a regression since it changed the
behavior in a stable release.
Fixes#9777.
*Rafael Mendon«®a Fran«®a*
* Confirm a record has not already been destroyed before decrementing
counter cache. *Ben Tucker*
* Default values for PostgreSQL bigint types now get parsed and dumped to the
schema correctly. Backport #10098. *Erik Peterson*
* Removed warning when `auto_explain_threshold_in_seconds` is set and the
connection adapter doesn't support explain.
This is causing a regression since the Active Record Railtie is trying to
connect to the development database in the application boot.
*Rafael Mendon«®a Fran«®a*
* Do not reset `inheritance_column` when it's set explicitly.
Backport of #5327. *kennyj + Fred Wu*
* Fix a problem wrong exception is occured
when raising no translatable exception in PostgreSQL. *kennyj*
* Resets the postgres search path in the structure.sql after the structure
is dumped in order to find schema_migrations table when multiples schemas
are used.
Fixes#9796.
*Juan M. Cuello + Dembskiy Alexander*
* Reload the association target if it's stale. `@stale_state` should be nil
when a model isn't saved.
Fixes#7526.
*Larry Lv*
* Don't read CSV files during execution of `db:fixtures:load`. CSV support for
fixtures was removed some time ago but the task was still loading them, even
though later the code was looking for the related yaml file instead.
*kennyj*
- Fix uninitialized indicators in conversion_into_type and
conversion_use_type specialisations
- Fixed placeholder matching for PostgreSQL-style casts with ORM
- Fixed memory leaking in use binding in case of bind/unbind sequence
- Fixed sscanf formatter for MinGW/MSVC in backends
- Fixed partial placeholder name matching for ORM cases
- Added test for use of indicators with rowset<row>
- Added test for get_affected_rows after bulk operations
Add options for selecting MySQL/PostgreSQL/SQLite backends, defaulting
to PostgreSQL.
* Shared Libraries are now named so as to allow having multiple versions of Slony installed simultaneously on a database cluster
* Let DDL for EXECUTE SCRIPT to be specified inline
* Added a RESUBSCRIBE NODE command to reshape clusters.
* The FAILOVER process has been reworked to be more reliable.
* Major "protocol" change; rather than constructing cursors to query logged updates, version 2.2 now uses the COPY protocol to stream data into log tables on subscribers.
* Add materialized views
* Make simple views auto-updatable
* Add many features for the JSON data type, including operators and functions to extract elements from JSON values
* Implement SQL-standard LATERAL option for FROM-clause subqueries and function calls
* Allow foreign data wrappers to support writes (inserts/updates/deletes) on foreign tables
* Add a Postgres foreign data wrapper to allow access to other Postgres servers
* Add support for event triggers
* Add optional ability to checksum data pages and report corruption
* Prevent non-key-field row updates from blocking foreign key checks
* Greatly reduce System V shared memory requirements
UPGRADE URGENCY: MODERATE.
* [FIX] Stop writes when fork() fails when trying to BGSAVE. BGSAVE errors
were trapped only in the case the saving child failed, so the fork()
error was no trapped as no child is created at all.
* [FIX] Fix a serious memory efficiency regression, Redis 2.6.16 is
significantly better with large values (>= a few kbytes) and will
be able to store two times the amount of data compared to Redis 2.6.15
when values are in that range.
* [FIX] Fixed an issue with Table conversion in the lua-cmsgpack library exposed
by the Redis scripting engine.
* [NEW] DEBUG SDSLEN was introduced to debug memory inefficiencies due to
SDS allocation more easily.
CouchDB 1.4.0
* We now support Erlang/OTP R16B and R16B01; the minimum required
version is R14B.
* User document role values must now be strings. Other types of values
will be refused when saving the user document.
* COUCHDB-1684: Support for server-wide changes feed reporting on
creation, updates and deletion of databases.
* COUCHDB-1139: it's possible to apply list functions to _all_docs view.
* Automatic loading of CouchDB plugins.
* COUCHDB-1634: Reduce PBKDF2 work factor.
* Allow storing pre-hashed admin passwords via _config API.
* COUCHDB-1772: Prevent invalid JSON output when using all_or_nothing
_bulk_docs API.
* Add a configurable whitelist of user document properties.
* COUCHDB-1852: Support Last-Event-ID header in EventSource changes
feeds.
* Much improved documentation, including an expanded description of
validate_doc_update functions and a description of how CouchDB handles
JSON number values.
* COUCHDB-1632: Ignore epilogues in multipart/related MIME attachments.
* Split up replicator_db tests into multiple independent tests.
CouchDB 1.3.1
* Tolerate missing source and target fields in _replicator docs (COUCHDB-1788).
* Don't log about missing .compact files.
* Fix bug in WARN level logging from 1.3.0 (COUCHDB-1794).
* Fix the -S option to couchjs to increase memory limits (COUCHDB-1792).
* Improve documentation: better structure, improve language, less duplication.
* Improvements to test suite and VPATH build system.
Fix an off-by-one error that caused quoted empty string at the end of a CRNL-terminated line of CSV input to be misread by the command-line shell.
Fix a query planner bug involving a LEFT JOIN with a BETWEEN or LIKE/GLOB constraint and then another INNER JOIN to the right that involves an OR constraint.
Fix a query planner bug that could result in a segfault when querying tables with a UNIQUE or PRIMARY KEY constraint with more than four columns.
1.65 Wed Jul 3 16:40:48 PDT 2013
Ruslan Zakirov:
* Bug fix for DateTimeInterval extraction on Pg
1.64 Mon Jul 1 10:20:43 PDT 2013
No changes since 1.63_03. Simply a non-dev release of everything since 1.63.
1.63_03 Fri Jun 14 13:11:01 PDT 2013
Ruslan Zakirov:
* warn when rollback and commit are mixed
* Handle->NullsOrder
* skip timezone tests on SQLite when tzinfo is not there
* skip tests if mysql can not do timezones
* DISTINCT argument in Join method
* DISTINCT argument in Join and NewAlias
Thomas Sibley:
* Reset the iterator position whenever a search is run
* Return the correct record from ->Last instead of the first record
* Document the caveat of using GotoItem with a non-zero N
1.63_02 Wed Apr 17 18:47:31 MSK 2013
* _Set now can take undef as argument to mean default or NULL.
Still may result in error if default is not defined and no_nulls
is true for the column. If old behaviour is required set
$record->{'no_undefs_in_set'} to true value.
* FUNCTION argument is now allowed in Limit. Code to combine
FUNCTION, ALIAS and FIELD was refactored and unified in one
place - CombineFunctionWithField method. Used in Column, GroupBy
and Limit. This change should be backwards compatible.
* Handle->DateTimeIntervalFunction
1.63_01 Wed Mar 27 13:02:35 PDT 2013
* IN and NOT IN operators in ->Limit method
* Add an AdditionalColumn method to collections
* Add an AS parameter to Column method in collections
* Consistent query generation by sorting hash keys/values
1.63 Fri Sep 14 2012 01:19:38 GMT+0400 (MSK)
* joins_are_distinct hint to indicate that distinct is not
required for the current set of joins.
1.62 Mon Mar 26 09:31:05 UTC 2012
* Bind values were ignored in SimpleUpdateFromSelect
0.40 Sat Dec 17 17:03:51 PST 2011
- doc: sql_update_schema link to sql_add_column misspelled
- Pg: fix mapping for DOUBLE PRECISION type to avoid needless alter cols
- mysql: implement altering column types & lengths
2.018002 2013-07-30 18:45:10 CST6CDT
- ::Helper::ResultSet correctly uses all Helpers (reported by moltar)
Note that some deprecated helpers were removed from ::ResultSet, so check
your code to see if you use the as_virtual_view method. If you do, replace
it with as_subselect_rs and you'll be fine.
- Fix return precedence in test (Reini Urban)
1.1.2 5 August 2011 15:47:00
- use Digest::SHA over Digest::SHA1 since it is core, RT #70092 (Salvatore Bonaccorso)
1.1.1 30 March 2011 12:17:00
- use 5.8.1 instead of 5.6.1 (and correctly)
- bump DBIx::Class dependency (RT#66601)
* B has been upgraded from 1.42 to 1.42_01, fixing bugs related to lexical subroutines.
* Digest::SHA has been upgraded from 5.84 to 5.84_01, fixing a crashing bug.
* Module::CoreList has been upgraded from 2.89 to 2.96.
* Starting in v5.18.0, a construct like /[#](?{})/x would have its # incorrectly interpreted as a comment. The code block would be skipped, unparsed. This has been corrected.
* A number of memory leaks related to the new, experimental regexp bracketed character class feature have been plugged.
* The OP allocation code now returns correctly aligned memory in all cases for struct pmop. Previously it could return memory only aligned to a 4-byte boundary, which is not correct for an ithreads build with 64 bit IVs on some 32 bit platforms. Notably, this caused the build to fail completely on sparc GNU/Linux.
* The debugger's man command been fixed. It was broken in the v5.18.0 release. The man command is aliased to the names doc and perldoc - all now work again.
* @_ is now correctly visible in the debugger, fixing a regression introduced in v5.18.0's debugger.
* Fixed a small number of regexp constructions that could either fail to match or crash perl when the string being matched against was allocated above the 2GB line on 32-bit systems.
* Perl v5.16 inadvertently introduced a bug whereby calls to XSUBs that were not visible at compile time were treated as lvalues and could be assigned to, even when the subroutine was not an lvalue sub. This has been fixed.
* Perl v5.18 inadvertently introduced a bug whereby dual-vars (i.e. variables with both string and numeric values, such as $! ) where the truthness of the variable was determined by the numeric value rather than the string value.
* Perl v5.18 inadvertently introduced a bug whereby interpolating mixed up- and down-graded UTF-8 strings in a regex could result in malformed UTF-8 in the pattern: specifically if a downgraded character in the range \x80..\xff followed a UTF-8 string
* Lexical constants (my sub a() { 42 }) no longer crash when inlined.
* Parameter prototypes attached to lexical subroutines are now respected when compiling sub calls without parentheses. Previously, the prototypes were honoured only for calls with parentheses.
* Syntax errors in lexical subroutines in combination with calls to the same subroutines no longer cause crashes at compile time.
* The dtrace sub-entry probe now works with lexical subs, instead of crashing
* Undefining an inlinable lexical subroutine (my sub foo() { 42 } undef &foo) would result in a crash if warnings were turned on.
* Deep recursion warnings no longer crash lexical subroutines.
Add support for partial indexes
Cut-over to the next generation query planner for faster and better query plans.
The EXPLAIN QUERY PLAN output no longer shows an estimate of the number of rows generated by each loop in a join.
Added the FTS4 notindexed option, allowing non-indexed columns in an FTS4 table.
Added the SQLITE_STMTSTATUS_VM_STEP option to sqlite3_stmt_status().
Added the cache_spill pragma.
Added the query_only pragma.
Added the defer_foreign_keys pragma and the sqlite3_db_status(db, SQLITE_DBSTATUS_DEFERRED_FKS,...) C-language interface.
Added the "percentile()" function as a loadable extension in the ext/misc subdirectory of the source tree.
Added the SQLITE_ALLOW_URI_AUTHORITY compile-time option.
Add the sqlite3_cancel_auto_extension(X) interface.
A running SELECT statement that lacks a FROM clause (or any other statement that never reads or writes from any database file) will not prevent a read transaction from closing.
Add the SQLITE_DEFAULT_AUTOMATIC_INDEX compile-time option. Setting this option to 0 disables automatic indices by default.
Issue an SQLITE_WARNING_AUTOINDEX warning on the SQLITE_CONFIG_LOG whenever the query planner uses an automatic index.
Added the SQLITE_FTS3_MAX_EXPR_DEPTH compile-time option.
Added an optional 5th parameter defining the collating sequence to the next_char() extension SQL function.
The SQLITE_BUSY_SNAPSHOT extended error code is returned in WAL mode when a read transaction cannot be upgraded to a write transaction because the read is on an older snapshot.
Enhancements to the sqlite3_analyzer utility program to provide size information separately for each individual index of a table, in addition to the aggregate size.
Allow read transactions to be freely opened and closed by SQL statements run from within the implementation of application-defined SQL functions if the function is called by a SELECT statement that does not access any database table.
Disable the use of posix_fallocate() on all (unix) systems unless the HAVE_POSIX_FALLOCATE compile-time option is used.
Update the ".import" command in the command-line shell to support multi-line fields and correct RFC-4180 quoting and to issue warning and/or error messages if the input text is not strictly RFC-4180 compliant.
Bug fix: In the unicode61 tokenizer of FTS4, treat all private code points as identifier symbols.
Bug fix: Bare identifiers in ORDER BY clauses bind more tightly to output column names, but identifiers in expressions bind more tightly to input column names. Identifiers in GROUP BY clauses always prefer output column names, however.
Bug fixes: Multiple problems in the legacy query optimizer were fixed by the move to NGQP.
messages from daily (or weekly).
Rebuilding man page index:
man-gpl-tmp2/mysql_client_test.1: No such file or directory
man-gpl-tmp2/mysqltest.1: No such file or directory
Bump PKGREVISION.
UPGRADE URGENCY: MODERATE, upgrade ASAP only if you experience issues related to
the expired keys collection algorithm, or if you use the
ZUNIONSTORE command.
* [FIX] Improved expired keys collection algorithm. Even under heavy load keys
to be expired can't accumulate because of lack of CPU time.
* [FIX] Fixed Issue #1240, ZUNIONSTORE could lead to wrong result.
* [NEW] redis-benchmark improvements.
* [NEW] dict.c API wrong usage detection.
WARNING: redis-benchmark released with 2.6.15 features non backward compatible
change in the way the random arguments are specified, use the --help
option for more information.
Upstream changes:
0.23 31 Oct 2012
* add find_related() method
0.24 5 Nov 2012
* add tests for CatalystX::CRUD::Controller::REST
0.25 5 Nov 2012
* fix skip test count for t/02-rest
0.26 28 Jan 2013
* wrap RDBO::Iterator in CXC::Iterator for search_related() and iterator_related() methods.
0.27 31 Jan 2013
* explicitly require JSON dependency for Helpers
0.28 22 July 2013
* do not attempt to sort related objects till column name api can be figured out r14454
Upstream changes:
0.53 31 Oct 2012
* add list_related and view_related primarily for REST support
0.54 5 Nov 2012
* add Results->serialize() method
* refactor some Controller methods into a Role class
* Model::File->fetch() now returns undef if file does not exist. Add Model::File->prep_new_object().
* add new required method to Object class: is_new()
* add Model->put_related method
0.55 28 Jan 2013
* add Iterator->serialize() method.
Upstream changes:
0.61 2013-06-19 12:48:34
- Fix test failure caused by hash randomisation in perl 5.17 (RT#82917)
0.60 2012-06-12 16:27:00
- Add per_request_schema hook to PerRequestSchema trait and docs
- Additional paranoia in types as it's possible for loading code
to clobber $_
pkgsrc-users.
Changes since 4.10:
* Turn down module cleanup verbosity
* Add check for rogue postmasters.
* Add pseudo-branch targets HEAD_PLUS_LATEST and HEAD_PLUS_LATEST2.
* Use Digest::SHA instead of Digest::SHA1.
* Make directory handling more robust in git code.
* Move web transaction into a module procedure.
* Switch to using the porcelain format of git status.
* Provide parameter for core file patterns.
* Use a command file for gdb instead of the -ex option
The web transaction and Digest::SHA changes have allowed the removal of
a couple of long-standing uglinesses on the system. In almost all
cases, the config parameter "aux_path" and the separate
run_web_transaction.pl script are now redundant (the exception is older
Lib/
* ldapobject.ReconnectLDAPObject._apply_last_bind() now sends
anonymous simple bind request even if the calling application
did not to provoke ldap.SERVER_DOWN in method reconnect()
* ldapobject.ReconnectLDAPObject.reconnect() now also catches
ldap.TIMEOUT exception after reconnection attempt
* Several other fixes for ldapobject.ReconnectLDAPObject
Upstream changes:
0.806 (06.08.2013) - John Siracusa <siracusa@gmail.com>
* Updated iterator leak test to work on perl 5.17.* and later (RT 86000)
0.805 (03.10.2013) - John Siracusa <siracusa@gmail.com>
* Changed the recommended Oracle trigger PL/SQL to avoid sequence gaps.
(Patch by Tom Adamo.)
* Updated several Manager calls in bench.pl, adding the inject_results
parameter.
0.804 (02.01.2013) - John Siracusa <siracusa@gmail.com>
* Fixed some test failures on perl 5.16.2, mysql 5.5.29, and DBD::Pg 2.19.3.
0.803 (01.04.2013) - John Siracusa <siracusa@gmail.com>
* Make char column's parse_value() method honor a column's overflow
attribute when handling column values that are too long.
* Correct length value in column overflow error messages.
0.802 (01.03.2013) - John Siracusa <siracusa@gmail.com>
* Make varchar column's parse_value() method honor a column's overflow
attribute when handling column values that are too long.
0.801 (11.24.2012) - John Siracusa <siracusa@gmail.com>
* Fixed "DBD::Informix::st execute failed: SQL: -255: Not in transaction"
errors in the test suite. (Patch by Sergey Leschenko.)
0.800 (09.09.2012) - John Siracusa <siracusa@gmail.com>
* Correct tests to account for the Loader's init_db generation fix
in 0.799 behavior (RT 79526)
0.799 (08.10.2012) - John Siracusa <siracusa@gmail.com>
* Added column type mappings for varchar2, nvarchar, and nvarchar2.
(Suggested by Chris Campise)
* Fixed some typos in the Loader documentation (RT 78860)
* Fixed a Loader bug that caused the base class's init_db method to
be ignored (RT 78571)
0.798 (04.04.2012) - John Siracusa <siracusa@gmail.com>
* Fixed a typo in the Rose::DB::Object::Manager documentation.
* Fixed a bug that caused save() not to throw an exception when
a transaction could not be started (Reported by jdv79)
* Converted some uses of each() to keys() to avoid iteration
state bugs (RT 75773)
* Corrected a broken POD link in the one-to-many relationship
documentation. (Reported by Nee)
Upstream changes:
0.771 (08.04.2013) - John Siracusa <siracusa@gmail.com>
* Documented the behavior of the dsn attribute when it has an explicit
value and attributes that contribute to the dsn are also set (RT 87487)
0.770 (11.24.2012) - John Siracusa <siracusa@gmail.com>
* Fixed "DBD::Informix::st execute failed: SQL: -255: Not in transaction"
errors in the test suite. (Patch by Sergey Leschenko.)
0.769 (05.25.2012) - John Siracusa <siracusa@gmail.com>
* Fixed (more) test failures due to DBD::SQLite not being installed.
0.768 (05.12.2012) - John Siracusa <siracusa@gmail.com>
* Fixed test failures due to DBD::SQLite not being installed.
0.767 (05.01.2012) - John Siracusa <siracusa@gmail.com>
* Fixed some bugs that could cause connect_options not to be honored.
* Fixed some incorrectly failing handle_error tests.
* Updated Rose::DB::Oracle to honor NLS_*_FORMAT environment variables
for dates.
Upstream changes:
Changes in DBI 1.628 - 22nd July 2013
Fixed missing fields on partial insert via DBI::DBD::SqlEngine
engines (DBD::CSV, DBD::DBM etc.) [H.Merijn Brand, Jens Rehsack]
Fixed stack corruption on callbacks RT#85562 RT#84974 [Aaron Schweiger]
Fixed DBI::SQL::Nano_::Statement handling of "0" [Jens Rehsack]
Fixed exit op precedence in test RT#87029 [Reni Urban]
Added support for finding tables in multiple directories
via new DBD::File f_dir_search attribute [H.Merijn Brand]
Enable compiling by C++ RT#84285 [Kurt Jaeger]
Typo fixes in pod and comment [David Steinbrunner]
Change DBI's docs to refer to git not svn [H.Merijn Brand]
Clarify bind_col TYPE attribute is sticky [Martin J. Evans]
Fixed reference to $sth in selectall_arrayref docs RT#84873
Spelling fixes [Ville Skyttä]
Changed $VERSIONs to hardcoded strings [H.Merijn Brand]
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)
== v0.15.0 [2013-03-03] Michael Granger <ged@FaerieMUD.org>
Bugfixes:
- Fix segfault in PG::Result#field_values when called with non String value.
- Fix encoding of messages delivered by notice callbacks.
- Fix text encoding for Connection#wait_for_notify and Connection#notifies.
- Fix 'Bad file descriptor' problems under Windows: wrong behaviour of
#wait_for_notify() and timeout handling of #block on Ruby 1.9.
Documentation fixes:
- conn#socket() can not be used with IO.for_fd() on Windows.
Enhancements:
- Tested under Ruby 2.0.0p0.
- Add single row mode of PostgreSQL 9.2.
- Set fallback_application_name to programm name $0. Thanks to Will Leinweber
for the patch.
- Release Ruby's GVL while calls to blocking libpq functions to allow better
concurrency in threaded applications.
- Refactor different variants of waiting for the connection socket.
- Make use of rb_thread_fd_select() on Ruby 1.9 and avoid deprecated
rb_thread_select().
- Add an example of how to insert array data using a prepared statement (#145).
- Add continous integration tests on travis-ci.org.
- Add PG::Result#each_row for iterative over result sets by row. Thanks to
Aaron Patterson for the patch.
- Add a PG::Connection#socket_io method for fetching a (non-autoclosing) IO
object for the connection's socket.
Specs:
- Fix various specs to run on older PostgreSQL and Ruby versions.
- Avoid fork() in specs to allow usage on Windows and JRuby.
This is a bugfix release, sending out a series of fixes that have accumulated as version 0.8.0's release is imminent.
Fixes in this version include issues related to the Oracle, SQL Server, MySQL, and Google App Engine dialects, as well as a few schema related and ORM related fixes.
2012-12-02: Added new functions
* sleep
* clear_bindings
Really old operating system distributions may have had problems
linking these functions, but it seems that reasonably recent
ones support them.
2012-11-19: Added missing .mldylib file for shared library support.
pkgsrc change: no need to patch gemspec any more.
Wed Mar 13 2013 version 0.99995 released
* added ODBC::Database.use_sql_column_name= flag to switch
usage of SQLColAttributes(SQL_COLUMN_LABEL) to
SQLColAttributes(SQL_COLUMN_NAME) on per connection basis
* mysql_upgrade now verifies that the server version matches the version against which it was compiled, and exits if there is a mismatch. In addiion, a --version-check option permits specifying whether to enable version checking (the default), or disable checking if given as --skip-version-checking.
* Bugs Fixed
* mysql_upgrade now verifies that the server version matches the version against which it was compiled, and exits if there is a mismatch. In addiion, a --version-check option permits specifying whether to enable version checking (the default), or disable checking if given as --skip-version-checking.
* Bugs Fixed
to address issues with NetBSD-6(and earlier)'s fontconfig not being
new enough for pango.
While doing that, also bump freetype2 dependency to current pkgsrc
version.
Suggested by tron in PR 47882
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.
