FreeTDS Development Group

["Lowden, James K" <LowdenJK AT bernstein.com>]

> From: ZIGLIO Frediano [mailto:Frediano.Ziglio AT vodafone.com]
> Sent: July 28, 2003 10:47 AM
> > 
> > All committed now.  Hope you like it.  :-)  Sorry for the 
> confusion.  
...
> > For the record, I normally test against a 7.0 server in 
> > Australia, and sometimes against Sybase's JDBC server.  I 
> > don't have access to an 8.0 machine.  
>
> Australia ?? A public server to test ??

No, a very nice guy on the list heard my plea and set up a server for me.
His firewall accepts connections from my ip address.  I'm pretty sure he'd
offer it to any of the developers.  

> I tried and get still error...

Ah, because I didn't really commit all the files.  I missed the last
password prompt before writing you.  Gads!  

Now I *know* it's OK.  I just updated from another server and got this:

creating table
insert
insert into #dblib0024 values (0, 'row 000')
insert into #dblib0024 values (1, 'row 001')
insert into #dblib0024 values (2, 'row 002')
insert into #dblib0024 values (3, 'row 003')
insert into #dblib0024 values (4, 'row 004')
insert into #dblib0024 values (5, 'row 005')
insert into #dblib0024 values (6, 'row 006')
insert into #dblib0024 values (7, 'row 007')
insert into #dblib0024 values (8, 'row 008')
insert into #dblib0024 values (9, 'row 009')
select 1
execute master..sp_help sp_helpdblib okay on 
        ...src/dblib/unittests/dbmorecmds.c

I should mention I'm relying on "sp_help" to return two result sets and one
return code (3 results total).  That works on M$ servers.  I'm not sure
about Sybase; and it's version-dependent.  OTOH, it doesn't require
installing our own stored procedure.  

The most robust strategy would be to use dbresults() against sp_help, count
the result sets, then call dbmorecmds() and compare the counts.  

--jkl
-----------------------------------------
The information contained in this transmission may contain privileged and 
confidential information and is intended only for the use of the person(s) 
named above. If you are not the intended recipient, or an employee or agent 
responsible for delivering this message to the intended recipient, any 
review, dissemination, distribution or duplication of this communication is 
strictly prohibited. If you are not the intended recipient, please contact 
the sender immediately by reply e-mail and destroy all copies of the original 
message. Please note that we do not accept account orders and/or instructions 
by e-mail, and therefore will not be responsible for carrying out such orders 
and/or instructions.