Home Page for the TeradataForum

Archives of the TeradataForum

Message Posted: Thu, 11 Aug 2005 @ 13:48:04 GMT

  <Prev Next>   <<First <Prev

Subj:   Re: BTEQ and comments anomaly
From:   Geoffrey Rommel

  Any ideas or is this something I should have already been aware of ...?  

Very interesting! This seems odd at first, but I think I can explain it.

First, remember that a "request" to the server is simply a string of SQL in a single Request packet. As you know, it may contain multiple statements separated by semicolons. For instance, these are multi-statement requests:

     [1] "select current_date; select current_time;"

     [2] "select current_date; /* comment */ select current_time;"

Each client must determine for itself how it is going to pass MSR's, if any, to Teradata. BTEQ, as you know, will not terminate the request until it sees a semicolon not followed by anything. Well, it appears that a comment is something. If it sees a comment, it thinks it could be like example 2, so it keeps going.

Kinda makes sense once you think about it, but it is unexpected.

  <Prev Next>   <<First <Prev
  Top Home Privacy Feedback  
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 15 Jun 2023