On Wednesday 03 March 2004 11:50 pm, Beau E. Cox wrote:That's a rapidly moving target and unfortunately you caught it while I was working on the parts that caused you problems.
Hello folks,
I noticed changed in DBD::DBM in the latest svn DBI source.
No, the fix isn't there. The fix is in DBD::File. See my next reply to Tim's message.1) added dbm to DBI registry (as noted in a prior reply). 2) patched DBM.pm to allow additions of private attribs:
+ #if (!$this->{f_valid_attrs}->{$var}) { + # die "Invalid attribute in connect: '$var'!\n" + #} $this->{$var} = $val;
3) (optional) got rid of annoying 'undefined var...' msgs in t/50dbm.t:Thanks, but the fix to that is replace everything with $dbh->dbm_versions, a method to display all that info that I was working on and forgot to take the previous info out of the test.
I'm going to upload momentarily a new version of the test that is much more complete - it checks on the users machine to see which of the five major DBM types is available, then if MLDBM and Data::Dumper are available, then runs the tests with all combinations of what's available (on Debian it passes all 10 combinations of the DBMs with/without MLDBM).
Check back in an hour and I think the problems you found (and some others as well) will have gone away.
Thanks much for the suggestions!
-- Jeff
