Florian Pflug writes:
> Just to clarify what's going on here, in case the OP is still puzzled.
> [ lots o detail snipped ]
Right. Thanks for writing out what I didn't have time for today...
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgre
On Aug4, 2011, at 22:54 , Tom Lane wrote:
> "Petro Meier" writes:
>> INSERT INTO "testtable" ("ID", "BinaryContents") values (1,
>> E'\xea2abd8ef3');
>> returns "invalid byte sequence".
>
>> '\xea2abd8ef3' is the string delivered by the PG 9.1 Beta3 serve
"Petro Meier" writes:
> INSERT INTO "testtable" ("ID", "BinaryContents") values (1,
> E'\xea2abd8ef3');
> returns "invalid byte sequence".
> '\xea2abd8ef3' is the string delivered by the PG 9.1 Beta3 server
> when calling PQescapeByteaConn(). It canno
On Wed, Aug 03, 2011 at 03:19:06PM +0200, Petro Meier wrote:
> Normal021false
> falsefalseDEX-NONEX-NONE
>
>
Normal021false
falsefalseDEX-NONEX-NONE
MicrosoftInternetExplorer4
On 07/27/2011 02:05 PM, Alvaro Herrera wrote:
Excerpts from Petro Meier's message of mié jul 27 02:51:22 -0400 2011:
If I use PQescapeByteaConn() for a conenction to a PG9.1 Beta3 server,
this function returns (e.g.) "\xea2abd8ef31...(and so on.)...".
Here the problem: there should
On Jul27, 2011, at 20:05 , Alvaro Herrera wrote:
> Excerpts from Petro Meier's message of mié jul 27 02:51:22 -0400 2011:
>
>> If I use PQescapeByteaConn() for a conenction to a PG9.1 Beta3 server,
>> this function returns (e.g.) "\xea2abd8ef31...(and so on.)...".
>>
>>Here the
Alvaro Herrera writes:
> Excerpts from Petro Meier's message of mié jul 27 02:51:22 -0400 2011:
>> If I use PQescapeByteaConn() for a conenction to a PG9.1 Beta3 server,
>> this function returns (e.g.) "\xea2abd8ef31...(and so on.)...".
>>
>> Here the problem: there should be a second
Excerpts from Petro Meier's message of mié jul 27 02:51:22 -0400 2011:
> If I use PQescapeByteaConn() for a conenction to a PG9.1 Beta3 server,
> this function returns (e.g.) "\xea2abd8ef31...(and so on.)...".
>
> Here the problem: there should be a second backslash in the prefi
On Jul27, 2011, at 08:51 , Petro Meier wrote:
> If I use PQescapeByteaConn() for a conenction to a PG9.1 Beta3 server, this
> function returns (e.g.) "\xea2abd8ef31...(and so on.)...".
> Here the problem: there should be a second backslash in the prefix. The SQL
> Statement which uses this strin
Normal021false
falsefalseDEX-NONEX-NONE
MicrosoftInternetExplorer4
11 matches
Mail list logo