dump utility

[Joel Jacobson]

i've been using rocksdb for a while, and i want to try out some experiments with hamsterdb for comparison.  the API seems pretty close, so my basic porting effort seems to have thus far gone mostly smoothly, but there's something very goofy and mysterious happening which i seem unable to debug.

specifically, i make heavy use of what rocksdb (leveldb) calls "batched writes", aka transactions.  my understanding of the hamsterdb API is that i should be able to do something like the following:

ham_txn_begin()

ham_db_insert(db, txn, key1....)

ham_db_insert(db, txn, key2...)

etc

ham_txn_commit()

however, what i see is that my txn contents never get committed.  im sure im doing something wrong, but i have no idea what it might be.  is there a way to:

(a) dump the contents of a txn being committed?

(b) dump the contents of a DB (offline is fine)?

- j

[Joel Jacobson]

err, never mind, found my stupid mistake.

- j

[Christoph Rupp]

OK, cool. In case you need a dump utility, there is "ham_dump" in the "tools" directory.

Best regards
Christoph

--
You received this message because you are subscribed to the Google Groups "hamsterdb User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hamsterdb-use...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.