| From: | Fernando Nasser <fnasser(at)redhat(dot)com> |
|---|---|
| To: | pgsql-patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | JDBC Issue warning if could not find encoding |
| Date: | 2002-11-25 22:28:39 |
| Message-ID: | 3DE2A417.7030108@redhat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
We currently silent fall back to the default JVM encoding if we could not find
the requested on or the one used by the backend (if it is unknown we also fall
back). At least we should log a warning. This patch adds the appropriate warnings.
P.S.: This affects up to 7.2 backends only. None of this makes sense on 7.3+
backends; we will just use UNICODE and warn that we ignored charSet.
--
Fernando Nasser
Red Hat - Toronto E-Mail: fnasser(at)redhat(dot)com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9
| Attachment | Content-Type | Size |
|---|---|---|
| JDBCENCODING.PATCH | text/plain | 7.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fernando Nasser | 2002-11-25 22:44:37 | JDBC SQLStatus for Dynamic SQL, unsupported feature, invalid transaction state and others |
| Previous Message | Rod Taylor | 2002-11-25 21:28:52 | Resultmap for FreeBSD 4.7 |