Skip to Content.
Sympa Menu

freetds - RE: Strange error in tsql

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: "'TDS Development Group'" <freetds AT franklin.metalab.unc.edu>
  • Subject: RE: Strange error in tsql
  • Date: Thu, 7 Nov 2002 16:19:21 -0500


> From: Frediano Ziglio [mailto:freddyz77 AT tin.it]
> Sent: November 7, 2002 7:43 AM
>
> 1> select degrees(-0.4)
> 2> go
>
> 166153499493666223.069050350390476800

This is a TDS version 5.0 problem. Here's a log comparison:

4.2:
Sending packet @ 2002-11-07 15:44:10.759943
0000 01 01 00 1d 00 00 00 00 73 65 6c 65 63 74 20 64 |........ select d|
0010 65 67 72 65 65 73 28 2d 30 2e 34 29 0a |egrees(- 0.4).|

5.0:
Sending packet @ 2002-11-07 15:43:34.378723
0000 0f 01 00 23 00 00 00 00 21 16 00 00 00 00 73 65 |...#.... !.....se|
0010 6c 65 63 74 20 64 65 67 72 65 65 73 28 2d 30 2e |lect deg rees(-0.|
0020 34 29 0a |4).|

Reponse headers:
4.2: 0000 04 01 00 2c 00 00 00 00
5.0: 0000 04 01 00 48 00 00 00 00

Then, 4.2 sends a0, a1, ae, d1, fd
Received packet @ 2002-11-07 15:44:10.764306
0000 a0 01 00 00 a1 06 00 0a 00 00 00 6d 08 ae 01 00
0010 00 d1 08 94 01 83 7b 16 eb 36 c0 fd 10 00 02 00
0020 01 00 00 00

But 5.0 sends ee, ae, d1, 1, 0?
Received packet @ 2002-11-07 15:43:34.383225
0000 ee 0d 00 01 00 00 30 0a 00 00 00 6c 21 4d 12 00
0010 ae 01 00 00 d1 21 01 00 00 00 00 00 00 00 00 00
0020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 3e
0030 0e 33 29 12 8c e4 a0 fd 10 00 02 00 01 00 00 00
^^
>From the rest of the log, it looks like we miss the fd?

The rest of the 4.2 log:
2002-11-07 15:44:10.764652 processing result tokens. marker is a0
2002-11-07 15:44:10.764785 processing result tokens. marker is a1
2002-11-07 15:44:10.764902 processing result. type = 109, varint_size 1
2002-11-07 15:44:10.765146 processing result tokens. marker is ae
2002-11-07 15:44:10.765262 inside tds_process_default_tokens() marker is ae
2002-11-07 15:44:10.765402 processing result tokens. marker is d1
2002-11-07 15:44:10.765528 processing row tokens. marker is d1
2002-11-07 15:44:10.765637 processing row. column is 0 varint size = 1
2002-11-07 15:44:10.765746 processing row. column size is 8
2002-11-07 15:44:10.765855 clearing column 0 NULL bit
2002-11-07 15:44:10.766162 processing row tokens. marker is fd
2002-11-07 15:44:10.766281 inside tds_process_end() more_results = 0,
was_cancelled =
2002-11-07 15:44:10.766394 inside tds_process_result_tokens() state is
COMPLETED

The rest of the 5.0 log:
2002-11-07 15:43:34.383710 processing result tokens. marker is ee
2002-11-07 15:43:34.383843 processing result. type = 108, varint_size 1
2002-11-07 15:43:34.383961 processing result. column_size 33
2002-11-07 15:43:34.384195 processing result tokens. marker is ae
2002-11-07 15:43:34.384312 inside tds_process_default_tokens() marker is ae
2002-11-07 15:43:34.384419 processing result tokens. marker is d1
2002-11-07 15:43:34.384538 processing row tokens. marker is d1
2002-11-07 15:43:34.384648 processing row. column is 0 varint size = 1
2002-11-07 15:43:34.384757 processing row. column size is 33
2002-11-07 15:43:34.384868 clearing column 0 NULL bit
2002-11-07 15:43:34.387455 processing row tokens. marker is 1
2002-11-07 15:43:34.387570 inside tds_process_default_tokens() marker is 1
Unknown marker: 1(1)!!
2002-11-07 15:43:34.387727 processing result tokens. marker is 0
2002-11-07 15:43:34.387833 inside tds_process_default_tokens() marker is 0
Unknown marker: 0(0)!!

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