RE: [PHP] DB stuff

Dennis, There are several different approaces to this, all have their relative strengths and weaknesses: 1. ODBC - speed and functionality depends on the vendor, and you need to obtain and install the drivers. You can get speed increases and additional functionality enforced on back end databases if you select a good driver, but they are usually not free and you are somewhat dependent on a commercial company developing upgrades, fixes, etc. 2. unified ODBC functions - limited set of functions, no real ODBC layer that abstracts or adds any value beyond simplified coding. Still dependent on native layer, which may require licensing the native layer and dealing with its speed and performance limitations. 3. a DB abstraction class or layer such as Metabase, PEAR, etc/ - database abstraction, and therefore easier database app building, but the paradigm is to hide logic in functions. You aren't always sure what you are getting and since it's not standards based you are limited to using it in individual circumstances - and why not roll your own database classes if you are going to do some real programming anyways? Just my .02 from what I've observed - I am positive that others will have differnet opinions, but I wanted to give my overview since I'm coming from a database connectivity standpoint. Best regards, Andrew ---------------------------------------------------- Andrew Hill Director Technology Evangelism OpenLink Software http://www.openlinksw.com XML & E-Business Infrastructure Technology Provider > -----Original Message----- > From: Voitenko, Denis [mailto:dvoitenko@qode.com] > Sent: Tuesday, November 07, 2000 10:22 AM > To: 'php-general@lists.php.net' > Subject: [PHP] DB stuff > > > I am wondering why wouldn't PHP support database connectivity like most > application servers do, e.g. something like a data source in JRun or > WebLogic where database connectivity is made DB server independent and all > the DB connectivity is configured in the guts of PHP? >