> I also would like to echo the comments that someone else has made about using
> DBI::DBD rather than Pg. Pg works well and is slightly easier to get working,
> but that is because the complexity of DBI::DBD adds some useful stuff not
> present in Pg. In particular, the error trapping is great. On the down side, it
> gets tedious writting each query as two parts: "prepare" and "execute". This is
> compensated for in overall portability to other DBMS, I think.
You may also avoid that downside by encapsulating prepare() and
execute(), eg.
sub mySelect { ... prepare... execute... ...}
Regards,
Ed Loehr