Re: Strange GDBM behavior

When you used "regular dbm(open|close)", did you also happen to have "use GDBM_File;" ? Or not? If not, then you were probably using some default dbm library other than GDBM, and maybe there was a problem with how your GDBM library and/or GDBM_File module were installed.

(According to perldoc -f dbmopen -- at least in my 5.8.1 version -- you can say "use SOMEDBM_File;" in combination with dbmopen, in order to override whatever dbm library was designated as the default when your perl was installed.)

But if the default dbm library works for you, all you need to do is find out what that is and check that it's available in all the places where you want your code to be portable to. Here's a one-liner to find out the default:

 perl -MAnyDBM_File -e 'print $AnyDBM_File::ISA[0],$/'
[download]

I get "NDBM_File" on macosx/perl-5.8.1, freebsd/perl-5.8.6 and solaris/perl-5.8.0 -- and since NDBM, like GDBM, is not byte-order dependent, it seems like a safe choice (unless the 4K limit on record size is an issue for you, which it probably isn't).

(minor update to fix grammar; also noticed that NDBM was also the default on 5.005_03 perl on solaris)

Comment on Re: Strange GDBM behavior Download Code

Replies are listed 'Best First'.
Re^2: Strange GDBM behavior by wink (Scribe) on Jul 22, 2005 at 05:14 UTC
No, I was not using GDBM. My point was just that I didn't think it was a problem with the method I was using to write or another error in my script. I'm actually thinking about using DB_File or just plain NDBM with flock. That's probably pretty much what GDBM does under the tie anyways (actually, the tie just gives you access to the C library, which I'm sure does file locking for you, likely with race condition checking, etc.)	[reply]

Replies are listed 'Best First'.

Re^2: Strange GDBM behavior
by wink (Scribe) on Jul 22, 2005 at 05:14 UTC

No, I was not using GDBM. My point was just that I didn't think it was a problem with the method I was using to write or another error in my script. I'm actually thinking about using DB_File or just plain NDBM with flock. That's probably pretty much what GDBM does under the tie anyways (actually, the tie just gives you access to the C library, which I'm sure does file locking for you, likely with race condition checking, etc.)

[reply]