RE: [PHP-DB] PHP can't lose to Micro$oft - Please HELP!

I'm absolutely no fan of commercial software but Oracle actually has (or has had) some advantages compared with MySQL: - You can make subqueries, e.g. "select * from ( select * from table )" - You can (not easily, OK) handle LOB with a size up to 2 GB - Oracle can handle LARGE databases (>> 10GB >100GB) - I don't know wheter MySQL is able to do this Maybe MySQL was improved since the last time I read anything about these features but otherwise if you need any of these features you cannot use MySQL or you have to implement time consuming workarounds. If you don't rely on these features, throw any commercial database away and use Postgres or MySQL. My strongest suggestion is to drop MS Windows and to move to Unix/Linux with you webserver this saves a lot of money and prevents you from many crashes - I never get my Linux system to crash but my Win2K system freezes each day when I shut it down. Helge > -----Original Message----- > From: Dave Watkinson [mailto:d.watkinson@mightymatch.com] > Sent: Donnerstag, 11. Oktober 2001 07:12 > To: php-db@lists.php.net > Subject: RE: [PHP-DB] PHP can't lose to Micro$oft - Please HELP! > > > we dropped Oracle Java and IIS for MySQL PHP and Apache. > > We spent a *hell* of a lot of money that we won't get back > (anybody want > a second hand Oracle licence!!!), but the systems is about a million > times faster, more efficient, easier to improve, stable, platform & > browser independent than ever before. > > I say you suggest dropping everything and look at the situation as a > whole - not just cost but also features, ease of use (why recompile > crappy Java Applets every five minutes when you can use Notepad?!) and > evertthing else I listed above. > > > Cheers > > Dave > > > -----Original Message----- > From: Jason G. [mailto:blair@nb.net] > Sent: 11 October 2001 06:21 > To: Notmy Realname; php-db@lists.php.net > Subject: Re: [PHP-DB] PHP can't lose to Micro$oft - Please HELP! > > > I do not know much about informix, but personally, if MySQL or > PostgreSQL > is better, then who cares how much you spent on informix. > Use the best > tool for the job! > > > At 10:11 PM 10/10/2001 -0700, Notmy Realname wrote: > >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 > > > > > > > >-- > >PHP Database Mailing List (http://www.php.net/) > >To unsubscribe, e-mail: php-db-unsubscribe@lists.php.net > >For additional commands, e-mail: php-db-help@lists.php.net > >To contact the list administrators, e-mail: > php-list-admin@lists.php.net > > > -- > PHP Database Mailing List (http://www.php.net/) > To unsubscribe, e-mail: php-db-unsubscribe@lists.php.net > For additional commands, e-mail: php-db-help@lists.php.net > To contact the list administrators, e-mail: > php-list-admin@lists.php.net > > > -- > PHP Database Mailing List (http://www.php.net/) > To unsubscribe, e-mail: php-db-unsubscribe@lists.php.net > For additional commands, e-mail: php-db-help@lists.php.net > To contact the list administrators, e-mail: > php-list-admin@lists.php.net >