now that i've gotten all the problems setting up my
development box out of the way, i need to focus in on
actually programming my applications.

i'm using php/apache/pgsql. the way i see it, i have
three choices.

1. pg api - all my books cover this approach and it is
kinda cool. ;-) downside is it locks you into pgsql
(not to big a deal) and you have to code like a
monster to get all your classes and functions
together.

2. pear - has some neat functions and classes pre made
- plug and play, as it were. however, i'd still have
a lot to learn using this style of programming b/c
i've never used before. i feel mor comfortable with
pg's api right now.

3. adodb - this just started sounding compelling about
30 minutes ago. seems to be faster and more portable
than pear. seems to have some nice functionality,
too. not sure if it has the same level of
class/function support - need to read up on this.

as a rookie, i appreciate the wisdon gained over
windows broken on second floors as monitors get tossed
out of them... ;-)

if you have something to say that you think is of
value, please chime in.

tia...




__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo (AT) postgresql (DOT) org so that your
message can get through to the mailing list cleanly

might as well throw mdb into the mix, too...

http://pear.php.net/package-info.php?package=MDB


--- operationsengineer1 (AT) yahoo (DOT) com wrote:




__________________________________
Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!
http://promotions.yahoo.com/new_mail

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html

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

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Tia,

I'd say these are your two reasonable choices. Regrettably, the Pear
database classes seem to have lost momentum to adodb lately.

We use our home-rolled stuff based on pg_connect, mostly because it was
written before Pear or Adodb were available. If I were starting now, I'd
probably use Adodb.

--
Josh Berkus
Aglio Database Solutions
San Francisco

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

On Fri, 10 Sep 2004 10:30:09 -0700, Josh Berkus <josh (AT) agliodbs (DOT) com> wrote:
Then you need to update your reference to 'lately' ;-)

PEAR:B has gone through great leaps and bounds (not just
functionality but documentation as well) - you should definitely
compare ADOdb and PEAR:B before making a decision.

I like ADOdb's query caching, and also make use of the non-db goodies
(like generating HTML dropdown form elements from the result of a
query) as well as generating INSERT statements from form submissions
(without having to test to see if values were submitted or not).
Don't forget ADOdb's XML goodies that allow you to reverse engineer a
database, define changes, and then apply those changes (or repeat on
another platform entirely).

OTOH, PEAR:B has awesome documentation, very good support for
prepared statements (great for many similar repeated statements), and
has also undergone pretty dramatic performance improvement. The
maintainer is very friendly and approachable.

Here is another thought - I have seen folks start out thinking "Hey,
I'll just use the native pgsql functions, and wrap them in a class to
simplify the interface." Next thing you know they are more-or-less
repeating the efforts of the two projects above, and usually with less
resources (and success). So if you are going to wrap your calls in a
class, why not use one of the leaders?

-- Mitch, hoping this helps

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo (AT) postgresql (DOT) org)