FreeTDS Development Group

["Eric Mountain" <e.mountain AT dev.amadeus.net>]

-----Original Message-----
From: Rahul Guha <rfguha AT yahoo.com>
To: TDS Development Group <freetds AT franklin.oit.unc.edu>
Date: Wednesday, 15 September, 1999 22:48
Subject: [freetds] BIG PROBLEM WITH TDS and MS SQL SERVER


>The problem is this....
>
>When  try to connect to my database and run the query
>the socket stays open during the entire time till
>the last result in the result set has been processed
>
>when i connect to the database with inetdae trial version
>the socket is closed as soon as the resultset is obtained
>
>so why does freeTDS keep the socket open unnecessarily
>
>it takes me almost 8 mins to process a result set and for that
>entire 8 mins the socket to the DB is open but
>with inetdae the socket stays open only for 10 secs

>
>when i try to close the statement or connection prior to
>using rs.next()
>the rs.next() function gives the error connection closed
>
>why is this so?

Because, when you do

ResultSet rs = statement.executeQuery(sqlstmt);

... you get an object back which allows you to then ask for the rows you are
interested in.

rs.next()

... fetches the next row from the server - so you need your connection to
the server to do this.

I don't know what your inetdae thing is, but my guess is it is doing:
1. open connection to server
2. send query
3. get all results back
4. close connection
5. give all results to the user in one go

It is silly to disconnect: connecting is a costly operation.  Keeping the
socket is cheap.

>please help
>
>i tried to find out where the problem is but the code is
>quite difficult to understand
>
>if anyone has a solution please email me
>
>at
>
>rfguha AT yahoo.com
>
>any help would be much appreciated
>
>
>-rahul
>
>---
>You are currently subscribed to freetds as: eric AT minouche.demon.co.uk
>To unsubscribe, forward this message to
$subst('Email.Unsub')
>