PHP can't lose to Micro$oft - Please HELP!

From: Date: Thu, 11 Oct 2001 05:11:03 +0000
Subject: PHP can't lose to Micro$oft - Please HELP!
Groups: php.db 
Request: Send a blank email to php-db+get-13214@lists.php.net to get a copy of this message
Situation: Small software company is at a cross-road. Do we use ASP (Win 2k, IIS, VB...) or PHP (UNIX, Apache...). Currently we have two teams working on prototypes for this project. The Micro$oft pets (ASP) vs. the PHP free-spirits (btw, PHP is way ahead in features implemented!). Good vs. Evil, right? :) Anyway, THE PROBLEM: We use INFORMIX IDS 7.3 (Windows) for db. Can't change that (spent to much money on it). The problem we are having is this: We create a persistent connection with the Informix server: $database = "tst22"; $server = "some_db_server"; $login = "blah"; $password = "blabblah"; $dbs = $database."@".$server; $connect_id_roll = ifx_pconnect($dbs,$login,$password); <-- Line 51 --| if (!$connect_id_roll) { echo "Unable to connect to Informix database<br>\n"; chk_ifx_err1($connect_id_roll); } ... (our code) This works fine; most of the time that is, until we get this (somewhat randomly): Warning: E [SQLSTATE=08 002 SQLCODE=-1802] in d:\apache_webdocs\php_demo\roll_list.php on line 51 Unable to connect to Informix database Informix error: E [SQLSTATE=08 002 SQLCODE=-1802] Connection name in use. The ifx_error function return the following string: x [SQLSTATE = aa bbb SQLCODE=cccc] where x = space : no error E : error N : no more data W : warning ? : undefined W : warning So, until we fix this problem we can't proceed to develop the reset of the application the boss says, which is quite understandable, and of course the other team is closing in (although buggy as hell) we can't afford to let the Micro$oft script kitties win this one, can we?! Please help. Thanks in advance, Anonymouse Self

« previous php.db (#13214) next »