E
Electric Natcho
Hi, I'm working on an application that uses JBoss 3.2, Tomcat 4.1,
IIS, SQL Server 2000 and the MS JDBC driver. It's a typical web app
where the client can use a browser to save data to the database & then
view it later.
Our servlets respond using utf-8 so I'm assuming subsequent requests &
data from the client will be encoded using utf-8 as well. According to
the SQL Server documentation, unicode is saved using the ucs-2
encoding and utf-8 is not supported
(http://support.microsoft.com/default.aspx?scid=kb;en-us;232580). I've
also read that Java uses ucs-2 internally.
Will I have to explicitly convert encodings for all parameters (that
came from the client) when using prepared statements to insert into
the database? Is this conversion normally left up to the JDBC driver
(our driver has an option to use unicode instead of the default db
encoding)?
IIS, SQL Server 2000 and the MS JDBC driver. It's a typical web app
where the client can use a browser to save data to the database & then
view it later.
Our servlets respond using utf-8 so I'm assuming subsequent requests &
data from the client will be encoded using utf-8 as well. According to
the SQL Server documentation, unicode is saved using the ucs-2
encoding and utf-8 is not supported
(http://support.microsoft.com/default.aspx?scid=kb;en-us;232580). I've
also read that Java uses ucs-2 internally.
Will I have to explicitly convert encodings for all parameters (that
came from the client) when using prepared statements to insert into
the database? Is this conversion normally left up to the JDBC driver
(our driver has an option to use unicode instead of the default db
encoding)?