On 08/08/15 10:49, Prasanth Reddy wrote:
>
[snip]
> 12:42:02.505 (1) <=BE ParameterStatus(client_encoding = UTF8)
[snip]
> 12:42:02.506 (1) <=BE ParameterStatus(server_encoding = SQL_ASCII)
There's your problem. The client is expecting UTF8 while the server
is storing un-vetted SQL_ASCII. You will need to change one of the
components' choice of encoding and/or enforce content conformance in the
data. Another choice, in cases of known and expected non-compliance, is
to use bytea casting to bypass the automated content vetting. But your
choice in this case is going to be driven by the ease with which you can
alter your application vs the server-side changes that would be needed.
HTH,
Bosco.
