Received: from correo.servidoresdns.net ([195.55.179.56]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f2UBrcK19765 for ; Fri, 30 Mar 2001 06:53:45 -0500 (EST) (envelope-from david.lizano@izanet.com) Received: from servidornt.izanet.com [195.55.250.69] by correo.servidoresdns.net with ESMTP (SMTPD32-6.04) id A34615A9022E; Fri, 30 Mar 2001 13:51:34 +0200 Message-Id: <4.3.2.7.0.20010330134922.00c259f0@192.168.1.1> X-Sender: sj7010@192.168.1.1 X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 30 Mar 2001 13:51:43 +0200 To: pgsql-php@postgresql.org From: David Lizano Subject: Re: A valuable addition to PHP... In-Reply-To: <20010329171654.A12635@waugh.econ.queensu.ca> References: <3ABFADEE.6000802@greatbridge.com> <3ABFADEE.6000802@greatbridge.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Archive-Number: 200103/65 X-Sequence-Number: 250 > >Of course yet-another-database-interface-layer while certainly a good >and usefull piece of engineering wouldn't be particularly new and >innovative. What _would_ be new and innovate, and maybe even impressive >is a database interface layer that provides not just the usual database >independant connect / query / result stuff but an organized, database >independant way of accessing metadata. Writing SQL queries that derive >metadata by futzing around with the pg_* tables works but is totally >non-portable. What I would really like to see is a database interface >layer that encapsulates all that nasty mess. Metadata and other >introspective stuff is a glaring ommission from SQL. You should see this pear tutorial. Pear have an abstraction layer library for databases. http://www.phpbuilder.com/columns/allan20010115.php3