cruppstahl's blog

hamsterdb moves to github.com!

chris — Mon, 02 Aug 2010 19:50:49 +0000

I just imported the hamsterdb sources to a github repository.

There were a few reasons for this, mainly

I was fed up with repairing broken svn repositories, i had to use “svnadmin recover” every second week and afterwards i had to fix broken file permissions for the bdb logfiles. One repository was broken beyond repair.
I hope to make collaborating easier by moving to an open platform
github offers a lot of features (i.e. a Wiki) that i could utilise, and i am happy if someone else does the server maintenance for me

If you want to browse the sources, see the most recent changes or branch off your own hamsterdb then please go to http://github.com/cruppstahl/hamsterdb. Everyone’s invited

hamsterdb: release 1.1.5 UNSTABLE

chris — Sun, 25 Jul 2010 18:50:46 +0000

This release implements remote functionality over http. The protocol is implemented with Google’s Protocol Buffers, the client uses libcurl for network handling and the server is based on mongoose, an embedded micro http server.
The server interface is very simple, and the server can easily be embedded into an application.

There are no known bugs, but currently the remote functionality is only supported on Unix/Linux. The next version 1.1.6 will also support the new features on Win32; several other improvements are also pending for the next release: a unix daemon, a win32 service and some other minor issues.

Download the sources at http://hamsterdb.com/download.

hamsterdb-dotnet: release 0.0.3

chris — Mon, 19 Apr 2010 18:55:50 +0000

… is available for download, including most of the functionality in hamsterdb 1.1.4.

hamsterdb: release 1.1.4

chris — Fri, 16 Apr 2010 15:45:56 +0000

Version 1.1.4 is now available!

This is mainly a bugfix release, and in case you’re not haunted by these bugs, there’s no need for you to update.

First one: hamsterdb only supports one Transaction at a time, but nevertheless it was allowed to create temporary, unnamed Transactions while another one was already running. -> fixed

Second one: on win32, if you have a cache size of more than a gigabyte and fill up the cache then the non-paged memory pool can be exhausted. -> fixed

What else? some macros in the header file were renamed for consistency reasons, but the old macros still exist and source compatibility was not broken.

Everything’s available here: http://hamsterdb.com/download.

Next thing on the TODO list: update the .NET wrapper. And then finally implement remote access.

hamsterdb java wrapper: release 0.0.3

chris — Wed, 07 Apr 2010 19:12:04 +0000

I just released a new version of the java wrapper, after neglecting things for a long time. Most of the current functionality is now available.

Next on the TODO list is the .NET wrapper.

Everything’s available for download, including precompiled win32/win64 libraries.

hamsterdb: release 1.1.3!

chris — Tue, 16 Mar 2010 20:34:19 +0000

Four weeks after 1.1.2, here’s the next! The headline is “partial read/write” - records can now be read or written partially. This can be a benefit if your records are REALLY big. But it will also enable you to “stream” records.

This feature caused changes in the layout of ham_record_t. Therefore the ABI of hamsterdb is no longer compatible (but the API and the database file format are compatible). To avoid crashes, i incremented the libtool version and embedded the hamsterdb version in the win32 dll/lib filenames.

Also, i fixed a performance related bug in the caching - 1.1.3 should therefore be much faster than 1.1.2.

I added a new function “ham_get_env” to retrieve the Environment handle of a Database. (This handle always exists, even if it was not created explicitely).

Everything’s available on http://hamsterdb.com/download.

Next big feature will be a remote client/server setup. And i’ll FINALLY update the java/python/.NET wrappers.

Presentation for OpenHUG Munich

chris — Fri, 26 Feb 2010 06:40:01 +0000

Yesterday i was invited to give a short presentation about hamsterdb for OpenHUG (Hadoop User Group) in Munich.

And i really enjoyed this meeting - most of the audience was coming from the Web 2.0/Enterprise area, where i do not have that many insights.

The OpenHUG was organized by Bob Schulze - thanks for the invitation, and thank you for the beer

Here’s the presentation.

hamsterdb

hamsterdb: release 1.1.2!

chris — Sat, 13 Feb 2010 20:41:44 +0000

Release 1.1.2 is available for download!

New features

Duplicate keys can now be sorted. Sorting has to be enabled with HAM_SORT_DUPLICATES. The default collation can be overwritten with ham_set_duplicate_compare_func.

Bugfixes

If multiple Databases in an Environment are open, an open Transaction was not immediately closed when the first Database was closed (with ham_close)
If multiple Databases in an Environment are open, and just one Database was closed, then the pages of this Database were not flushed correctly
Fixed crash on Linux 64bit/gcc 4.4 with compiler optimization

Other Changes

The documentation is now reduced to public interfaces; internal documentation is only built when requested
A lot of refactoring and code improvements

Everything’s available on http://hamsterdb.com/download.

David Bolton blogs about hamsterdb

chris — Thu, 04 Feb 2010 14:03:08 +0000

I like the title - “A Small Furry Database”

http://cplus.about.com/b/2009/12/15/a-small-furry-database.htm

crashes on 64bit Linux with gcc 4.4 (fixed!)

chris — Wed, 13 Jan 2010 07:38:23 +0000

I received several reports that hamsterdb crashes on 64bit linux with gcc 4.4.1 on Ubuntu (but maybe not restricted to Ubuntu).

I did some tests with gcc and the following gcc versions work fine:

4.1.3 20080704 (prerelease) (Debian 4.1.2-27)

4.3.4 (Debian 4.3.4-6)

4.4.3 20100108 (prerelease) (Debian 4.4.2-9)

It seems that the problem is only in 4.4.1 and maybe 4.4.2. To find out if your gcc has the same issue, just make a clean build and start the unittest; they would crash more or less immediately:

./configure –enable-internal
make clean
make
make test

I’ll try to get more test results…

update (jan 17, 2010) - i fixed the issues. They were caused by gcc’s “strict antialiasing” which caused crashes when compiled with -O3.