Received: from waugh.econ.queensu.ca (waugh.econ.QueensU.CA [130.15.74.5]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f2TMGuK13485 for ; Thu, 29 Mar 2001 17:16:56 -0500 (EST) (envelope-from drew@waugh.econ.queensu.ca) Received: from drew by waugh.econ.queensu.ca with local (Exim 3.12 #1 (Debian)) id 14ikis-0003IC-00 for ; Thu, 29 Mar 2001 17:16:54 -0500 Date: Thu, 29 Mar 2001 17:16:54 -0500 To: PostgreSQL-PHP list Subject: A valuable addition to PHP... Message-ID: <20010329171654.A12635@waugh.econ.queensu.ca> References: <3ABFADEE.6000802@greatbridge.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3ABFADEE.6000802@greatbridge.com>; from ned@greatbridge.com on Mon, Mar 26, 2001 at 04:00:30PM -0500 From: Andrew Hammond X-Archive-Number: 200103/62 X-Sequence-Number: 247 As an unabashed hacker, I'd like to point out one addition that I personally would really appreciate and find useful. Perl (and hence mod-perl and/or mason based stuff) has DBI and zope offers their SQL objects. Sadly, PHP's database stuff, while functional, is a fugly mess. A layer of abstraction gives at least the illusion of database independance. And while I certainly can (and have) written n'th tier layers that encapsulate all the pg_* php function calls, I personally don't _like_ having to do that kind of stuff. And given the choice, I always go with a tool that will do it for me. 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. Well, you _did_ ask... :)