GNATS was designed as a tool for software maintainers. It consists of several
utilities which, when used in concert, formulate and administer a database of
Problem Reports grouped by site-defined problem categories. It allows a
support organization to keep track of problems (hence the term Problem Report)
in an organized fashion. Essentially, GNATS acts as an active archive for
field-separated textual data.
Changes:
* changed DB and DBEnv set_get_returns_none() default from 1 to 2.
* cleaned up compatibility iterator interface.
* the legacy compatibility dict-like interface now support iterators
and generators and allows multithreaded access to the database.
* fixed a tuple memory leak when raising "object has been closed"
exceptions for DB, DBEnv and DBCursor objects. I doubt much
previous code triggered this.
* use of a closed DBCursor now raises a DBCursorClosedError exception
subclass of DBError rather than a boring old DBError.
* added DBCursor.get_current_size() method to return the length in bytes
of the value pointed to by the cursor without reading the actual data.
* Standalone pybsddb builds now use a _pybsddb dynamic/shared library
rather than _bsddb. This allows for pybsddb to be built, installed
and used on python >= 2.3 which includes an older version of pybsddb
as its bsddb library.
* Can now compile and link with BerkeleyDB 4.2.x (when its released).
* the legacy bsddb module supports the iterator interface on python 2.3.
* Support the DBEnv.set_shm_key() method.
* Fixed setup.py include/{db4,db3} header file searching (SF bug #789740).
provided by Michal Pasternak in PR 24657
What's new in ZODB3 3.2.1?
==========================
Release-date: 12-Feb-2004
The storage comparison matrix (Doc/storages.html) was updated. It
now has current information about Adaptable Persistence (Ape):
http://hathaway.freezope.org/Software/Ape.
What's new in ZODB3 3.2.1 release candidate 1?
==============================================
Release-date: 20-Jan-2004
FileStorage
-----------
Fixed a serious bug in the new pack implementation. If pack was
called on the storage and passed a time earlier than a previous pack
time, data could be lost. In other words, if there are any two pack
calls, where the time argument passed to the second call was earlier
than the first call, data loss could occur. The bug was fixed by
causing the second call to raise a StorageError before performing any
work.
ZEO
---
Fixed a bug in the ZEO authentication implementation that could cause
a properly authenticated connection to fail unexpectedly with a
ValueError -- "Received message without HMAC."
Fixed a bug in the ZEO server's getInvalidations() method. If it had
the requested invalidations, it would send all the invalidations in
its queue rather than just the requested ones. This didn't affect
correctness of the cache, but did cause it to throw out valid data.
Fixed a bug that prevented the -m / --monitor argument from working.
Fixed and enhanced the zeopasswd.py script. It now runs as a script
and supports command-line arguments for all the options that can be
specified in the configuration file.
What's new in ZODB3 3.2.1 beta 1
================================
Release-date: 18-Nov-2003
This code in this release should be identical to the code in Zope
2.7.0 beta 3.
Changed the ZEO server and control process to work with a single
configuration file; this is now the default way to configure these
processes. (It's still possible to use separate configuration files.)
The ZEO configuration file can now include a "runner" section used by
the control process and ignored by the ZEO server process itself. If
present, the control process can use the same configuration file.
Fixed a performance problem in the logging code for the ZEO protocol.
The logging code could call repr() on arbitrarily long lists, even
though it only logged the first 60 bytes; worse, it calls repr() even
if logging is currently disabled. Fixed to call repr() on individual
elements until the limit is reached.
ReadConflictErrors have an experimental new method, ignore(). If a
database connection raises a read conflict, the current transaction
was eventually be aborted. If the ignore() method is called, it will
allow a transaction to commit after receiving a read conflict. This
method should be used with great care, because ignoring read conflicts
may allow inconsistent data to be written to the database.
Several bare string exceptions were changed to raise exception
objects. All these exceptions were in fairly obscure parts of the
code.
Bug fix for Acquisition in ExtensionClass. Zope Collector #1056:
aq_acquire() ignored the default argument.
The zdaemon.Daemon module was removed, because it is no longer used by
zdaemon.
The ZEO test suite is more robust. A variety of small changes were
made that make it less likely to fail on slow or loaded machines.
and slightly modified by me.
IndexedCatalog is an extension to the Zope Object Database (ZODB) that
provides indexing and allows queries for objects based on attributes.
Which is accomplished by indexing all fields by type
(string/integer/float) and by a simple query language.
improved by wiz@, and slightly modified by me.
The DBI Shell, or dbish, is a command-line tool that allows you to run
arbitrary SQL statements and diagnostics against databases without
needing to write a complete Perl program.
the PKGREVISION. The fix was provided by Nick Hudson and modifies
the libldap initialization routine to call the GNU pth initialization
routine before using it. The resulting slapd/slurpd passes the test
suite included in the OpenLDAP sources. This fixes PR 24473.
support. The slapd built without threads passes all of its test except
for the replication test, which is because slurpd is not built (slurpd
requires threads). Bump the PKGREVISION.
This is in response to PR 24473. As a debugging aid in case someone
attempts to really fix the PR, if _OPENLDAP_REQUIRE_THREADS is "yes",
then openldap will forcibly build using GNU pth if native threads
aren't available.
Changes since version 2.0:
==========================
item 2.01 (07 July 2002)
New testing method MLDBM::_compare($a, $b) used in t/*.t
scripts to verify data structures are identical. In
perl 5.8.0 RC2, the order of hashes changed, making the prior
hard coded test case string comparisons invalid, so created
this more flexible method for testing that should work in
future releases, without relying on specific hash ordering.
Many programs and desktops use the MIME system to represent the types of
files. Frequently, it is necessary to work out the correct MIME type for
a file. This is generally done by examining the file's name or contents,
and looking up the correct MIME type in a database.
For interoperability, it is useful for different programs to use the same
database so that different programs agree on the type of a file, and new
rules for determining the type apply to all programs.
This package contains the core database of common types and the
update-mime-database command used to extend it.
20031217. Changes from version 2.1.22 include many bug fixes including
memory leaks, adding lutil_passwd extensions, and adding config file
keywords to control the replication daemon.
This module is built using SWIG (http://www.swig.org) to produce a
Python module that maps to the Berkeley DB XML C++ API fairly closely.
At present, separate documentation for the Python API is not provided.
Refer to the C++ API documentation and the Python examples for more
information, or contact Sleepycat Support (support@sleepycat.com).
Berkeley DB XML is an application-specific native XML data manager
built on Berkeley DB, the world's most widely deployed data management
engine. Berkeley DB XML provides fast, reliable, scalable and
cost-effective storage and retrieval for native XML data and
semi-structured data.
Berkeley DB XML is supplied as a library that links directly into the
application's address space. This provides superior performance by
eliminating bottlenecks that occur in client-server systems.
