 |
Version 1.4.2
|
|
Version 1.4.2
|
A new member, WT_COMPRESSOR::compress_raw, was added to the WT_COMPRESSOR extension API. Applications using the WT_COMPRESSOR extension API should add a NULL as the second field of that structure.
The WT_SESSION::create method's checksum configuration string has been changed from a boolean type to a string type. Applications using the checksum configuration string should change a value of true to the string on, and a value of false to the string off or the string uncompressed.
The underlying file formats changed in the 1.3.9 release; tables and files should be dumped and re-loaded into a new database.
The statistics key constants have been renamed to use all capitals, and use consistent prefixes to distinguish between connection statistics and statistics for data sources.
The installed WiredTiger extension library names changed to limit namespace pollution:
| Library | Previous Name | New Name |
|---|---|---|
| Bzip2 compression | bzip2_compress.a | libwiredtiger_bzip2.a |
| bzip2_compress.la | libwiredtiger_bzip2.la | |
| bzip2_compress.so | libwiredtiger_bzip2.so | |
| Snappy compression | snappy_compress.a | libwiredtiger_snappy.a |
| snappy_compress.la | libwiredtiger_snappy.la | |
| snappy_compress.so | libwiredtiger_snappy.so | |
| No-op compression | nop_compress.a | No longer installed |
| nop_compress.la | No longer installed | |
| nop_compress.so | No longer installed | |
| Reverse order collator | reverse_collator.a | No longer installed |
| reverse_collator.la | No longer installed | |
| reverse_collator.so | No longer installed |
The built-in compression name arguments to the WT_SESSION:create block_compressor configuration string changed for consistency:
| Extension | Previous Name | New Name |
|---|---|---|
| Bzip2 compression | "bzip2_compress" | "bzip2" |
| Snappy compression | "snappy_compress" | "snappy" |
The underlying file formats changed in the 1.3.5 release; tables and files should be dumped and re-loaded into a new database.
The checkpoint functionality supported by WT_SESSION::checkpoint and the snapshot functionality supported by WT_SESSION::sync have been merged into a single piece of functionality.
WT_SESSION.checkpoint
The WT_SESSION::checkpoint method's snapshot configuration string has been renamed to name. The name assigned to checkpoints without a specified name configuration is now "WiredTigerCheckpoint".
WT_SESSION.drop
In releases before 1.3, the WT_SESSION::drop method was used to delete snapshots. In 1.3, the functionality of deleting snapshots has been moved to the WT_SESSION::checkpoint method, specifically, snapshots are discarded using the WT_SESSION::checkpoint method's drop configuration string.
WT_SESSION.sync
The WT_SESSION::sync method has been removed from the 1.3 release; the functionality of creating an object snapshot has moved to the WT_SESSION::checkpoint method, specifically, creating a snapshot of a one or more objects is done using the WT_SESSION::checkpoint method's target configuration string.
wt drop -s
The -s option to the drop command for the wt command line utility has been removed, and object snapshots may no longer be removed from the command line.
-s options to the dump and list commands for the wt command line utility have been renamed to be -c. In releases before 1.3, the WT_SESSION::open_cursor method could duplicate cursors that were not positioned in an object; in 1.3, a cursor must be positioned in order to be duplicated.
In releases before 1.3, ending a transaction by calling the WT_SESSION::commit_transaction or WT_SESSION::rollback_transaction methods implicitly closed all open cursors; in 1.3, the cursors remain open, but are reset (discarding their positions and cursor values). This means applications must change to either close cursors explicitly, or rely on an eventual WT_SESSION::close or WT_CONNECTION::close methods to implicitly close open cursors.
In releases before 1.3, the default isolation level for transaction was snapshot, and the default isolation level for non-transaction operations was read-uncommitted; in 1.3, the default isolation level for all operations is read-committed.
The default can be overridden for a session using the isolation setting in WT_CONNECTION::open_cursor.
In releases before 1.3, the WT_SESSION::truncate method required cursors used for truncation of a cursor range to reference existing keys in the object; in 1.3, the WT_SESSION::truncate method has been changed to allow cursors to reference any valid key in the object's name space so applications may discard portions of the object name space without knowing exactly what records the object contains.
In releases before 1.3, the WT_CURSOR::equals method returned zero/non-zero to indicate cursor equality; in 1.3, the WT_CURSOR::equals method has been replaced with WT_CURSOR::compare, which compares two cursors and returns a cursor comparison status (less than 0, equal to 0, or greater than 0) depending on the cursors' key order.
The underlying file formats changed in the 1.3 release; tables and files should be dumped and re-loaded into a new database.