Lines Matching refs:DB_HASH
163 our ($VERSION, @ISA, @EXPORT, $AUTOLOAD, $DB_BTREE, $DB_HASH, $DB_RECNO);
178 #typedef enum { DB_BTREE, DB_HASH, DB_RECNO } DBTYPE;
180 $DB_HASH = new DB_File::HASHINFO ;
199 $DB_BTREE $DB_HASH $DB_RECNO
585 [$X =] tie %hash, 'DB_File', [$filename, $flags, $mode, $DB_HASH] ;
637 =item B<DB_HASH>
642 the files created using DB_HASH are not compatible with any of the
655 As with the DB_HASH format, it is possible to provide a user defined
662 to be manipulated using the same key/value pair interface as in DB_HASH
696 associative array (for DB_HASH & DB_BTREE file types) or an ordinary
713 interface methods (DB_HASH, DB_BTREE or DB_RECNO) is to be used.
721 tie %array, 'DB_File', $filename, $flags, $mode, $DB_HASH ;
724 equivalent of their dbopen() counterparts. The final parameter $DB_HASH
728 In the example above $DB_HASH is actually a pre-defined reference to a
730 Apart from $DB_HASH, there is also $DB_BTREE and $DB_RECNO.
734 $DB_HASH reference will only allow keys called C<bsize>, C<cachesize>,
739 $DB_HASH->{'cachesize'} = 10000 ;
741 The three predefined variables $DB_HASH, $DB_BTREE and $DB_RECNO are
747 for DB_HASH, DB_BTREE and DB_RECNO respectively.
826 call to C<tie> and let them take default values. As DB_HASH is the most
833 tie %A, "DB_File", "filename", O_CREAT|O_RDWR, 0666, $DB_HASH ;
842 tie %A, "DB_File", undef, O_CREAT|O_RDWR, 0666, $DB_HASH ;
853 =head1 DB_HASH
855 The DB_HASH file format is probably the most commonly used of the three
871 tie %h, "DB_File", "fruit", O_RDWR|O_CREAT, 0666, $DB_HASH
1837 my $db = tie %hash, 'DB_File', $filename, O_CREAT|O_RDWR, 0666, $DB_HASH
1880 my $db = tie %hash, 'DB_File', $filename, O_CREAT|O_RDWR, 0666, $DB_HASH
2026 visit along with the time you last visited them in a DB_HASH database.