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.

Full JDBC compliance

3 posts in JDBC Connect (product renamed to JConnect) Last posting was on 1997-04-15 16:35:55.0Z
Dmitry Mikhailov Posted on 1997-04-06 10:08:07.0Z
Message-ID: <33477607.45FD@mlit.kiev.ua>
Date: Sun, 06 Apr 1997 13:08:07 +0300
From: Dmitry Mikhailov <dmitry@mlit.kiev.ua>
X-Mailer: Mozilla 3.01Gold (Win95; I)
MIME-Version: 1.0
Subject: Full JDBC compliance
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.jdbcconnect
Lines: 7
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.jdbcconnect:1061
Article PK: 252812

When does Sybase expect to have compeletely JDBC-compliant product?
Under "completeness" I mean full implementation of all methods (maybe
but few that cannot be implemented with SQL Server) and no "not
implemented" SQL Exceptions.


David Clegg Posted on 1997-04-15 16:35:55.0Z
Message-ID: <3353AE6B.D5E7FB8@sybase.com>
Date: Tue, 15 Apr 1997 09:35:55 -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: Full JDBC compliance
References: <33477607.45FD@mlit.kiev.ua>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.jdbcconnect
Lines: 24
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.jdbcconnect:1009
Article PK: 252761

We are working on a "Maintenance" release of jConnect now, hope
to have it out within the next couple months. This release will
fill in the remaining un-implemented methods from the JDBC 1.2
standard, and of course fix any bugs which get reported -- Have
not had ANY product bugs entered against the GA product yet though!


We will be Beta-testing this stuff from the www.sybase.com
download site as we get the work done. I expect to have the
Statement.setMaxFieldSize()
PreparedStatement.setUnicodeStream()
PreparedStatement.setAsciiStream()
ResultSet.getUnicodeStream()
ResultSet.getAsciiStream()
Methods available by the end of the week.

dave

> When does Sybase expect to have compeletely JDBC-compliant product?
> Under "completeness" I mean full implementation of all methods (maybe
> but few that cannot be implemented with SQL Server) and no "not
> implemented" SQL Exceptions.


Kevin P. Micalizzi Posted on 1997-04-07 09:44:31.0Z
From: "Kevin P. Micalizzi " <kevinmic@sybase.com>
Subject: Re: Full JDBC compliance
References: <33477607.45FD@mlit.kiev.ua>
Organization: Sybase, Inc.
Message-ID: <01bc4340$f071f7a0$95b75dc7@kevinmic.powersoft.com>
X-Newsreader: Microsoft Internet News 4.70.1155
Newsgroups: sybase.public.jdbcconnect
Date: Mon, 07 Apr 1997 05:44:31 -0400
Lines: 25
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.jdbcconnect:1055
Article PK: 252804

Taken from jConnect FAQ
(http://www.sybase.com/products/internet/jconnect/jdbcfaq.html)

>>Is there any plan to include multi-language support in jConnect
>> for JDBC?
>>
>> We don't plan to provide I18N internationalization &
localization support
>> in the release 1.0 of jConnect for JDBC. This feature will be

available in
>> future releases of the product."

HTH


-kevin
**************************************************
Kevin P. Micalizzi
kmicalizzi@powersoft.com / kevinmic@sybase.com
Powersoft Web Master
Tel: 508-287-1905
**************************************************

Dmitry Mikhailov <dmitry@mlit.kiev.ua> wrote in article
<33477607.45FD@mlit.kiev.ua>...
> When does Sybase expect to have compeletely JDBC-compliant product?
> Under "completeness" I mean full implementation of all methods (maybe
> but few that cannot be implemented with SQL Server) and no "not
> implemented" SQL Exceptions.
>