On Thu, 18 Dec 2008 02:41:41 +0100 Mark Martinec <[email protected]> wrote:
Hi, Mark, > tieing? When already choosing BerkeleyDB for its features, my > preferred choice would be to use explicit bdb function calls, which > give you full access to options and first-hand error status on > failures. Hiding bdb API under a perl 'tie' limits your choices and > muddies failure reasons. Sorry, I referred to it as tieing because that's how the docs refer to it and it's rife in the method names, but I actually use explicit BDB calls. > 3.2.5 should be alright for the purpose, although generally new > development would be least painful when starting from current code. Sure. > As it stands presently, the CVS head is stable and is still > compatible with 3.2.5, so one can switch back and forth if necessary. > One of the shifts in 3.3 is tighter error handling and informative > reporting/logging of all unexpected/unhandled error conditions, > please keep it in mind. I try to be diligent, but everybody fails now and again. I have no doubt that more eyes on the code will spot those quickly. :) Mike.
