From: | Michael Bussmann <bus(at)fgan(dot)de> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | libpq and PQsetdb() |
Date: | 1998-03-08 11:42:51 |
Message-ID: | 19980308124251.22819@goliath.mb.priv |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi!
Maybe I have overlooked something, but I think there should be a small line
in migration/6.2.1_to_6.3 file that tells the user he has to recompile and
relink each program that uses libpq.so.
When I upgraded to 6.3 I thought that the interface routines of libpq
didn't change (I know that the protocol has changed, but this should be
nothing the application has to worry about), so I simply replaced libpq.so
and I got _very_ surprised when I couldn't start my binaries any more due
to a missing PQsetdb() function in libpq (it's now defined to
PQsetdbLogin).
(As a quick and dirty solution I made PQsetdb a function again that calls
PQsetdbLogin)
What about adding a version number to the library? The minor release
number could be used to indicate changes in the protocol, the major number
would _only_ be increased when changes in the interface occur (e.g. other
functions or other/new parameter of the routines), that would break
existing applications.
Just a thought...
Best regards,
MB
--
Michael Bussmann <bus(at)fgan(dot)de> [Tel.: +49 228 9435 211; Fax: +49 228 348953]
Today's Excuse:
static from plastic slide rules
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1998-03-08 17:51:14 | Re: [QUESTIONS] Testing Postgresql v6.3 |
Previous Message | Peter T Mount | 1998-03-08 11:09:03 | Re: WG: [QUESTIONS] Re: [HACKERS] text should be a blob field |