FreeTDS Development Group

["Castellano, Nicholas" <Nicholas_Castellano AT acml.com>]

Sounds reasonable, and it's mostly how t0022 currently behaves.  However,
the permissions issue isn't really solved by this.  I guess I can make it
exit with a warning instead of failure if the "create procedure" step
returns an error.

Cheers,
--nick

-----Original Message-----
From: bounce-freetds-145195 AT franklin.oit.unc.edu
[mailto:bounce-freetds-145195 AT franklin.oit.unc.edu] 
Sent: Wednesday, November 20, 2002 10:39 PM
To: TDS Development Group
Subject: [freetds] RE: Output parameters (was: Strange things)


On Wed, 20 Nov 2002 16:50:42 -0500, "Castellano, Nicholas"
<Nicholas_Castellano AT acml.com> wrote:
> I think we should just scrap src/dblib/unittests/t0022.c.  It seems to 
> be the general consensus that this is obsolete functionality and just 
> isn't useful behavior anyway.

Nick, 

I really should never answer things when I'm rushing out the door.  I think
I know what you're going after, now, having re-read the thread.  

What you're saying is:

        sprintf(cmd, "declare @b int\nexec t0022 @b = @b output\n");
        fprintf(stdout, "%s\n", cmd);
        dbcmd(dbproc, cmd);

isn't supported (per Bill [thanks Bill!]) on a Microsoft server anymore, so
let's can it.  

The demarcation point, as you guessed and as Bill said, is SQL server 7
service pack 3. 

It would be nice to have the test work for those servers it should work on,
in the way they expect to be used.  

It's an old bugaboo of ours that we can't discover the service pack/whatever
level through the API; we have to parse the version string. 
Brian used to do that for "broken datetimes" until he just gave up and
emulated little endian throughout.  I've complained to Steve Balmer about
this.  Well, actually I haven't, but the effect is the same.  

I think it would be satisfactory if t0022.c remained as is with an advisory
message indicating that failure is normal for Microsoft servers "SQL Server
7.0 service pack 3" and above.  Or, as they say in traffic court, "Guilty
with an explanation."  

If the TDS version is 8+, we *know* it won't work, shouldn't try, and
shouldn't fail.  

If the TDS version is 7 or 8, we can set the procedure name to #t0022,
obviating the permissions problem.  

Now I'm going to look at Bob's dump.  Does any of the aforegoing sound
reasonable to you?

--jkl

---
You are currently subscribed to freetds as: [Nicholas_Castellano AT acml.com]
To unsubscribe, forward this message to
$subst('Email.Unsub')


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.