Bug #16424 Updated: dba_*open "c" mode broken again

From: Date: Thu, 04 Apr 2002 12:37:36 +0000
Subject: Bug #16424 Updated: dba_*open "c" mode broken again
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-4034@lists.php.net to get a copy of this message
ID: 16424 Updated by: tmo@virtua.ch Reported By: tmo@virtua.ch -Status: Feedback +Status: Open Bug Type: DBM/DBA related Operating System: trustix (rh 6.2 based) PHP Version: 4.1.2 New Comment: The problem is that our firm policy is only to use stable release on production servers. And as I found some complaint on newsgroup about this bug since upgrading php lately (~10 of march), I thought it may have passed through. Maybe the 3.x to 4.x BerkeleyDB code changed again, as described in #13629. Because copy/paste of the example given in #13629 fail on the second access, and succeed again when the db file is erased on my dev box. For myself, I already wrote a small check lib which give me back the access type to use. So this issue isn't a big one, and if it works with the next release, nothing to worry about. Beside, I haven't tried to downgrade my DB3 lib to 3.x, I prefer stay up to date with today libs. Previous Comments: ------------------------------------------------------------------------ [2002-04-04 07:19:13] sniper@php.net I just tried the example code found in #13629 and it works fine with PHP 4.2.0RC2 (found at http://www.php.net/~derick/) But I've compiled PHP with db-3.3.11. ------------------------------------------------------------------------ [2002-04-04 07:11:20] tmo@virtua.ch sorry, forgot it. It was referenced by n°10380 and 13629. Both are refernced as closed. ------------------------------------------------------------------------ [2002-04-04 07:04:46] sniper@php.net And what was the bug number where it says this is fixed? ------------------------------------------------------------------------ [2002-04-04 06:40:14] tmo@virtua.ch I've found reply as this bug has been fixed in 4.0.6, but it isn't anymore. Using a dba_open in mode "c" will create the file if it doesn't exists, but will fail in opening an existing file. I'm using 4.1.2 stable with an compiled sleepycat 4.0.14 db3 implementation. php configure command: //--- ./configure --with-apxs=/usr/local/apache/bin/apxs --with-openssl --enable-bcmath --enable-calendar --enable-ctype --enable-ftp --enable-imgstrttf --with-ttf --with-imap --with-imap-ssl --enable-trans-sid --enable-shmop --enable-sockets --enable-sysvshm --with-pgsql=/usr/local/pgsql --with-gd=/usr/local --with-mysql --with-mcrypt=/usr/lib/libmcrypt --with-mssql=/usr/local/freetds --with-sybase=/usr/local/freetds --with-gdbm --with-db3=/usr/local/BerkeleyDB.4.0/ --enable-dba //--- ------------------------------------------------------------------------ [2002-04-04 04:59:40] tmo@virtua.ch I've found reply as this bug has been fixed in 4.0.6, but it isn't anymore. Using a dba_open in mode c will create the file if it doesn't exists, but will fail in opening an existing file. I'm using with an compiled sleepycat 4.0.14 db3 implementation. php configure command: //--- ./configure --with-apxs=/usr/local/apache/bin/apxs --with-openssl --enable-bcmath --enable-calendar --enable-ctype --enable-ftp --enable-imgstrttf --with-ttf --with-imap --with-imap-ssl --enable-trans-sid --enable-shmop --enable-sockets --enable-sysvshm --with-pgsql=/usr/local/pgsql --with-gd=/usr/local --with-mysql --with-mcrypt=/usr/lib/libmcrypt --with-mssql=/usr/local/freetds --with-sybase=/usr/local/freetds --with-gdbm --with-db3=/usr/local/BerkeleyDB.4.0/ --enable-dba //--- ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=16424&edit=1

« previous php.bugs (#4034) next »