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.

LONGVARBINARY under v. 2.0

4 posts in JDBC Connect (product renamed to JConnect) Last posting was on 1997-05-20 20:38:22.0Z
Jerome Scheuring Posted on 1997-04-22 04:35:11.0Z
From: "Jerome Scheuring" <jerome@sylvia.com>
Subject: LONGVARBINARY under v. 2.0
Organization: The Digiratti Companies
Message-ID: <01bc4eaf$f50ca060$bb9058cf@dominic>
X-Newsreader: Microsoft Internet News 4.70.1161
Newsgroups: sybase.public.jdbcconnect
Date: Tue, 22 Apr 1997 00:35:11 -0400
Lines: 30
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.jdbcconnect:955
Article PK: 252708

We downloaded the jConnect beta, and, within the memory limitations of our
meager Sparc 5, it was happily able to handle Sybase System XI image data
on read and write, using the PreparedStatement.setBinaryStream() and
ResultSet.getBinaryStream() methods.

The same program, run under the jConnect 2.0 release version, balks on
write with: "java.sql.SQLException: LONGVARBINARY parameters not supported
by this Database".

The jConnect 2.0 release notes for Database Dependent Problems: SQL Server,
state that "...PreparedStatement cannot be used to insert any binary/text
data longer than 255 characters/bytes."

Some of our applications depend on the ability to write large blocks of
binary data (500K and up), and our tests on the jConnect beta indicated
that it was the best option for us-- but this news about the release is
troublesome.

Is this accurate? Was there a problem that caused the engineers to remove
this functionality from the released version? Is there a viable workaround
for large images, i.e., larger than the limits on literals in update
statements?

TIA,

Jerome Scheuring
Software Author
Sylvia Enterprises

jerome@sylvia.com


David Clegg Posted on 1997-04-28 17:28:11.0Z
Message-ID: <3364DE2B.466B97C8@sybase.com>
Date: Mon, 28 Apr 1997 10:28:11 -0700
From: David Clegg <davec@sybase.com>
X-Mailer: Mozilla 2.01 (X11; I; Linux 1.2.13 i586)
MIME-Version: 1.0
Subject: Re: LONGVARBINARY under v. 2.0
References: <01bc4eaf$f50ca060$bb9058cf@dominic>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.jdbcconnect
Lines: 38
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.jdbcconnect:915
Article PK: 252666

Support for insert of LONGVARBINARY and LONGVARCHAR was added to
jConnect just after the GA release. It has been available in the
Trial download product for a while. An official update to the GA
product is available through Tech. Support.

dave

>
> We downloaded the jConnect beta, and, within the memory limitations of our
> meager Sparc 5, it was happily able to handle Sybase System XI image data
> on read and write, using the PreparedStatement.setBinaryStream() and
> ResultSet.getBinaryStream() methods.
>
> The same program, run under the jConnect 2.0 release version, balks on
> write with: "java.sql.SQLException: LONGVARBINARY parameters not supported
> by this Database".
>
> The jConnect 2.0 release notes for Database Dependent Problems: SQL Server,
> state that "...PreparedStatement cannot be used to insert any binary/text
> data longer than 255 characters/bytes."
>
> Some of our applications depend on the ability to write large blocks of
> binary data (500K and up), and our tests on the jConnect beta indicated
> that it was the best option for us-- but this news about the release is
> troublesome.
>
> Is this accurate? Was there a problem that caused the engineers to remove
> this functionality from the released version? Is there a viable workaround
> for large images, i.e., larger than the limits on literals in update
> statements?
>
> TIA,
>
> Jerome Scheuring
> Software Author
> Sylvia Enterprises
>
> jerome@sylvia.com


Jon Nordby Posted on 1997-05-20 16:58:24.0Z
From: "Jon Nordby" <nordby@channelpoint.com>
Subject: Re: LONGVARBINARY under v. 2.0
References: <01bc4eaf$f50ca060$bb9058cf@dominic> <3364DE2B.466B97C8@sybase.com>
Organization: ChannelPoint
Message-ID: <01bc6548$0e0e9a60$512fd626@nord>
X-Newsreader: Microsoft Internet News 4.70.1161
Newsgroups: sybase.public.jdbcconnect
Date: Tue, 20 May 1997 12:58:24 -0400
Lines: 5
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.jdbcconnect:812
Article PK: 252565

Can I read into this that 2.1 does support LONG BINARY datatypes with
arbitrary lengths using SQL Server NT PRO? Is 2.1 a supported product yet?

Thanks for your help, Jon.


Lance Andersen Posted on 1997-05-20 20:38:22.0Z
Message-ID: <33820BBE.4A01@sybase.com>
Date: Tue, 20 May 1997 16:38:22 -0400
From: Lance Andersen <lancea@sybase.com>
X-Mailer: Mozilla 3.01Gold (X11; I; SunOS 5.5.1 sun4m)
MIME-Version: 1.0
To: Jon Nordby <nordby@channelpoint.com>
Subject: Re: LONGVARBINARY under v. 2.0
References: <01bc4eaf$f50ca060$bb9058cf@dominic> <3364DE2B.466B97C8@sybase.com> <01bc6548$0e0e9a60$512fd626@nord>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.jdbcconnect
Lines: 18
Path: forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.jdbcconnect:805
Article PK: 252557

Yes, 2.1 is supported product on all platforms.


-lance

Jon Nordby wrote:
>
> Can I read into this that 2.1 does support LONG BINARY datatypes with
> arbitrary lengths using SQL Server NT PRO? Is 2.1 a supported product yet?
>
> Thanks for your help, Jon.

--
===============================================================================
Lance J. Andersen Email: lancea@sybase.com
Sybase Technical Support Phone:(617) 564-6336
77 South Bedford Street Fax: (617) 564-6148
Burlington, MA 01803

The Dark Knight Returns!!! Let's Go Penguins!!!
===============================================================================