Thread: libpq PGresult object and encoding

libpq PGresult object and encoding

From
Jeff Davis
Date:
libpq has a PQclientEncoding() function that takes a connection object. 

However, the client encoding is, in some cases, a property of the result
object. For instance, if your client_encoding changes, but you keep the
result object around, you have no way to determine later what encoding
the results are in.

The result object already saves the client_encoding. Should an accessor
be provided?

Regards,Jeff Davis



Re: libpq PGresult object and encoding

From
Jeroen Vermeulen
Date:
Jeff Davis wrote:
> libpq has a PQclientEncoding() function that takes a connection object. 
> 
> However, the client encoding is, in some cases, a property of the result
> object. For instance, if your client_encoding changes, but you keep the
> result object around, you have no way to determine later what encoding
> the results are in.
> 
> The result object already saves the client_encoding. Should an accessor
> be provided?

That'd certainly save libpqxx the trouble of lugging a copy around.


Jeroen