Unfortunately, Java and especially JDBC is one of those places where I
cannot even maintain the illusion of "knowing everything". :-)
From colleagues of mine who work in the UNIX/Java sphere, the impression I
have gotten is that many/most of the JDBC stuff was done prior to SQL 7.0,
and thus had no Unicode fields to run against. This makes them always
convert using some code page (probably using the non-Unicode SQLS scheme
which is to base it off the collation choice of the server, which until 7.0
was actually the ideal plan).
I would hope that my (limited) knowledge is obsolete and that work has been
done to make things work in SQLS 7.0 and 2000 Unicode fields through JDBC.
Can someone confirm or deny this?
michka
----- Original Message -----
From: "Tex Texin" <texin@progress.com>
To: "Michael (michka) Kaplan" <michka@trigeminal.com>
Cc: "Unicode List" <unicode@unicode.org>
Sent: Wednesday, July 26, 2000 8:49 AM
Subject: Re: SQL Server and Unicode
> Michael,
> Do you know of JDBC drivers that support using
> queries and updates of UCS-2 (or UTF-16) text in the SQL Server database?
>
> I am having trouble confirming which ones support this and have confirmed,
> that
> even though Java is Unicode-based, some of the drivers only work provided
> the text is to be converted to some code page other than Unicode for
storage
> and retrieval on the database.
>
> tex
>
>
> "Michael (michka) Kaplan" wrote:
> >
> > SQL Server supports the datatypes NTEXT, NCHAR, and NVARCHAR, all of
which
> > are of type UCS-2. When such a column indexed, then the index is Unicode
(I
> > am not sure if this what you mean).
> >
> > SQL Server 7.0 only supports one language collation at the server
level....
> > this choice affects the actual ordering of all such indexes.
> >
> > SQL Server 2000 supports a COLLATE keyword that allows you to specify a
> > collation at the database or field level and thus choose a different
> > language for such columns/indexes if you like (I discuss practical
details
> > and implications of this feature in an upcoming article in the Visual
Basic
> > Programmer's Journal, tentatively scheduled for November).
> >
> > In any case, you can certainly query and such field in either SQL 7.0 or
in
> > SQL 2000.
> >
> > Hopefully this answers your question; if not, let me know. :-)
> >
> > michka
> >
> > ----- Original Message -----
> > From: "pierre vaures" <p-vaures@heimannsystems.fr>
> > To: "Unicode List" <unicode@unicode.org>
> > Sent: Wednesday, July 26, 2000 1:23 AM
> > Subject: SQL Server and Unicode
> >
> > > To Whom It May Concern:
> > >
> > >
> > > SQL server is in the Unicode Products WebSite described as Unicode
> > enables.
> > >
> > > What we would like to know is :
> > >
> > > a - Does SQL Server allows to set as an index a field in Unicode
standard?
> > > b - Can you make SQL query on this particular field?
> > >
> > > If you have any information, or ideas, thanks for your help.
> > >
> > > Regards,
> > >
> > > Pierre
> > >
>
> --
> If practice makes perfect, and nobody's perfect, why practice?
> --------------------------------------------------------------------------
-- > Tex Texin Director, International Products > mailto:texin@progress.com +1-781-280-4271 Fax:+1-781-280-4655 > Progress Software Corp. 14 Oak Park, Bedford, MA 01730 > > http://www.progress.com #1 Embedded Database > http://www.SonicMQ.com JMS Messaging- Best Middleware Award > http://www.aspconnections.com #1 provider in the ASP marketplace > http://www.NuSphere.com Open Source software and services for MySQL > > Globalization Program http://www.progress.com/partners/globalization.htm > -------------------------------------------------------------------------- --- > Come to the Panel on Open Source Approaches to Unicode Libraries > at the Sept. Unicode Conference http://www.unicode.org/iuc/iuc17 >
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:21:06 EDT