Prev: Using views for row-level access control isleaky
Next: [HACKERS] Plans for 9.1, Grouping Sets, disabling multiqueries, contrib module for string, plpgpsm, preload dictionaries
From: Jeroen Vermeulen on 17 Feb 2010 17:32
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


--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

 | 
Pages: 1
Prev: Using views for row-level access control isleaky
Next: [HACKERS] Plans for 9.1, Grouping Sets, disabling multiqueries, contrib module for string, plpgpsm, preload dictionaries