Subject | Re: [firebird-support] UTF-8 columns in ISO8859_1 database |
---|---|
Author | Milan Babuskov |
Post date | 2009-09-01T11:45:37Z |
Alec Swan wrote:
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
==================================
> We have a database where most of the table columns require ISO8859_1I'm not an expert in Java, but you will probably get transliteration
> 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?
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
==================================