Ian Barwick wrote: > Short answer: no urgent need. > Long answer: Unfortunately DBD::Pg is "out of sync" with the PostgreSQL > release process and hasn't yet been upgraded to take into account of > the changes in 7.3. > > _Basically_ a Perl application using DBD::Pg with 7.3 should work out of the > box if you retain all objects in the default PUBLIC schema; AFAICS there are > no problems using other schemas; where you may run into problems is with > DBD::Pg functions querying database meta-data (anything that accesses the > system catalogs). Definitively broken is the DBD::Pg-specific function > "table_attributes", though I am in the process of submitting a patch to fix > that.
And we will issue a new release once they are in, with an announcement to the gborg dbdpg mailing list and a posting to the interfaces list, and on CPAN. > > speaking > > of which, are there docs about what changed in the latest DBD::Pg? > > The latest DBD::Pg (v1.20) includes a "Changes" file. > I haven't seen anything specific on using it with PostgreSQL 7.3. I've The DBD:pg regression test passes with 7.3. That's about as far as I go. ;-) -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
