Re: DBD::Pg and "invalid frontend message type 10" - Mailing list pgsql-interfaces

From Greg Sabino Mullane
Subject Re: DBD::Pg and "invalid frontend message type 10"
Date
Msg-id f4422406517dd3ef95faf1fa36a35d89@biglumber.com
Whole thread Raw
In response to Re: DBD::Pg and "invalid frontend message type 10"  (Scott Cain <cain@cshl.edu>)
List pgsql-interfaces
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


> $dbh->func($_, 'putline');
> $dbh->func('endcopy');  # no docs on this func--got from google


Not sure what's going on exactly, but it is no doubt related
to the COPYing. Something that might help is to use the more
recent DBD::Pg COPY interfaces:

$dbh->pg_getline();
$dbh->pg_putline();
$dbh->pg_endcopy();

- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200508251305
https://www.biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEARECAAYFAkMN+lIACgkQvJuQZxSWSsgjqQCg8Voy1tajPfIt1lhIgDo+H/hI
ukcAoI7cD/uV5bx7olhvq2yZmBamTU+f
=Yiq+
-----END PGP SIGNATURE-----




pgsql-interfaces by date:

Previous
From: Tom Lane
Date:
Subject: Re: LabView and PostgreSQL ; and RecordSet GetString performance
Next
From: Michael Meskes
Date:
Subject: Re: [HACKERS] ECPG ignores SAVEPOINT if first statement of a transaction