Shouldn't the character set specified in the JDBC URL match the character
set of the database?

Here is the jist of my problem:
1. I need to create indexes on large columns, such as varchar(1024). This
requires that I use single-byte character set.
2. I need to store UTF8 characters in other columns which are much shorter.
This requires that I use multi-byte character set.
3. I need to access data via JDBC. Which character set should I specify on
the JDBC URL?

Any ideas on how to solve this problem?

Thanks.

Alec

On Tue, Sep 1, 2009 at 5:45 AM, Milan Babuskov <milanb@...> wrote:

>
>
> Alec Swan wrote:
> > We have a database where most of the table columns require ISO8859_1
> > character set and a few require UTF-8. We set ISO8859_1 as the default
> > database character set and specify UTF-8 character set only on those
> columns
> > that require it. We also set the JDBC URL character set property to
> > ISO8859_1.
> >
> > Are there any known problems with such configuration?
>
> I'm not an expert in Java, but you will probably get transliteration
> errors when you try to fetch UTF-8 character which do not exist in
> ISO8859_1. It would be a better idea to use UTF-8 as connection
> character set (i.e. in JDBC URL).
>
> --
> Milan Babuskov
>
> ==================================
> The easiest way to import XML, CSV
> and textual files into Firebird:
> http://www.guacosoft.com/xmlwizard
> ==================================
>
>
>


[Non-text portions of this message have been removed]