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

MySQL 4.0 & 4.1 will come soon. Transactions supported. In 4.1 - stored procedures. On slashdot.org yesterday someone posted an article which points to zdnet.com explaining. -- Andrey Hristov Web Developer IcyGEN Corporation BALANCED SOLUTIONS http://www.icygen.com P.S. Keep in mind the PGSQL in fast as MySQL. pgsql people do their job well. According by test posted on www.phpbuilder.com On Thursday 11 October 2001 16:19, you wrote: > On Wednesday 10 October 2001 23:23, Helge A. Kraenz (FF) wrote: > > This sounds really nice. > > > > But there is an another big problem: Can anybody give me a hint how to > > convince my bosses to replace Oracle with MySQL? They think, everything > > that costs nothing is worth nothing. > > > > Helge > > According to the www.mysql.com web site, they have commercial licenses > available to purchase, as well as commercial support. So, if they 'have' to > pay big bucks for the software, you can pay for mysql and support. > > -- > Chip > > > > -----Original Message----- > > > From: Jason G. [mailto:blair@nb.net] > > > Sent: Donnerstag, 11. Oktober 2001 08:12 > > > To: Helge A. Kraenz (FF); 'Dave Watkinson'; php-db@lists.php.net > > > Subject: RE: [PHP-DB] PHP can't lose to Micro$oft - Please HELP! > > > > > > > > > Check this out: > > > > > > Currently Mytrix provides extended statistics for more than > > > 200 000 web > > > resources, accounting for more than 70 million events per > > > day. The "raw" > > > gathered data is stored in a self-implemented data warehouse, and > > > statistics of it are stored in MySQL databases. > > > MySQL is used for extensive analysis of the data. For a > > > couple of years > > > MyISAM tables were used to store the processed data. We found > > > that the > > > InnoDB support for transactions, row level locks, and fast > > > automatic crash > > > recovery gives us an advantage, so we are migrating to InnoDB now. > > > Totally we have about 30 servers (mostly Dual PIII with 1-2 > > > GB of RAM) > > > which have in total more than 1 TB of data stored in MySQL > > > databases. The > > > number of tables is more than 100 000 (small tables were used > > > with MyISAM > > > to overcome concurrency problems in table level locking used > > > with MyISAM). > > > The tables contain more than 20 000 000 000 rows in total. > > > > > > At 07:44 AM 10/11/2001 +0200, Helge A. Kraenz (FF) wrote: > > > >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 > > > > > > > >-- > > > >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