luckbird888 wrote:
各位，有没有遇到过0.9-rc2乱码的问题？
在做项目的时候，通过hibernate与sql server连接，从数据库中检索出的数据全为乱码，该怎么解决？

huajiazhou wrote:
请问这个连接MS SQL数据库的代码是什么样子的啊 ?

huajiazhou wrote:
机器环境是这样的XP SP2，Tomcat 5.0，jtds-1.0.2，SQL SERVER 2000

mmwy wrote:
读vachar字段的时候，要用iso8859-1转码。如果是nvarchar的字段就不用转了

why wrote:
http://sourceforge.net/projects/jtds/

Overview

jTDS is an open source 100% pure Java (type 4) JDBC 3.0 driver for
Microsoft SQL Server (6.5, 7, 2000 and 2005) and Sybase (10, 11, 12).
jTDS is based on the work of the FreeTDS project and is currently the
fastest production-ready JDBC driver for SQL Server and Sybase.
jTDS is 100% JDBC 3.0 compatible, supporting forward-only
and scrollable/updateable ResultSets, concurrent (completely
independent) Statements and implementing all of the DatabaseMetaData
and ResultSetMetaData methods. Check out the feature matrix for more details.


http://sourceforge.net/project/shownotes.php?release_id=299683
Release Name: 1.0

Notes:
The jTDS Project has released version 1.0 of the jTDS JDBC driver for
SQL Server and Sybase. After 3 1/2 years of development, 21 releases
and 100K downloads, jTDS is finally considered stable enough and JDBC
feature complete to grant the first official production release.

All important bugs fixed, jTDS is still the most performant JDBC driver for
SQL Server and Sybase. It passes the J2EE 1.3 certification and Hibernate
test suites and is the preferred SQL Server/Sybase driver for JBoss,
Hibernate, Atlassian JIRA and Confluence, DbVisualizer and ComPiere.

New features:
o Single Sign On (Windows authentication using the logged user's credentials)
o SSL secure communication support
o Local named pipes (greatly improved local communication speed)
o Paged fetching for cursor based ResultSets



jTDS is THE JDBC driver for SQL Server. Open source, faster than any
other SQL Server driver and with a full implementation of the JDBC 2.1 spec.

jTDS JDBC Driver 0.8-rc1 released

The 0.8-rc1 release comes with three major changes. From a functional
point of view the release is centered around one major improvement:
the new semantically correct Connection implementation, using a single
physical connection (as opposed to previous releases, which used multiple
physical connections to achieve Statement concurrency at the cost of
correctness and possible deadlocking). Thanks to this one change 0.8-rc1
is the first jTDS release to pass the Hibernate test suite and to actually
be a complete and correct JDBC implementation.

The two other areas where major changes took place are documentation
and licensing. The documentation has been greatly improved both in the
source package and online (the site and the documentation included in
the source package are actually the same). Also, starting with 0.8-rc1
jTDS is licensed under the LGPL. We have decided to do this in order to
give jTDS a greater chance to grow in the future, but also to prevent it
from becoming a launchpad for new commercial drivers.

New features:

o Correct Connection implementation, using a single physical connection.
o SQLExceptions thrown by jTDS now have associated SQL state values.
o Improved performance (no kidding).
o Closer to complete Blob/Clob support (there are still some memory issues).

Bugfixes:

o Scrollable/updateable ResultSets did not work with PreparedStatements.
o macAddress and lastUpdateCount parameters work.
o executeBatch() now works with empty batches too.
o Bug #887508 (getObject() returns Integer-Object on Types.SMALLINT) fixed.
o Bug #924030 (EscapeProcessor problem with "{}" brackets) fixed.
o SELECT FOR BROWSE returned an extra column.


0.8 released (2004-06-21)
Notes:
The 0.8 release corrects a number of bugs reported against 0.8-rc1, and adds several more JDBC 3 features.

New features:
o Support for passing parameters to stored procedures by name.
o Support for Types.BOOLEAN.
o Initial Savepoint implementation
o Support for streaming Blob/Clob writes.
o Added initial (limited) ParameterMetaData support.
o initCause() is now called for SQLExceptions under 1.4+ JVMs.


0.8.1 released (2004-07-07)
Notes:
The 0.8.1 release primarily corrects a deployment problem with 0.8 in JREs prior to 1.4.