D. J. Bernstein's constant database library adapted as a python
extension module. Like GDBM and kin, cdb files map keys to values.
The file format boasts wickedly fast lookups and atomic updates.
* Extra checks of search arguments for possible SQL injection attacks
* Remove excess parentheses in debug SQL
* Fix parsing of foo.* in SQLA::Tree
* Fix bindtype fail when using -between with arrayrefref literals
* Add handling for NULL for -in
* The -nest operator has entered semi-deprecated status and has been
undocumented. Please do not use it in new code
* Production release, no changes from 1.32_04
Changes 1.32_04:
* Updated to SQLite 3.7.6.3
* Made util/getsqlite.pl state that it needs fixing to work for
SQLite 3.7.5+ when it dies at the last step, and outline what the
user needs to do manually instead, until getsqlite is fixed
Changes 1.32_03:
* Updated to SQLite 3.7.6.2
* Resolved 67843 for DBD-SQLite: savepoint rollback alters AC state
Changes 1.32_02:
* Updated to SQLite 3.7.5
* Resolved 65267 for DBD-SQLite: Add RTree support option;
skip fts3/metadata tests if those features are disabled
* Resolved 65267: Add RTree support option
* Added sqlite_see_if_its_a_number database handle attribute
to deal with issues caused by (quoted) bind values against
numbers such as return values from a function etc.
* Recently introduced test sql_type_cast.t cannot work with DBI less
than 1.611.
* Minor change to Makefile.PL to avoid use of unitialised warning on
$ENV{LD_LIBRARY_PATH} in warning when it is not set.
Changes 1.30_7:
* Some time ago (I don't know when) a few internal errors generated by
DBD::ODBC got ignored. There are about 5 of them but I seriously
doubt anyone would hit any other than the data truncated error
(which is reported by the ODBC driver anyway) and "no select
statement currently executing". You can see rt_68720.t in the t
directory for an example of the latter.
* An extra argument has been added to the sub associated with
odbc_err_handler. The arguments passed to the odbc_err_handler are
now state (string), error (string), native error code (number) and
the status returned from the last ODBC API. The status will be
SQL_ERROR (-1) for errors or SQL_SUCCESS_WITH_INFO (1) for
informational messages.
* Changed incorrect verion number
Changes 1.40:
* Fixed bug rt44591 second preapre giving an error
* Fixed bug rt57981 warnings during clone
* Fixed bug rt63191 Synopsis errors
* Fixed bug rt66813 Google's group link in the POD
* Fixed spurious dbi_profile lines written to the log when
profiling is enabled and a trace flag, like SQL, is used.
* Fixed to recognize SQL::Statement errors even if instantiated
with RaiseError=0
* Fixed RT-61513 by catching attribute assignment to tied table access
interface
* Fixing some misbehavior of DBD::File when running within the Gofer server.
* Fixed compiler warnings RT-62640
* Optimized connect() to remove redundant FETCH of \%attrib values.
* Improved initialization phases in DBI::DBD::SqlEngine
* Added DBD::Gofer::Transport::corostream. An experimental proof-of-concept
transport that enables asynchronous database calls with few code changes.
It enables asynchronous use of DBI frameworks like DBIx::Class.
* Added additional notes on DBDs which avoid creating a statement in
the do() method and the effects on error handlers
* Adding new attribute "sql_dialect" to DBI::DBD::SqlEngine to allow
users control used SQL dialect (ANSI, CSV or AnyData), defaults to CSV
* Add documentation for DBI::DBD::SqlEngine attributes
* Documented dbd_st_execute return
* Fixed typo in InactiveDestroy
This is bug fix release. Since whole changes are too many to write here,
please refer http://dev.mysql.com/doc/refman/5.1/en/news-5-1-58.html.
Especially, some important one for related to us.
* On FreeBSD 64-built builds of the embedded server, exceptions were not
prevented from propagating into the embedded application. (Bug #38965,
Bug #11749418)
This is major feature update which requires at least PHP 5.2.0 and
MySQL 5.0. It features a new user interface and uses MySQL for
authentication and access control.
The update was necessary as "phpmyadmin" 2.11 is no longer supported:
http://sourceforge.net/news/?group_id=23067&id=301992
Lib/
* Mostly corrected/updated __doc__ strings
Doc/
* Corrected rst files
* Added missing modules, functions, classes, methods, parameters etc.
at least as auto-generated doc
Changes 2.4.2:
Logging:
* pprint.pformat() is now used when writing method/function
arguments to the trace log
ldap.schema.subentry:
* SubSchema.__init__() now has new key-word argument check_uniqueness
which enables checking whether OIDs are unique in the subschema subentry
* Code-cleaning: consequent use of method SubSchema.getoid() instead of
accessing SubSchema.name2oid directly.
* SubSchema.getoid() and SubSchema.getoid() now have key-word argument
raise_keyerror=0 and raise KeyError with appropriate description.
* The undocumented --all option for perror is deprecated and will be removed in
MySQL 5.6.
Bugs Fixed:
* InnoDB Storage Engine: A failed CREATE INDEX operation for an InnoDB table
could result in some memory being allocated and not freed. This memory leak
could affect tables created with the ROW_FORMAT=DYNAMIC and
ROW_FORMAT=COMPRESSED settings.
* Partitioning: Auto-increment columns of partitioned tables were checked even
when they were not being written to. In debug builds, this could lead to a
crash of the server.
* Partitioning: The UNIX_TIMESTAMP() function was not treated as a monotonic
function for purposes of partition pruning.
* Replication: If a LOAD DATA INFILE statement—replicated using statement-based
replication—featured a SET clause, the name-value pairs were regenerated
using a method (Item::print()) intended primarily for generating output for
statements such as EXPLAIN EXTENDED, and which cannot be relied on to return
valid SQL. This could in certain cases lead to a crash on the slave.
* To fix this problem, we now name each value in its original, user-supplied
form, and use that to create LOAD DATA INFILE statements for statement-based
replication.
* Previously, an inappropriate error message was produced if a multiple-table
update for an InnoDB table with a clustered primary key would update a table
through multiple aliases, and perform an update that may physically move the
row in at least one of these aliases. Now the error message is: Primary
key/partition key update is not allowed since the table is updated both as
'tbl_name1' and 'tbl_name2'
* ALTER TABLE {MODIFY|CHANGE} ... FIRST did nothing except rename columns if
the old and new versions of the table had exactly the same structure with
respect to column data types. As a result, the mapping of column name to
column data was incorrect. The same thing happened for ALTER TABLE DROP
COLUMN, ADD COLUMN statements intended to produce a new version of table with
exactly the same structure as the old version.
* Incorrect handling of metadata locking for FLUSH TABLES WITH READ LOCK for
statements requiring prelocking caused two problems:
* Execution of any data-changing statement that required prelocking (that is,
involved a stored function or trigger) as part of transaction slowed down
somewhat all subsequent statements in the transaction. Performance in a
transaction that periodically involved such statements gradually degraded
over time.
Also fixed INSTALL_PROGRAM patch to not break install-sh.
Changes since 1.0.1
============================================================================
HTTP Interface:
* Native SSL support.
* Added support for HTTP range requests for attachments.
* Added built-in filters for '_changes': '_doc_ids' and '_design'.
* Added configuration option for TCP_NODELAY aka "Nagle".
* Allow POSTing arguments to '_changes'.
* Allow 'keys' parameter for GET requests to views.
* Allow wildcards in vhosts definitions.
* More granular ETag support for views.
* More flexible URL rewriter.
* Added support for recognizing "Q values" and media parameters in
HTTP Accept headers.
* Validate doc ids that come from a PUT to a URL.
Externals:
* Added OS Process module to manage daemons outside of CouchDB.
* Added HTTP Proxy handler for more scalable externals.
Replicator:
* Added '_replicator' database to manage replications.
* Fixed issues when an endpoint is a remote database accessible via SSL.
* Added support for continuous by-doc-IDs replication.
* Fix issue where revision info was omitted when replicating attachments.
* Integrity of attachment replication is now verified by MD5.
Storage System:
* Multiple micro-optimizations when reading data.
View Server:
* Added CommonJS support to map functions.
* Added 'stale=update_after' query option that triggers a view update after
returning a 'stale=ok' response.
* Warn about empty result caused by 'startkey' and 'endkey' limiting.
* Built-in reduce function '_sum' now accepts lists of integers as input.
* Added view query aliases start_key, end_key, start_key_doc_id and
end_key_doc_id.
Futon:
* Added a "change password"-feature to Futon.
URL Rewriter & Vhosts:
* Fix for variable substituion
* Support for Berkeley DB 5.2.
* Support for the newly available replication manager events:
DB_EVENT_REP_SITE_ADDED, DB_EVENT_REP_SITE_REMOVED,
DB_EVENT_REP_LOCAL_SITE_REMOVED, DB_EVENT_REP_CONNECT_BROKEN,
DB_EVENT_REP_CONNECT_ESTD, DB_EVENT_REP_CONNECT_TRY_FAILED,
DB_EVENT_REP_INIT_DONE.
* New Object: "DB_SITE". Support for all its methods.
* Parameters for "DB_SITE->set_config()": DB_BOOTSTRAP_HELPER,
DB_GROUP_CREATOR, DB_LEGACY, DB_LOCAL_SITE, DB_REPMGR_PEER.
* Support for some stuff in the new "Dynamic Environment Configuration":
DB_MEM_LOCK, DB_MEM_LOCKOBJECT, DB_MEM_LOCKER, DB_MEM_LOGID,
DB_MEM_TRANSACTION, DB_MEM_THREAD.
* Add "bytes" to "DBEnv_memp_stat()".
Modules:
* New LDAP option OPT_X_TLS_PACKAGE available in OpenLDAP 2.4.26+
to determine the name of the SSL/TLS package OpenLDAP was
built with
Lib/
* ldap.modlist.modifyModlist(): New key-word argument
case_ignore_attr_types used to define attribute types for which
comparison of old and new values should be case-insensitive
* Minor changes to which data is sent to debug output for various
trace levels
* Now tag [1] is used in ldap.extop.dds.RefreshResponse in
compliance with RFC 2589 (fix available for OpenLDAP ITS-6886)
* New sub-module ldap.controls.sessiontrack implements request control
as described in draft-wahl-ldap-session (needs pyasn1_modules)
Changes since 2.4.0:
* OpenLDAP 2.4.11+ required to build
* Support for extracting LDAPv3 extended controls in
LDAP_RES_SEARCH_ENTRY responses
(see SF-2829057, thanks to Rich)
* Generic support for LDAPv3 extended operations (thanks to Rich)
Lib/
* new class API in ldap.controls, not backwards-compatible!
* new sub-modules for ldap.controls, some require pyasn1 and pyasn1_modules
* New methods LDAPObject.result4() and LDAPObject.extop_result()
* New (optional) class ldap.controls.AssertionControl
* New helper module ldap.logger contains file-like object which
sends trace messages to logging.log()
* Removed non-functional method LDAPObject.set_cache_options()
* Removed unused dictionary ldap.controls.knownLDAPControls
Modules/
* ldapcontrol.c: Fixed encode_assertion_control() and function is no longer
hidden behind ifdef-statement
* Fix a bug causing PRAGMA case_sensitive_like statements compiled using
sqlite3_prepare() to fail with an SQLITE_SCHEMA error.
Changes 3.7.7:
* Add support for URI filenames
* Add the sqlite3_vtab_config() interface in support of ON CONFLICT clauses
with virtual tables.
* Add the xSavepoint, xRelease and xRollbackTo methods in virtual tables in
support of SAVEPOINT for virtual tables.
* Update the built-in FTS3/FTS4 and RTREE virtual tables to support ON CONFLICT
clauses and REPLACE.
* Avoid unnecessary reparsing of the database schema.
* Added support for the FTS4 prefix option and the FTS4 order option.
* Allow WAL-mode databases to be opened read-only as long as there is an
existing read/write connection.
* Added support for short filenames.
* CMake configuration support on Linux now provides a boolean ENABLE_GCOV
option to control whether to include support for gcov.
* InnoDB now permits concurrent reads while creating a secondary index.
* Client programs now display more information for SSL errors to aid in
diagnosis and debugging of connection problems.
* In the audit plugin interface, the event_class member was removed from the
mysql_event_general structure and the calling sequence for the notification
function changed. Originally, the second argument was a pointer to the event
structure. The function now receives this information as two arguments: an
event class number and a pointer to the event. Corresponding to these
changes, MYSQL_AUDIT_INTERFACE_VERSION was increased to 0x0300.
* The plugin_audit.h header file, and the NULL_AUDIT example plugin in the
plugin/audit_null directory have been modified per these changes. See
Section 21.2.4.7, “Writing Audit Plugins”.
* Bug fixes.
## 0.10.6 2011-05-22
Bugfixes
* Fix an issue on some platforms when multiple DO drivers are loaded
## 0.10.5 2011-05-03
Bugfixes
* Fix an issue with DateTime
## 0.10.4 2011-04-28
New features
* Add save point to transactions (all)
* JRuby 1.9 mode support (encodings etc.)
Bugfixes
* Fix bug when using nested transactions in concurrent scenarios (all)
* Use column aliases instead of names (jruby)
* DST calculation fixes (all)
Other
* Refactor to DRY up the adapters (all)
* Many style fixes
* Switch back to RSpec
## 0.10.3 2011-01-30
* Reworked transactions
* Fix a DST bug that could cause datetimes in the wrong timezone
## 0.10.6 2011-05-22
Bugfixes
* Fix an issue on some platforms when multiple DO drivers are loaded
## 0.10.5 2011-05-03
Bugfixes
* Fix an issue with DateTime (do\_sqlite3)
## 0.10.4 2011-04-28
New features
* Add save point to transactions (all)
* JRuby 1.9 mode support (encodings etc.)
Bugfixes
* Fix segfault when no tuples are returned from a non select statement (do\_postgres)
* Fix bug when using nested transactions in concurrent scenarios (all)
* Use column aliases instead of names (jruby)
* DST calculation fixes (all)
* Attempt to add better support for ancient MySQL versions (do\_mysql)
* Fix handling sub second precision for Time objects (do\_postgres)
Other
* Refactor to DRY up the adapters (all)
* Many style fixes
* Switch back to RSpec
## 0.10.3 2011-01-30
* Reworked transactions
* Fix a DST bug that could cause datetimes in the wrong timezone
v0.11.1
- Add counter support for Cassandra 0.8. (Thanks Swrve team!)
- Add additional rake tasks to start and stop cassandra in the background.
- Fix issue with non-utf8 column names not being encoded/decoded properly.
- Add way to specify a default read/write consistency.
- Consolidate 0.7 and 0.8 functions, and move 0.6 specific functions into lib/cassandra/0.6/
- Use 0.8-rc1 as 0.8 install target.
- Updated get_index_slices API to allow passing an array of hashes instead of IndexClause instance. (Maintains backward compatibility.)
- Fix permissions issue.
v0.11.0
- Remove direct thrift dependency. Allow thrift_client to require it.
- Add functions for each and each_key to iterate through key ranges.
- Add function for get_range_keys which returns an array of keys in a given range.
- Changed the return value of get_range to an OrderedHash.
- Change get_range to accept both a range of keys and a range of columns.
- Add batched range support to get_range and add get_range_batch.
v0.10.0 Major Update (rjackson)
- Update Rakefile to install 0.6.13, 0.7.4, 0.8.0-beta1 to ~/cassandra/cassandra-VERSION
- Add data:load task to Rakefile for creating the schema required for the tests
- Default the Rakefile to use 0.8-beta1
- Setup test suite to work on 0.6.13, 0.7.4, and 0.8.0-beta1
- All tests pass for all supported (0.6.13, 0.7.4, 0.8.0-beta1) versions.
- Added Support for 0.8-beta1
- Changed get_index_slices to return a hash of rows
- Updated Cassandra::Mock to pass all tests for each Cassandra version
v0.9.2 fix bug with deletions in batch mutations
v0.9.1 Support for secondary indexing. (jhermes)
Fix bug in mock where we didn't support range queries. (therealadam)
Support deletes in batch mutations. [blanquer]
v0.9.0 cassandra 0.7 compat
DataMapper 1.1.0 released
I¡Çm pleased to announce that we have released DataMapper 1.1.
This has been one of the most enjoyable releases in recent memory. The
community rallied together and compared to the previous release we had at
least 3-4x more people submitting patches and working together to get this
release ready.
DataMapper 1.1 brings several minor API changes, warranting the minor version
bump, and closes 52 tickets in Lighthouse. There have been many performance
improvements, some closing bottlenecks that result in as much as a 20x speedup
from the 1.0.2 behaviour.
As part of the bug fixing process we¡Çve refactored some of the objects we use
internally to group relationships and dependencies and removed methods and
classes that were deprecated in 1.0.
For more changes in detail, please refer:
http://datamapper.org/articles/datamapper-110-released.html.
