PEAR is archived and read-only

This mirror preserves historical PEAR package releases and metadata so existing references remain available.

Home » Database » MDB2 » Bug #10021

silent exit during connecting

Details

Submitted2007-02-04 09:29 UTC
Fromph7apul at atlas dot cz
StatusClosed
PackageMDB2
PHP Version5.1.4
OSLinux zzz 2.6.16-gentoo-r7 #2
Roadmaps(Not assigned)

Comments

[2007-02-04 09:29 UTC] ph7apul at atlas dot cz

Description:
------------
Script involving MDB2 connection exits silently (even with error_reporting(E_ALL) ) during creating such connection. MDB2 example script included in the package also exits silently. Problem seems to be independent of method used(ie. singleton, factory, connect). However I tried only with mysql and mysqli drivers.

Problem can be solved by downgrading to MDB2 2.2.2 which operates seamlessly.

additional info: pear 1.5.0 (go-pear), MDB2 2.3.0
--with-libdir=lib64' '--disable-cli' '--with-apxs2=/usr/sbin/apxs2' '--with-config-file-path=/etc/php/apache2-php5' '--with-config-file-scan-dir=/etc/php/apache2-php5/ext-active' '--without-pear' '--disable-bcmath' '--without-bz2' '--disable-calendar' '--disable-ctype' '--without-curl' '--without-curlwrappers' '--disable-dbase' '--disable-exif' '--without-fbsql' '--without-fdftk' '--disable-filepro' '--disable-ftp' '--with-gettext' '--without-gmp' '--disable-hash' '--without-hwapi' '--without-informix' '--disable-ipv6' '--without-kerberos' '--enable-mbstring' '--without-mcrypt' '--enable-memory-limit' '--without-mhash' '--without-ming' '--without-msql' '--without-mssql' '--without-ncurses' '--without-openssl' '--without-openssl-dir' '--disable-pcntl' '--without-pgsql' '--disable-posix' '--with-pspell' '--without-recode' '--disable-shmop' '--without-snmp' '--disable-soap' '--enable-sockets' '--without-sybase' '--without-sybase-ct' '--disable-sysvmsg' '--disable-sysvsem' '--disable-sysvshm' '--with-tidy' '--disable-tokenizer' '--disable-wddx' '--disable-xmlreader' '--disable-xmlwriter' '--without-xmlrpc' '--with-xsl' '--with-zlib' '--disable-debug' '--without-cdb' '--without-db4' '--without-flatfile' '--without-gdbm' '--without-inifile' '--without-qdbm' '--without-freetype-dir' '--without-t1lib' '--disable-gd-jis-conv' '--disable-gd-native-ttf' '--without-jpeg-dir' '--without-png-dir' '--without-xpm-dir' '--without-gd' '--with-mysql=/usr/lib/mysql' '--with-mysql-sock=/var/run/mysqld/mysqld.sock' '--with-mysqli=/usr/bin/mysql_config' '--without-pdo-dblib' '--with-pdo-mysql=/usr' '--without-pdo-odbc' '--without-pdo-pgsql' '--without-pdo-sqlite' '--without-readline' '--without-libedit' '--without-mm' '--without-sqlite'

Test script:
---------------
require_once 'MDB2.php';
$mdb2 =& MDB2::singleton("mysqli://xxx:yyy@localhost/zzz");
echo "something happened";

Expected result:
----------------
"something happened"

Actual result:
--------------
blank page

[2007-02-04 15:56 UTC] ph7apul at atlas dot cz

No, beyond the attempt to create connection any output is simply not rendered.

But I found strange thing though. If I replace MDB2 files with any other version and then overwrite them with v 2.3.0 then the first test page reload actually produces some output, ie. "something happened" (and MDB2 error "not supported"). However, any other successive reload leads again to blank page without any output. Seems to me like some package files handling problem.

[2007-02-04 16:14 UTC] ph7apul at atlas dot cz

MDB2 2.3.0 and mdb2 mysql(i) drivers 1.3.0 produced this bug in the first place.

[2007-02-04 17:48 UTC] ph7apul at atlas dot cz

Latest MDB2_Schema (0.7.0) installed, no "not supported" message yet still one-use-only. As stated before, rewriting /PEAR/MDB2.php with any MDB2.php, even the same version(I was wrong at this point), lets me do one attempt. Quite funny, really :)

[2007-02-11 12:50 UTC] ph7apul at atlas dot cz

resolved by CVS upgrade and solving some dependency issues, thx