Closed p5pRT closed 20 years ago
The usual failure
lib/anydbm...........# # anydbm.t test 12 will fail when AnyDBM_File uses the combination of # DB_File and Berkeley DB 2.4.10 (or greater). # You are using DB_File 1.72 and Berkeley DB 2.4.14 # # Berkeley DB 2 from version 2.4.10 onwards does not allow null keys. # This feature will be reenabled in a future version of Berkeley DB. # FAILED at test 12
All others passed.
schinder@pobox.com wrote
lib/anydbm...........# # anydbm.t test 12 will fail when AnyDBM_File uses the combination of # DB_File and Berkeley DB 2.4.10 (or greater). # You are using DB_File 1.72 and Berkeley DB 2.4.14 # # Berkeley DB 2 from version 2.4.10 onwards does not allow null keys. # This feature will be reenabled in a future version of Berkeley DB. # FAILED at test 12
Since this is a known result\, and since the test has gone to the trouble of determining that DB_File is in use and the version of Berkeley DB (as evidenced by the message text)\, why doesn't it quietly ignore in this case?
Mike Guy
M.J.T. Guy writes: : Since this is a known result\, and since the test has gone to the : trouble of determining that DB_File is in use and the version of : Berkeley DB (as evidenced by the message text)\, why doesn't it : quietly ignore in this case?
Or we could patch around it with a key of "*!@NuLl kEy@!*" or such.
Larry
Larry Wall (lists.p5p):
Or we could patch around it with a key of "*!@NuLl kEy@!*" or such.
Somebody\, *somewhere*\, and you know it...
--
God Save the Queen! And let Satan take the Prime Minister... - Tanuki\, in the monastery.
simon@brecon.co.uk writes: : Larry Wall (lists.p5p): : >Or we could patch around it with a key of "*!@NuLl kEy@!*" or such. : : Somebody\, *somewhere*\, and you know it...
Well\, sure\, but it still wouldn't be our fault. :-)
And it would make it less buggy than it is.
Larry
On 2 Feb 2000\, Simon Cozens wrote:
Larry Wall (lists.p5p):
Or we could patch around it with a key of "*!@NuLl kEy@!*" or such.
Somebody\, *somewhere*\, and you know it...
Use a Truely Random Bits source such as HotBits http://www.fourmilab.ch/hotbits/how.html and run it out to 4096 bits. It will never[1] collide.
-- Benjamin Franz
[1] For values of never smaller than the heat death of the universe.
Benjamin Franz writes:
Use a Truely Random Bits source such as HotBits http://www.fourmilab.ch/hotbits/how.html and run it out to 4096 bits. It will never[1] collide.
[1] For values of never smaller than the heat death of the universe.
I hope I will not cause the immediate heat death of the universe by the following remark:
a) Write a DB_File with Perl modified as you propose; b) convert it to\, say\, Oracle by an independent tool; c) Now read these Oracle and DB_File databases into one Perl application.
The keys would collide.
Ilya
On Wed\, 2 Feb 2000\, Ilya Zakharevich wrote:
Benjamin Franz writes:
Use a Truely Random Bits source such as HotBits http://www.fourmilab.ch/hotbits/how.html and run it out to 4096 bits. It will never[1] collide.
[1] For values of never smaller than the heat death of the universe.
I hope I will not cause the immediate heat death of the universe by the following remark:
a) Write a DB_File with Perl modified as you propose; b) convert it to\, say\, Oracle by an independent tool; c) Now read these Oracle and DB_File databases into one Perl application.
The keys would collide.
True. Can't be avoided as far as I can tell once you regard DB_File interfaces as an open system. But I have a weasle-out on semantics since "right now" still satisfies the specified inequality.[1] :)
-- Benjamin Franz [1] And thus the universe is saved from an untimely death.
Simon Cozens \simon@​brecon\.co\.uk writes:
Larry Wall (lists.p5p):
Or we could patch around it with a key of "*!@NuLl kEy@!*" or such.
Somebody\, *somewhere*\, and you know it...
We could use a Tcl-like hack that used a utf8-encoded 0 ;-)
-- Nick Ing-Simmons
Nick Ing-Simmons writes:
We could use a Tcl-like hack that used a utf8-encoded 0 ;-)
You mean some quantity which is not utf8-encoded *anything*. ;-)
Ilya
Migrated from rt.perl.org#2066 (status was 'resolved')
Searchable as RT2066$