| From: | George Koras <gkoras(at)cres(dot)gr> |
|---|---|
| To: | Peter Mount <petermount(at)maidstone(dot)gov(dot)uk> |
| Cc: | fubjj(at)flashmail(dot)com, pgsql-interfaces(at)postgresql(dot)org |
| Subject: | Re: How to change the encoding inside the JDBC interface |
| Date: | 2000-11-28 11:54:12 |
| Message-ID: | 3A239CE3.40AC0440@cres.gr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
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.
| Attachment | Content-Type | Size |
|---|---|---|
| gkoras.vcf | text/x-vcard | 283 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2000-11-28 13:19:46 | RE: pgAdmin problems |
| Previous Message | Peter Mount | 2000-11-28 11:18:42 | RE: How to change the encoding inside the JDBC inter face |