>> My question: Which way is available to query the linked libpq version?
> But it does outline that fact that it wouldn't suck to have a >function in
> libpq returning the version so that application can >check this at runtime -
> clearly it would also be useful when >being linked "through" s
A.M. wrote:
>
> On Oct 7, 2010, at 5:34 AM, Devrim G?ND?Z wrote:
>
> > On Thu, 2010-10-07 at 12:23 +0300, Peter Eisentraut wrote:
> >> This is really something that psycopg2 should work out for you. I
> >> suggest you take up a discussion on this on their mailing list.
> >
> > ...which is down o
On Oct 7, 2010, at 5:34 AM, Devrim GÜNDÜZ wrote:
> On Thu, 2010-10-07 at 12:23 +0300, Peter Eisentraut wrote:
>> This is really something that psycopg2 should work out for you. I
>> suggest you take up a discussion on this on their mailing list.
>
> ...which is down over the last 3 weeks or so:
On Thu, 2010-10-07 at 12:23 +0300, Peter Eisentraut wrote:
> This is really something that psycopg2 should work out for you. I
> suggest you take up a discussion on this on their mailing list.
...which is down over the last 3 weeks or so:
http://www.initd.org/
--
Devrim GÜNDÜZ
PostgreSQL Danış
On tis, 2010-10-05 at 09:33 +0200, Massa, Harald Armin wrote:
> Now I would love to have an additional check "is the used psycopg2
> linked to an advanced-enough libpq", to be able to set bytea_output to
> 'escape' if the libpq is not worthy.
This is really something that psycopg2 should work out
On Tue, Oct 5, 2010 at 16:32, Greg Sabino Mullane wrote:
>> My question: Which way is available to query the linked libpq version?
>
> That's information your driver should be supplying. For example, in
> Perl (DBD::Pg), you would say
>
> if ($dbh->{pg_lib_version} >= 9) {
>
> I'd raise a bug
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> My question: Which way is available to query the linked libpq version?
That's information your driver should be supplying. For example, in
Perl (DBD::Pg), you would say
if ($dbh->{pg_lib_version} >= 9) {
I'd raise a bug with psycopg2
On Tue, Oct 5, 2010 at 09:33, Massa, Harald Armin wrote:
> With 9.0 there is the new hex encoding for BYTEA, which is activated by
> default.
> libpq BEFORE 9.0 are not able to decode that encoding.
> I am programming with Python, using psycopg2. When psycopg2 is linked with
> libpq 9.0, everythin
