Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:7300 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 6883 invoked by uid 1010); 23 Jan 2004 18:17:07 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 6825 invoked from network); 23 Jan 2004 18:17:06 -0000 Received: from unknown (HELO shiva.mind.de) (212.42.230.204) by pb1.pair.com with SMTP; 23 Jan 2004 18:17:06 -0000 Received: from [192.168.1.100] (p508EB09B.dip.t-dialin.net [80.142.176.155]) by shiva.mind.de (Postfix) with ESMTP id 2B1DE97B64; Fri, 23 Jan 2004 19:16:55 +0100 (CET) Date: Fri, 23 Jan 2004 19:18:33 +0100 Reply-To: Marcus Boerger X-Priority: 3 (Normal) Message-ID: <105-1499799937.20040123191833@marcus-boerger.de> To: Martin Kraemer Cc: Marcus Boerger , internals@lists.php.net In-Reply-To: <20040123091637.GB80022@deejai2.mch.fsc.net> References: <20040115170830.GA60445@deejai2.mch.fsc.net> <102109045968.20040115203958@marcus-boerger.de> <20040115201900.GA28871@deejai2.mch.fsc.net> <702115865593.20040115223338@marcus-boerger.de> <20040123091637.GB80022@deejai2.mch.fsc.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] PHP 4.3.5RC1 and dba(db4) From: helly@php.net (Marcus Boerger) Hello Martin, thanks for prooving my thoughts. What should i say other than the module is far too complex and allows far too many combinations so that as a consequence a lot of them don't work. Most of the non working combinations are inherent problems we cannot solve. The most common is the problem of name clashes in the external libs. And i don't want to search for all failing combinations that would be an endless story. Does this make you feel more comfortable in any way? marcus Friday, January 23, 2004, 10:16:37 AM, you wrote: > On Thu, Jan 15, 2004 at 10:33:38PM +0100, Marcus Boerger wrote: >> >> > I'll report when I found anything. >> >> Could you please update your php to current cvs version (PHP4.3.5RC1-dev and >> PHP5-dev). Also if that doesn't help you could update db4 to db4>=4.1.25 and >> test with db3 or db2 version. And what is the output of >> "php run-tests.php ext/dba"? > I have upgraded to db4.1.25 and now the locking problems have vanished. > The output of php run-tests.php ext/dba follows: > env TEST_PHP_EXECUTABLE=$cwd/sapi/cli/php sapi/cli/php run-tests.php ext/dba > ===================================================================== > CWD : /home/openis/cache/tmp/php-4.3.5RC1 > PHP : /home/martin/SRC/plusCD/work/php-4.3.5RC1/sapi/cli/php > PHP_SAPI : cli > PHP_VERSION : 4.3.5RC1 > ZEND_VERSION: 1.3.0 > PHP_OS : POSIX-BC - POSIX-BC S130he12.mch.fsc.net 04.0A A35 BS2000 > INI actual : > More .INIs : > Extra dirs : > ===================================================================== > Running selected tests. > PASS DBA CDB handler test [ext/dba/tests/dba_cdb.phpt] (info: CDB does not support replace or delete) > FAIL DBA CDB_MAKE handler test [ext/dba/tests/dba_cdb_make.phpt] (info: CDB_MAKE does not support reading) > FAIL DBA CDB handler test (read only) [ext/dba/tests/dba_cdb_read.phpt] > SKIP DBA DBM handler test [ext/dba/tests/dba_dbm.phpt] (reason: DBM handler not available) > SKIP DBA DB2 handler test [ext/dba/tests/dba_db2.phpt] (reason: DB2 handler not available) > SKIP DBA DB3 handler test [ext/dba/tests/dba_db3.phpt] (reason: DB3 handler not available) > PASS DBA DB4 handler test [ext/dba/tests/dba_db4.phpt] > PASS DBA FlatFile handler test [ext/dba/tests/dba_flatfile.phpt] > PASS DBA GDBM handler test [ext/dba/tests/dba_gdbm.phpt] > PASS DBA INIFILE handler test [ext/dba/tests/dba_inifile.phpt] > SKIP DBA NDBM handler test [ext/dba/tests/dba_ndbm.phpt] (reason: NDBM handler not available) > PASS DBA File Creation Test [ext/dba/tests/dba001.phpt] (info: FLATFILE handler used) > PASS DBA Insert/Fetch Test [ext/dba/tests/dba002.phpt] (info: FLATFILE handler used) > PASS DBA Insert/Replace/Fetch Test [ext/dba/tests/dba003.phpt] (info: FLATFILE handler used) > PASS DBA Multiple Insert/Fetch Test [ext/dba/tests/dba004.phpt] (info: FLATFILE handler used) > PASS DBA FirstKey/NextKey Loop Test With 5 Items > [ext/dba/tests/dba005.phpt] (info: FLATFILE handler used) > PASS DBA FirstKey/NextKey with 2 deletes [ext/dba/tests/dba006.phpt] (info: FLATFILE handler used) > PASS DBA Multiple File Creation Test [ext/dba/tests/dba007.phpt] (info: FLATFILE handler used) > PASS DBA magic_quotes_runtime Test [ext/dba/tests/dba008.phpt] (info: FLATFILE handler used) > PASS DBA dba_popen Test [ext/dba/tests/dba009.phpt] (info: FLATFILE handler used) > So, as I understand it, the problem went away by replacing db-4.0.14 > by db-4.1.25. But isn't it going to bite other db4 users? > Strange however that php-4.3.3 did not experience these problems. > Martin -- Best regards, Marcus mailto:helly@php.net