Dbase32 0.6

Milestone information

Jason Gerard DeRose
Release registered:
No. Drivers cannot target bugs and blueprints to this milestone.  

Download RDF metadata


Assigned to you:
No blueprints or bugs assigned to you.
No users assigned to blueprints and bugs.
No blueprints are targeted to this milestone.
No bugs are targeted to this milestone.

Download files for this release

After you've downloaded a file, you can verify its authenticity using its MD5 sum or signature. (How do I verify a download?)

File Description Downloads
download icon dbase32-0.6.0.tar.gz (md5, sig) tarball 12
last downloaded 10 days ago
Total downloads: 12

Release notes 

Added new monotonic ID function `dbase32.log_id()`.

The first 4 bytes are from the time in seconds since the Unix Epoch, truncated to a 32 bit unsigned int (which wont overflow till the year 2106, although the point here is being *generally* monotonic, not storing a timestamp).

The remaining 11 bytes are from /dev/urandom. 120-bits in total, 88 of which are (presumably) of a high quality random nature.

The resulting 15 byte binary ID is then Dbase32 encoded, giving you a 24 byte UTF-8 ID.

By using a generally monotonic ID, the b-tree will tend to grow in a more space efficient manner compared to IDs where the leading bytes are random. Especially after a compaction, monotonic IDs will usually give you a dramatic space savings.

This sort of ID is aimed at event logging in Dmedia and Novacut, cases where having the IDs sort in roughly chronological order nicely matches the typically access pattern.


This release does not have a changelog.

0 blueprints and 0 bugs targeted

There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.

This milestone contains Public information
Everyone can see this information.