I think that this is also true for DB2 using UTF-8 as the database encoding.
From an application perspective, MS SQL Server is the one that gives us the most
trouble, because it doesn't support UTF-8 as a database encoding for char, etc.
Kenneth Whistler <firstname.lastname@example.org> on 06/22/2000 06:42:20 PM
To: "Unicode List" <email@example.com>
cc: firstname.lastname@example.org, email@example.com, firstname.lastname@example.org (bcc: Joe Ross/Tivoli
Subject: Re: Java, SQL, Unicode and Databases
> Oracle doesn't have special requirement for datatype in JDBC driver if you use
UTF8 as database
> character set. In this case, all the text datatype in JDBC will support
The same thing is, of course, true for Sybase databases using UTF-8
at the database character set, accessing them through a JDBC driver.
But I think Tex's question is aimed at the much murkier area
of what the various database vendors' strategies are for dealing
with UTF-16 Unicode as a datatype. In that area, the answers for
what a cross-platform application vendor needs to do and for how
JDBC drivers might abstract differences in database implementations
are still unclear.
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:21:04 EDT