Re: Perl-like DBI and generic SQL

I have found metabase to be superior to any other abstraction layer I've ever come across. Hey, it also allows you to do DB schema definitions with XML files, which is hugely cool. We're running development of commercial-grade (tested, yadda-yadda) doing development on mySQL, and moving to Oracle in production. With no problems. Without metabase, I would consider the above suicidal and idiotic, but with metabase it works like a charm. If you'd like other resources beyond an abstraction layer (like authentication, permissions, and all kinds of other groovy tools), have a look at binarycloud.com. _a -- Alex Black, Head Monkey enigma@turingstudio.com The Turing Studio, Inc. http://www.turingstudio.com vox+510.666.0074 fax+510.666.0093 Saul Zaentz Film Center 2600 Tenth St Suite 433 Berkeley, CA 94710-2522 > From: michael@tapinternet.com (Michael Kimsal) > Newsgroups: php.general > Date: 15 Jan 2001 06:28:19 -0800 > Subject: Re: [PHP] Perl-like DBI and generic SQL > > > > Dean Hall wrote: > >> I read once on this list that PHP supports a DBI-like database access object >> (such as the one in Perl). Is this true? Does anyone know where I can find >> documentation for it? I can't seem to find it in the manual. >> >> Also, how do you all handle generic SQL for multiple DBMSs? I'd like >> (ideally) to write SQL that is DBMS-independent, although that's probably not >> possible. I'm very familiar with mysql and not much else; as far as I'm >> aware, mysql is the primary DBMS that has problems with standard SQL (like >> nested queries and such). Does anyone even worry about this? >> >> I'm writing a little piece of software that I'd like to be as extensible as >> possible and as usable as possible for people using any DBMS, including >> mysql. >> >> Anyway, if I can't find a generic built-in database interface in PHP, it'll >> all be moot. I'd really rather not use phplib; I'd like to use an interface >> built in to the interpreter rather than something that's interpreted on every >> page access. >> > > You won't find one. The 'benefit' of PHP is that is, for the most part, uses > native db drivers for access to each db. Should be a bit faster and allows > access to the specific features of each db. > > There is a PEAR repository which offers something similar to DBI, afaik, but > it's not widely discussed, from what I can see. PEAR is a set of files that > comes with a distribution, and there is a README. People on shared host > environments may be out of luck here, though, with respect to a README (d/l > the file and read it manualyl I guess). > > "metabase" from manuel lemos purports to be a single interface to multiple dbs > - write one SQL statement and it'd do the necessary translation on the SQL to > be specific to whatever db you are using. Haven't used it, but heard nice > things about it. But, it violates your 'not interpreted' clause. > > Good luck. > > > > >> >> Thanks for the help. >> Dean. > > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, e-mail: php-general-unsubscribe@lists.php.net > For additional commands, e-mail: php-general-help@lists.php.net > To contact the list administrators, e-mail: php-list-admin@lists.php.net >