Add a default handler that makes handler parameter to open functions
optional.
@Improved dba extension (Marcus)
@-Made handler parameter of dba_(p)open() optional.
@-Added php.ini opt

Add a default handler that makes handler parameter to open functions
optional.
@Improved dba extension (Marcus)
@-Made handler parameter of dba_(p)open() optional.
@-Added php.ini option 'dba.default_handler' to specify a default handler.

show more ...

Alias dba_popen() to dba_open() until persistent STDIO streams are
implemented.

-Fix memory handling of persistent dba connections.
-Update tests.
# cdb and flatfile still FAIL for dba_popen since the known streams problem

At least this problem exposed some leaks..

Warnings and Notices when lock modifiers for dba_(p)open are used wrong.
This finally closes bug #20828 (and i hope it must not be reopened)

add missing comment

LOCK_EX is not allowed in read mode -> try using existing .lck file in read
only mode only when in read mode.

-remove second attempt to close lock file
-default to lock on db file instead on .lck file.
-try to use existing .lck file and only create it on failure (allows ro access)

Added open modifier '-' to skip/ignore locking. See bug #20828, #20858

Add Berkeley db4 support

Make magic_quotes_runtime work bidirectional for dba

Add magic_quotes_runtime support

Fix locking behaviour: On some systems read during write is permitted but
most libraries are not capable of that. GDBM is system dependant so there
we only test that we do not deadlock.

Use php_flock instead of flock

-fix file open mode when modifier 'd' is used
#Add my name to authors

Emit a warning when open mode modifier t is used wrong.

-Centralise open stream for builtin modules that use streams
-If locks work on database file then only one stream open call is used

finish work on locking
-all but gdbm do internal locking now since only gdbm has internal locking
-you can force locking on database or lck file (with gdbm this makes no
sense so a notic

finish work on locking
-all but gdbm do internal locking now since only gdbm has internal locking
-you can force locking on database or lck file (with gdbm this makes no
sense so a notice is generated)

show more ...

-lock support moved from dba_flatfile.c to dba.c
-flatfile, cdb, cdb_make use locking now
#locking is blocking per default use 'rt', 'wt', ct' or 'nt' for non blocking alias
#test access

-lock support moved from dba_flatfile.c to dba.c
-flatfile, cdb, cdb_make use locking now
#locking is blocking per default use 'rt', 'wt', ct' or 'nt' for non blocking alias
#test access to a database file.
#locking uses flock() which will be emulated or warned if that is not eally
#possible in ext/standard/flock_compat.c

show more ...

emalloc never returns 0, so we can simplify the code paths.
also replace ecalloc with emalloc+memset, so that the latter can be inlined.

Use the the name 'flatfile' correctly so the handler support can be built now.
#I do not like the lock solution since a crashed php would leave the *lck
#file locked now.

move newly introduced flatfile support from dbm to new flatfile handler
# do not make the same mistake as with ext/db where it was not clear
# which format was used.

-use of emalloc functions
-info was not initialised fulle due to memset parameters
now that the whole structure is initialised we can stop putting 0 in it.

Why did open fail?

incorporate cdb-0.75 as suggested by D. J. Bernstein
#dba now supports cdb_make