Peter Mount wrote:
> The encoding patch added a new method to Connection called getEncoding().
> The sensitive parts of Connection then replace getBytes() with
> getBytes(getEncoding()), with a new encoding argument to PG_Stream's
> ReceiveString() method.
>
> However, the encoding is only changed with the charSet connection property
> (allows you to set the encoding on a per connection basis). Now I feel this
> should default (if charSet is absent) to be the file.encoding property. What
> do you think?
It seems to be the most elegant way to do it. And yes, a connection-specific
encoding could be useful.
