From: | Mitch Pirtle <mitch(dot)pirtle(at)gmail(dot)com> |
---|---|
To: | "operationsengineer1(at)yahoo(dot)com" <operationsengineer1(at)yahoo(dot)com> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: Opinions Requested - PG API or Abstraction Layer |
Date: | 2004-09-10 13:50:21 |
Message-ID: | 330532b604091006506f8cf672@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-novice |
Hello,
My favourite is ADOdb, mainly as it seems to be the fastest of the DB
classes, has solid transaction support, a convenient quoting/escaping
method, and a whole host of other handy features (like generating a
form dropdown with the results of a query for you). Caching queries
on the webserver is also nice, as you don't have to make the
round-trip to the database (like you would with MySQL's caching).
Most importantly is the XML goodies that are with the most current
releases of ADOdb, which allow you to reverse-engineer a schema
dynamically and then make alterations to that schema, and then apply
them to your database again.
Quite impressive.
If you do not like the syntax of ADOdb, then PEAR's DB is my second
recommendation, as it has just about everything you would need out of
a DB class.
-- Mitch
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2004-09-10 14:10:25 | Re: Display of text fields |
Previous Message | Michael Wimmer | 2004-09-10 12:57:18 | unicode and varchar |
From | Date | Subject | |
---|---|---|---|
Next Message | Salerno, Vincent | 2004-09-10 14:34:38 | Alter session set current_schema |
Previous Message | operationsengineer1 | 2004-09-10 09:32:25 | Re: Opinions Requested - PG API or Abstraction Layer |