Skip to Content.
Sympa Menu

freetds - RE: still java problem

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: "'TDS Development Group'" <freetds AT franklin.metalab.unc.edu>
  • Subject: RE: still java problem
  • Date: Tue, 25 Jun 2002 11:02:37 -0400


> > > i'm looking in the freeTDS code now, for the point where the
> > > data coming in from the
> > > database isn't put into a resultset yet, but still as bytestream.
> > > that way i could create my own function to return the
> > > bytestream to my own program so
> > > i can send it to my client app, and put it into a resultset there.
> > > or is there any reason i should'nt do anything like this?
> >
> > That's what db-lib and ct-lib do, actually: fetch a row at a time,
> > optionally binding the fields to the program's variables.
> > Your function
> > will just gobble up a bunch of rows, and bundle them into
> > an object for your application's convenience.
> >
> > Which API are you dealing with?
>
> From: Marc Schouten [mailto:m.schouten AT itsec.nl]
> Sent: June 25, 2002 10:38 AM
>
> Java 2.0

Ah. I'm probably no use to you. You're using one of the FreeTDS Java
libraries, about which I know nothing. You said you were looking "in the
freeTDS code", and I thought that might mean you were using the C libraries
from Java, perhaps struggling with libtds.

> (if i read your reply correctly, are you implying i'd be able
> to gather all the rows
> in a byte array if thats more convenient than the normal resultset?)

No, well, maybe. I wasn't implying anything, nothing profound. I meant
there's no TDS reason -- nothing in the protocol -- to prevent you from
reading rows and putting them anywhere you like, including into your
application's notion of a collection object. Sorry to mislead you.

Regards,

--jkl




Archive powered by MHonArc 2.6.24.

Top of Page