Skip to Content.
Sympa Menu

freetds - RE: [freetds] RPC/Packet Type 3 Format

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: 'FreeTDS Development Group' <freetds AT lists.ibiblio.org>
  • Subject: RE: [freetds] RPC/Packet Type 3 Format
  • Date: Thu, 17 Jul 2003 18:28:35 -0400

> From: lists-tds AT mymailfilter.net [mailto:lists-tds AT mymailfilter.net]
> Sent: July 17, 2003 5:32 PM
>
> > create procedure foo @bar char(1) = 'B' output
> > as select @bar='A'
> > return 0
> >
> > Then try these three calls:
> >
> > execute foo
> > execute foo @a
> > execute foo @a output

> I haven't examined these yet

Hmmm. The length byte grows, of course (5a, 88, 96), but the size of the
"prefix" is constant. Pretty much, so is the content. After the second FF
FF FF FF block, there's a slight variation:

1. 00 00 63 1a 00 00 00 09 04 00 01 32 1a 00 00
2. 00 00 63 48 00 00 00 09 04 00 01 32 48 00 00
3. 00 00 63 56 00 00 00 09 04 00 01 32 56 00 00
^^ ^^

What I can tell you is that those bytes don't leap out as having intrinsic
TDS significance. They don't represent a datatype that I know of. They're
not in the server's systypes table, either.

I don't think they're bitmapped values; they're too different:

$ perl -e'printf " %b\n %b\n %b\n", 0x1a, 0x48, 0x56'
11010
1001000
1010110

Maybe try initializing @a to a few different values, and try defining @a as
char(2) and/or varchar(1)? That might offer a few more data points.

--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.






Archive powered by MHonArc 2.6.24.

Top of Page