Pages Navigation Menu

KitaroDB Release Notes

KitaroDB Release Notes

Version 2.0

Released May 2013

  • Added support for Windows Phone 8 development.
  • Increased the maximum record size from 64K (minus 32 bytes for overhead) to 2 GB (which includes from 32 bytes to 64K of overhead). And we added a DB.Create[Async] parameter (recordLength) that enables you to limit record size to something less than 2 GB.
  • Increased the maximum size of a KitaroDB database from 100 terabytes to 256 terabytes. And we added a parameter (maxDBSize) to DB.Create[Async] that enables you to limit the size to something less than 256 terabytes.
  • Added support for global record file addresses (GRFAs) and record file addresses (RFAs). GRFAs are 10-byte binary identifiers that uniquely identify the location and contents of a record in a KitaroDB database. You can use GRFAs to access previously-read records and to detect when a record has changed. A GRFA consists of a six-byte record file address (RFA) and four additional bytes that change when the contents of the record change. A record’s RFA remains the same for the life of the record, so you can use this to access a record whether or not its content has changed.
  • Added support for binary intrusive keys and segments.
  • Added DBReadFlag enumerations MatchGreater and MatchGTEQ for “greater than” and “greater than or equal to” comparisons when positioning cursors.
  • Added support for manual cursor unlocking, and we added a one-second pause before generating an error when attempting to lock the record or key-value pair at the current cursor position. Previously, you could use DBReadFlags enumerations to specify either no locking (NoLock) or automatic locking/unlocking (AutoLock). Now you can also use one or more of the following new DBReadFlags enumerations:
    • ManualLock, which locks the record or key-value pair at the cursor position, but doesn’t automatically unlock it. You can now unlock it with the new DBCursor.UnlockGRFA[Async] method.
    • WaitOnLock, which waits up to one second before generating an error when attempting to lock a record or key-value pair.
  • Fixed a number of bugs.
  • IMPORTANT NOTES AND WARNINGS
    • KitaroDB 2.0 can access files created with earlier versions of KitaroDB, but this access is read-only.
    • By default, KitaroDB now creates database files with .kdb and .kd1 extensions (rather than .ism and .is1).
    • The kdbutl utility now generates a log file with the name kdbutl.log rather than isutl.log.