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

libpq PGresult object and encoding

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: libpq PGresult object and encoding
Date: 2010-02-16 04:06:27
Message-ID: 1266293187.22594.45.camel@jdavis-laptop (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
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?

	Jeff Davis


pgsql-hackers by date

Next:From: KaiGai KoheiDate: 2010-02-16 05:10:00
Subject: Re: CommitFest Status Summary - 2010-02-14
Previous:From: Jeff DavisDate: 2010-02-16 03:48:32
Subject: Re: Confusion over Python drivers

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