Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

How to connect to SQL Server?

2 posts in JDBC Connect (product renamed to JConnect) Last posting was on 1997-04-15 17:02:40.0Z
Dmitry Mikhailov Posted on 1997-04-06 10:14:30.0Z
Message-ID: <33477786.2429@mlit.kiev.ua>
Date: Sun, 06 Apr 1997 13:14:30 +0300
From: Dmitry Mikhailov <dmitry@mlit.kiev.ua>
X-Mailer: Mozilla 3.01Gold (Win95; I)
MIME-Version: 1.0
Subject: How to connect to SQL Server?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.jdbcconnect
Lines: 14
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.jdbcconnect:1060
Article PK: 252814

The question is: how to connect to SQL Server if it uses some charset
which is not compatible with iso1 (for instance some Cyrillic encoding)
and I do not want my app to depend on it.

The problem is that if simply connect, I get SQLException. If I connect
and provide "CHARSET" property jConnect opens connection but my app is
completely dependent on this specific installation of SQL Server.

So is there any way to ask jConnect to use the same charset that SQL
Server uses automatically?

Regards,
Dmitry Mikhailov


David Clegg Posted on 1997-04-15 17:02:40.0Z
Message-ID: <3353B4B0.266D544B@sybase.com>
Date: Tue, 15 Apr 1997 10:02:40 -0700
From: David Clegg <davec@sybase.com>
X-Mailer: Mozilla 2.01 (X11; I; Linux 1.2.13 i586)
MIME-Version: 1.0
To: Dmitry Mikhailov <dmitry@mlit.kiev.ua>
Subject: Re: How to connect to SQL Server?
References: <33477786.2429@mlit.kiev.ua>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.jdbcconnect
Lines: 52
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.jdbcconnect:1008
Article PK: 252760

I agree that it would be prefereable to be able to use the
Server's default charset as a default on the client too.
Unfortunately this is simply not how the login sequence with
SQL Server works currently. Furthermore, the jConnect product
does not currently have logic to do conversions from any of the
Sybase/SQL Server multi-byte character sets to UCS2 Unicode, so
even if we could tell the SQL-Server to go ahead and use its
Cyrillic charset, it would get scrambled in jConnect -- sorry.

We have the same issues with SJIS, EUCJIS, etc. and definitely
understand the need to support these conversion for the International
market.

The next feature-release (not the maintenance release I mentioned
in the previous posting) is targetted to have this charset conversion
support. We have all the necessary conversion logic written in
C for OpenClient, just need to port it to Java -- which shouldn't
be too bad, but we'd really like to take advantage of some of the
new JDK1.1 charset conversion classes to implement this (save us
some design work and coding, AND keep the size of the Bytecode
small for ease of downloading) -- but of course this would mean
that currently available Web Browsers (Netscape 3.x, I.E. 3.x, etc)
which are based on the 1.0.2 JDK would not be able to take advantage
of the charset-conversion either...

I cannot give you any firm commitment on when this next release
will be available -- we are haggling out details on that here still.

dave

>
> The question is: how to connect to SQL Server if it uses some charset
> which is not compatible with iso1 (for instance some Cyrillic encoding)
> and I do not want my app to depend on it.
>
> The problem is that if simply connect, I get SQLException. If I connect
> and provide "CHARSET" property jConnect opens connection but my app is
> completely dependent on this specific installation of SQL Server.
>
> So is there any way to ask jConnect to use the same charset that SQL
> Server uses automatically?
>
> Regards,
> Dmitry Mikhailov