Thread: Perl module: Postgres - obsolete?
I've just upgraded my development machine to 6.3, having been working with 6.2 and 6.2.1 quite successfully for much of the last year. When I started out with Postgres I picked up a module from the CPAN Perl archive called 'Postgres' (PostgresPerl-1.3.tar.gz). It doesn't seem to have been updated since late 1996, but seemed to work fine with 6.2 (so long as the Makefile.PL was amended to fix obsolete references to 'postgres95' directories. I've been using this module ever since, and am now wondering how safe it'll be with 6.3. It needed a further tweak to Makefile.PL this time (changed libpq.so.1 to libpq.so.1.1). In the medium term I will fix my code to use a more up to date Perl interface; in the meantime I'd be grateful for any advice. Am I likely to damage my data or crash the postmaster? The number change from 1 to 1.1 seems to indicate that the library should still work... Dan ps. the module can be obtained from any CPAN archive, eg http://src.doc.ic.ac.uk/packages/CPAN/modules/by-module/Postgres/
On Sat, 7 Mar 1998, Dan Brickley wrote:
> I've been using this module ever since, and am now wondering how safe
> it'll be with 6.3. It needed a further tweak to Makefile.PL this time
> (changed libpq.so.1 to libpq.so.1.1). In the medium term I will fix my
> code to use a more up to date Perl interface; in the meantime I'd be
> grateful for any advice. Am I likely to damage my data or crash the
> postmaster? The number change from 1 to 1.1 seems to indicate that the
> library should still work...
Is there a reason to not use the perl5 interface included with
v6.3? *raised eyebrow*
Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
On Sat, 7 Mar 1998, The Hermit Hacker wrote: > On Sat, 7 Mar 1998, Dan Brickley wrote: > > > I've been using this module ever since, and am now wondering how safe > > it'll be with 6.3. It needed a further tweak to Makefile.PL this time > > (changed libpq.so.1 to libpq.so.1.1). In the medium term I will fix my > > code to use a more up to date Perl interface; in the meantime I'd be > > grateful for any advice. Am I likely to damage my data or crash the > > postmaster? The number change from 1 to 1.1 seems to indicate that the > > library should still work... > > Is there a reason to not use the perl5 interface included with > v6.3? *raised eyebrow* Yep, my legacy code ;-) I've a /cgi-bin/dbase script written last year when the other library seemed OK. It shouldn't need too much reworking to move over to the new interface, but I won't be able to do this immediately. I'd really like to move to 6.3 first so I can take advantage of the improved ODBC support. I want to hack a whois++ interface to PostgreSQL at some point soon, and will be using the standard perl5 library for that. cheers, Dan -- Daniel.Brickley@bristol.ac.uk Research and Development Unit tel: +44(0)117 9288478 Institute for Learning and Research Technology http://www.ilrt.bris.ac.uk/ University of Bristol, Bristol BS8 1TN, UK. fax: +44(0)117 9288473
On Sat, 7 Mar 1998, Dan Brickley wrote:
> On Sat, 7 Mar 1998, The Hermit Hacker wrote:
>
> > On Sat, 7 Mar 1998, Dan Brickley wrote:
> >
> > > I've been using this module ever since, and am now wondering how safe
> > > it'll be with 6.3. It needed a further tweak to Makefile.PL this time
> > > (changed libpq.so.1 to libpq.so.1.1). In the medium term I will fix my
> > > code to use a more up to date Perl interface; in the meantime I'd be
> > > grateful for any advice. Am I likely to damage my data or crash the
> > > postmaster? The number change from 1 to 1.1 seems to indicate that the
> > > library should still work...
> >
> > Is there a reason to not use the perl5 interface included with
> > v6.3? *raised eyebrow*
>
> Yep, my legacy code ;-)
>
> I've a /cgi-bin/dbase script written last year when the other library
> seemed OK. It shouldn't need too much reworking to move over to the new
> interface, but I won't be able to do this immediately. I'd really like to
> move to 6.3 first so I can take advantage of the improved ODBC support.
Ah, okay...not sure, but I *think* you should be okay as mentioned
above, with just changing the shared library and going...but since I've
not used the other perl interface, am not certain...
Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
Hello,
> > Yep, my legacy code ;-)
> >
> Ah, okay...not sure, but I *think* you should be okay as mentioned
> above, with just changing the shared library and going...but since I've
> not used the other perl interface, am not certain...
It works. We have a rather large application working with the old
interface from Vivek Khera. Edmund (maintainer of the "new"
interface, in fact at the time we decided to use Viveks interface, it
simply was more perlish, you'll find references in Edmunds code,
called old style) to pick up the sentence again: Edmund has added
a new function which fetches a complete line into a Perl array. This
one was missing and should help transition from Postgres.pm to Pg.pm.
Ciao
Das Boersenspielteam.
---------------------------------------------------------------------------
http://www.boersenspiel.de
Das Boersenspiel im Internet
*Realitaetsnah* *Kostenlos* *Ueber 6000 Spieler*
---------------------------------------------------------------------------