FreeTDS Development Group

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

I created in the newest sourceforge-version a JUNIT-Test- Called AsTest.
you can call it by:

doTest freetds.AsTest

I fear you have to access the CVS-Repository to do this. 
There are problems at the moment with the mixing of Resultset-producing and
not producing Batches. But they normally return at least the Resultsets.

Could you look at the code in AsTest.java and suggest the changes that lead
to
your problem ?
Andreas

> -----Original Message-----
> From: Anton van Straaten [mailto:anton AT appsolutions.com]
> Sent: Montag, 10. September 2001 09:42
> To: TDS Development Group
> Subject: [freetds] Re: Why can't this stored procedure be called?
> (FreeTDS_JDBC and jtds)
> 
> 
> Andreas wrote:
> > Just in Case: [...] the ' should be duplicated
> 
> Thanks, good catch, but that's not the problem either.  I 
> made the dumb
> mistake of changing the text when I wrote the email - it used 
> to say 'Did it
> work?'.
> 
> To summarize for anyone else reading this, here's a stored 
> procedure for MS
> SQL 6.5 which works fine in all environments, but I can't 
> successfully call
> with any version of the FreeTDS JDBC drivers, including the 
> SourceForge
> version or Curt Hagenlocher's version:
> 
>       create procedure spTestExec as
>               create table #tmp ( Result varchar(50) )
>               insert #tmp execute spTestExec2
>               select * from #tmp
> 
> The above depends on the following procedure:
> 
>       create procedure spTestExec2 as
>               select 'Did it work?' as Result -- substitute 
> text depending on degree of
> optimism
> 
> If anyone is kind enough to take the time to try this and can 
> actually get
> it working with SQL 6.5 and FreeTDS JDBC, please let me know, 
> because then
> at least I'll know that there's something wrong with my setup 
> or something
> I'm doing, rather than with the FreeTDS JDBC driver.  At the 
> moment, I must
> admit I suspect a FreeTDS JDBC limitation, although it's not 
> clear to me why
> the innards of a stored procedure should affect FreeTDS, 
> other than the
> speculation about multiple result sets in my first message.
> 
> Anton
> 
> 
> ---
> You are currently subscribed to freetds as: [andreas.schoerk AT infor.de]
> To unsubscribe, forward this message to 
> $subst('Email.Unsub')
>