FreeTDS Development Group

["Schörk, Andreas" <andreas.schoerk AT infor.de>]

The next dirty hack,
after this condition include once more:
         if (tds.isResultSet())
         {
            result = true;
                break;
         } else

I am just experimenting. Stored Procedures should be handled like 
batches, because they return UPdateCounts and Resultssets like them.
I will try to fix this at least for 7.0 in the nead future for batches 
and Procedures.
I suspect the code is only able to handle only changes or only resultsets.
So perhaps if you could put the select at the beginning of the code 
you at least would not get an exception.
Andreas

> -----Original Message-----
> From: Anton van Straaten [mailto:anton AT appsolutions.com]
> Sent: Montag, 10. September 2001 13:52
> To: TDS Development Group
> Subject: [freetds] Re: Why can't this stored procedure be called? (Fre
> eTDS_JDBC and jtds)
> 
> 
> Andreas,
> 
> Changing the code as you suggested caused the error message 
> to change.  The
> packet type reported has changed from 0x7c to 0xa0.  Here's 
> the message:
> 
> There was 1 error:
> 1) testProc1(freetds.AsTest)
> java.sql.SQLException: Protocol confusionFound a
> com.internetcds.jdbc.tds.PacketColumnNamesResult (packet type 0xa0)
>         at
> com.internetcds.jdbc.tds.PreparedStatement_base.executeCall(Pr
> eparedStatemen
> t_base.java:275)
>         at
> com.internetcds.jdbc.tds.PreparedStatement_base.execute(Prepar
> edStatement_ba
> se.java:184)
>         at
> com.internetcds.jdbc.tds.PreparedStatement_base.executeQuery(P
> reparedStateme
> nt_base.java:351)
>         at freetds.AsTest.testProc1(AsTest.java:61)
>         at freetds.AsTest.main(AsTest.java:43)
> 
> Please don't spend a lot of time on this if it's not simple 
> to fix.  This
> isn't a high priority problem - for the short term, I'm 
> simply going to have
> my client purchase some commercial driver licenses.  They also plan to
> upgrade their database soon, so if this is just a problem 
> with 6.5, that
> should take care of it.
> 
> OTOH, if it's something you actively want to fix, I'm happy 
> to try anything
> you suggest and report back.
> 
> Thanks for your help,
> 
> Anton
> 
> 
> > -----Original Message-----
> > From: bounce-freetds-132811 AT franklin.oit.unc.edu
> > [mailto:bounce-freetds-132811 AT franklin.oit.unc.edu]On 
> Behalf Of Schörk,
> > Andreas
> > Sent: Monday, September 10, 2001 7:03 AM
> > To: TDS Development Group
> > Subject: [freetds] Re: Why can't this stored procedure be 
> called? (Fre
> > eTDS_JDBC and jtds)
> >
> >
> > Anton
> > Sorry I do not have 6.5 available, I tried by
> > setting the protocol to tds4.2 and tds7.0
> > in both environments it worked with a sql-server 7.0.
> > A blind suggestion:
> > in PreparedStatement_base.java
> > extend:
> >                else if (tmp.getPacketType()
> >                         == TdsDefinitions.TDS_RET_STAT_TOKEN)
> >                {
> >                   // nop
> >                }
> >
> > to
> >                else if (tmp.getPacketType()
> >                         == TdsDefinitions.TDS_RET_STAT_TOKEN
> >                         ||
> >                         tmp.getPacketType() == 
> TdsDefinitions.TDS_PROCID)
> >                {
> >                   // nop
> >                }
> > the procid-packet seems to be ignored all the time it is sent.
> > perhaps this helps.
> > Tell me if it is working
> > Andreas
> >
> >
> 
> 
> ---
> You are currently subscribed to freetds as: [andreas.schoerk AT infor.de]
> To unsubscribe, forward this message to 
> $subst('Email.Unsub')
>