FreeTDS Development Group

["Chris McDaniel" <Chris.McDaniel AT telus.com>]

I thought about that, but I get an error back saying I can't use the OUTPUT
notation if I'm passing in a constant, but passing a null breaks DBI, so I'm
a little confused...  I am not a T-SQL expert by any strech, but I was
guessing that since the variables are declared with the output statement in
the stored procedure, maybe I didn't have to do it too.  I'll dredge the DBI
documentation again and let y'all know if I find anything.

-----Original Message-----
From: Lowden, James K [mailto:LowdenJK AT bernstein.com]
Sent: January 6, 2003 3:09 PM
To: 'freetds AT lists.ibiblio.org'
Subject: RE: [freetds] DBD::ODBC (0.45), MS SQL, unixODBC, FreeTDS
(CVS), bind_param_ino ut


> From: Chris McDaniel [mailto:Chris.McDaniel AT telus.com]
> Sent: January 6, 2003 2:38 PM
> 
> The whole log can be perused at
> http://nicotine.golden.net/~chrism/freetds.log

That makes it pretty clear.  Your SQL needs "OUTPUT" after every output
parameter.  The server won't send back a value otherwise.  

Try something more like "execute p_ccs_MakeBooking ... @AvailableInd=?
OUTPUT".  

I don't know who's supposed to insert "OUTPUT" into the SQL.  It seems like
"inout" in 

$sth->bind_param_inout(1, \$DDI, 32, DBI::SQL_VARCHAR);

would be clue to DBD::ODBC (or DBI?).  But maybe it's your job even so.  

--jkl

0000  01 00 02 00 00 00 00 00  65 78 65 63 75 74 65 20   |........ execute |
0010  70 5f 63 63 73 5f 4d 61  6b 65 42 6f 6f 6b 69 6e   |p_ccs_Ma keBookin|
0020  67 20 40 43 6c 69 65 6e  74 41 63 63 6f 75 6e 74   |g @Clien tAccount|
0030  3d 22 33 36 32 31 31 38  22 2c 20 40 50 61 79 6d   |="362118 ", @Paym|
0040  65 6e 74 4e 75 6d 62 65  72 3d 22 38 30 38 30 38   |entNumbe r="80808|
0050  30 22 2c 20 40 43 6f 6e  66 65 72 65 6e 63 65 4e   |0", @Con ferenceN|
0060  61 6d 65 3d 22 53 63 72  69 70 74 73 3a 20 30 36   |ame="Scr ipts: 06|
0070  3a 34 37 20 42 6f 6f 6b  65 64 22 2c 20 40 43 6f   |:47 Book ed", @Co|
0080  6e 66 65 72 65 6e 63 65  43 6f 6d 6d 65 6e 74 73   |nference Comments|
0090  3d 22 43 72 65 61 74 65  64 20 62 79 20 43 68 72   |="Create d by Chr|
00a0  69 73 20 4d 63 44 61 6e  69 65 6c 22 2c 20 40 43   |is McDan iel", @C|
00b0  6f 6e 66 65 72 65 6e 63  65 54 79 70 65 3d 31 2c   |onferenc eType=1,|
00c0  20 40 4c 61 6e 67 75 61  67 65 54 79 70 65 3d 31   | @Langua geType=1|
00d0  2c 20 40 50 72 69 6f 72  69 74 79 54 79 70 65 3d   |, @Prior ityType=|
00e0  32 2c 20 40 53 74 61 72  74 44 61 74 65 54 69 6d   |2, @Star tDateTim|
00f0  65 3d 22 32 30 30 33 2d  30 32 2d 30 31 20 31 32   |e="2003- 02-01 12|
0100  3a 33 30 3a 30 30 22 2c  20 40 44 75 72 61 74 69   |:30:00",  @Durati|
0110  6f 6e 3d 31 30 2c 20 40  43 6f 6e 66 65 72 65 65   |on=10, @ Conferee|
0120  73 3d 33 2c 20 40 53 75  62 43 6f 6e 66 65 72 65   |s=3, @Su bConfere|
0130  65 73 3d 30 2c 20 40 54  6f 6c 6c 46 72 65 65 49   |es=0, @T ollFreeI|
0140  6e 64 3d 31 2c 20 40 52  65 63 6f 72 64 69 6e 67   |nd=1, @R ecording|
0150  49 6e 64 3d 31 2c 20 40  45 6e 74 65 72 54 6f 6e   |Ind=1, @ EnterTon|
0160  65 49 6e 64 3d 31 2c 20  40 4c 65 61 76 69 6e 67   |eInd=1,  @Leaving|
0170  54 6f 6e 65 49 6e 64 3d  31 2c 20 40 51 61 6e 64   |ToneInd= 1, @Qand|
0180  41 49 6e 64 3d 31 2c 20  40 50 6f 6c 6c 69 6e 67   |AInd=1,  @Polling|
0190  49 6e 64 3d 31 2c 20 40  52 6f 6c 6c 43 61 6c 6c   |Ind=1, @ RollCall|
01a0  49 6e 64 3d 31 2c 20 40  42 72 6f 61 64 63 61 73   |Ind=1, @ Broadcas|
01b0  74 49 6e 64 3d 31 2c 20  40 44 65 6d 61 6e 64 49   |tInd=1,  @DemandI|
01c0  6e 64 3d 30 2c 20 40 4d  6f 64 65 72 61 74 6f 72   |nd=0, @M oderator|
01d0  49 6e 64 3d 31 2c 20 40  41 75 74 6f 50 49 4e 49   |Ind=1, @ AutoPINI|
01e0  6e 64 3d 31 2c 20 40 44  44 49 3d 27 31 27 2c 20   |nd=1, @D DI='1', |
01f0  40 43 50 49 4e 3d 27 30  27 2c 20 40 4d 50 49 4e   |@CPIN='0 ', @MPIN|


Sending packet @ 2003-01-06 11:09:19.672544
0000  01 01 00 a8 00 00 00 00  3d 27 30 27 2c 20 40 52   |........ ='0', @R|
0010  65 63 6f 72 64 69 6e 67  50 49 4e 3d 22 35 35 35   |ecording PIN="555|
0020  22 2c 20 40 49 6e 66 6f  72 6d 61 74 69 6f 6e 3d   |", @Info rmation=|
0030  27 20 20 20 20 20 20 20  20 20 20 20 20 20 20 20   |'                |
0040  20 20 20 20 20 20 20 20  20 20 20 20 20 20 20 20   |                 |
0050  20 20 20 20 20 20 20 20  20 20 20 20 20 20 27 2c   |               ',|
0060  20 40 52 65 73 65 72 76  61 74 69 6f 6e 52 65 66   | @Reserv ationRef|
0070  3d 30 2c 20 40 43 6f 6e  66 65 72 65 6e 63 65 52   |=0, @Con ferenceR|
0080  65 66 3d 30 2c 20 40 41  63 74 75 61 6c 44 75 72   |ef=0, @A ctualDur|
0090  61 74 69 6f 6e 3d 30 2c  20 40 41 76 61 69 6c 61   |ation=0,  @Availa|
00a0  62 6c 65 49 6e 64 3d 30                            |bleInd=0|








> -----Original Message-----
> From: Lowden, James K [mailto:LowdenJK AT bernstein.com]
> Sent: January 6, 2003 2:02 PM
> To: Chris McDaniel
> Subject: RE: [freetds] DBD::ODBC (0.45), MS SQL, unixODBC, FreeTDS
> (CVS), bind_param_ino ut
> 
> 
> Sorry, Chris, not enough information.  Can you post the whole 
> log to a www
> site somewhere?  (Beware the top of the log includes your password).  
> 
> I tried to release your message, but either my firewall won't 
> let me or the
> admin site is down.  
> 
> In the log, you should see three things amidst everything else:
> 
> 1.  Your query being sent.
> 2.  The result set arriving.
> 3.  The parameter values arriving.  
> 
> in that order.  I'd like to see all of that.  If you can't 
> post all that,
> perhaps you could trim the query so that the log is smaller.  
> 
> I'm not sure what form #3 will take; the protocol has a few 
> flavors.  Also
> you should know that I wrote the db-lib output parameter handling, but
> Frediano did the protocol and ODBC work.  He's the fellow who 
> most needs
> your logs, which is why list/www postings are better.  
> 
> Regards, 
> 
> --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.


_______________________________________________
FreeTDS mailing list
FreeTDS AT lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/freetds