| Name : perl-Tie-DB_FileLock
| |
| Version : 0.11
| Vendor : obs://build_opensuse_org/devel:languages:perl
|
| Release : 6.71
| Date : 2024-08-05 18:40:58
|
| Group : Development/Libraries/Perl
| Source RPM : perl-Tie-DB_FileLock-0.11-6.71.src.rpm
|
| Size : 0.02 MB
| |
| Packager : (none)
| |
| Summary : Locking access to Berkeley DB 1.x
|
Description :
Module DB_File allows perl to tie hashes to on-disk dbm files, but fails to
provide any method by which the hashes might be locked, providing exclusive
access or preventing page-level collisions. Tie::DB_FileLock extends
DB_File, providing a locking layer using flock().
You should probably be using BerkeleyDB which supports locking, but if that
isn\'t an option read on.
Unlike Tie::DB_Lock, Tie::DB_FileLock does not duplicate files to allow
concurrent access for readers and writers. Tie::DB_FileLock is therefore
suitable for large dbms with relatively short locking periods.
Tie::DB_FileLock is designed as a drop-in replacement for DB_File,
requiring minimal code changes. Change all occurrences of \"DB_File\" to
\"Tie::DB_FileLock\" and all should be well. DB_RECNO is not presently
supported by Tie::DB_FileLock.
Arguments to Tie::DB_FileLock are identical as those to DB_File. The dbm is
locked for shared access if opened RO, exclusively otherwise. The default,
as in DB_File, is read/write/create.
Use of the predefined references $DB_HASH, $DB_BTREE, and $DB_RECNO, is
identical as with DB_File. When creating your own, the new call is the
same, but the object created is a DB_File::XXX thing and not a
Tie::DB_FileLock::XXX thing -- therefore error messages will refer to
DB_File::XXX.
|
RPM found in directory: /packages/linux-pbone/ftp5.gwdg.de/pub/opensuse/repositories/devel:/languages:/perl:/CPAN-T/openSUSE_Tumbleweed/noarch |
