Skip site navigation (1) Skip section navigation (2)

Re: libpq PGresult object and encoding

From: Jeroen Vermeulen <jtv(at)xs4all(dot)nl>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: libpq PGresult object and encoding
Date: 2010-02-17 22:32:59
Message-ID: 4B7C6E9B.705@xs4all.nl (view raw or flat)
Thread:
Lists: pgsql-hackers
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


In response to

pgsql-hackers by date

Next:From: Jeroen VermeulenDate: 2010-02-17 22:52:14
Subject: Re: Avoiding bad prepared-statement plans.
Previous:From: Alvaro HerreraDate: 2010-02-17 22:12:03
Subject: Re: alpha4 timing

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group