| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
New Features/Improvements
-------------------------
Added support for global message prefixes.
Added Replication Manager write forwarding, which enables a client to perform simple put and delete operations by forwarding them to the master.
Improved the way we mark a password as consumed.
Added support for IPv6.
Added support for Java 8.
Added support for ARMv7 and above, and for ARM64. ARMv6 and below are no longer supported.
Add a new SMP-optimized data model that is especially valuable for highly multithreaded applications. A sliced Berkeley DB instance contains a collection of related Berkeley DB environments, known as slices, each containing a disjoint subset of records. Transactional consistency is individually maintained within each slice, rather than across multiple slices.
DB now supports the client-server architecture by providing a stand-alone server program and Java client driver APIs. The server program offers remote access to DB features. The client driver APIs provide building blocks for applications that communicate with a database server. Multiple client applications can communicate with a single server simultaneously.
Enabled support of the SQLite user authentication extension.
Added Visual Studio 2012 projects.
Encryption and checksum can now be enabled with external files (formerly known as BLOBs). Note that only the data stored in the database will be encrypted and checksum protected. The data in the external files will not be encrypted or checksum protected.
The BLOB files feature has been renamed external files to reduce confusion with the SQL BLOB datatype. The BLOB related functions have been deprecated, and replaced with new function names; for example, ext_file_threshold has replaced blob_threshold, and blob_threshold is deprecated. See the Upgrading section of the documentation for more details.
|
|
avoid the former for C++.
|
|
was being checked and not the gcc toolchain's use of __aarch64__.
db6 does support the 64-bit ARM platform.
previous condition put back as it was prior.
ride PKGREVISION bump
|
|
build on aarch64 Linux
Also add '--enable-dbm' to CONFIGURE_ARGS (legacy dbm interface) in
order to be compatible with db4 builds which happens to fix obscure
build errors on aarch64 Linux with packages such as python27.
bump PKGREVISION to pick up change
|
|
Problems found with existing distfiles:
distfiles/D6.data.ros.gz
distfiles/cstore0.2.tar.gz
distfiles/data4.tar.gz
distfiles/sphinx-2.2.7-release.tar.gz
No changes made to the cstore or mariadb55-client distinfo files.
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
|
|
A 'salvage' (db_dump -r) no longer hangs on a corrupt database which contains a loop in an overflow item's chain of pages.
Remove +u1 compiler flag from the HP-UX build and fixed related alignment issue.
Fixed DB_RUNRECOVERY errors caused by pthreads-based mutexes.
Allow the failchk process to call __env_refresh when necessary.
DB->open() now detects invalid pagesizes sooner, avoiding a potential floating point exception when a purported database file has a pagesize of 0. Added a pre-verify step to the db_dump utility.
Fixed a bug that can cause DBcursor->get to return incorrect data when DB_GET_BOTH_RANGE flag is used.
Added support for Java 8.
Aborting a transaction no longer panics if a deadlock error occurs while freeing up the transaction's cursors.
Fixed a crash which could occur when multiple BDB SQL processes repeatedly open a database file.
Fixed a bug where db_printlog improperly handled a "No such file or directory" error condition.
Fixed a bug that could cause a master crash in the following cases: an unencrypted client attempts to join an encrypted replication group, or an encrypted client attempts to join an unencrypted replication group.
Fixed a bug that can cause a crash when DB_ENV->memp_stat() is called.
Added support for arm64.
Reduced the minimum hash table size.
Fixed a bug where file names were not displayed correctly when a file failed to open during backup.
Enabled cross compiling the JDBC driver.
Fixed a crash when writing to a SQL BLOB while txn_bulk is enabled.
DB->open() now detects invalid bt_minkey better, avoiding a potential floating point excetpion.
Removed EnvironmentConfig.setTxnNotDurable() and Environment.getTxnNotDurable() from the Java API. This flag cannot be set on environments.
|
|
|
|
Berkeley DB is an embeddable database system that supports keyed access to
data. The software is distributed in source code form, and developers can
compile and link the source code into a single library for inclusion
directly in their applications.
Developers may choose to store data in any of several different storage
structures to satisfy the requirements of a particular application. In
database terminology, these storage structures and the code that operates on
them are called access methods. The library includes support for the
following access methods:
* B+tree: Stores keys in sorted order, using either a programmer-supplied
ordering function or a default function that does lexicographical
ordering of keys. Applications may perform equality or range searches.
* Hashing: Stores records in a hash table for fast searches based on
strict equality. Extended Linear Hashing modifies the hash function
used by the table as new records are inserted, in order to keep buckets
underfull in the steady state.
* Fixed and Variable-Length Records: Stores fixed- or variable-length
records in sequential order. Record numbers may be immutable or
mutable, i.e., permitting new records to be inserted between existing
records or requiring that new records be added only at the end of the
database.
This package privides Berkeley DB 6 released under GNU AGPL3.
|
