Re: Update Subset Of Column

Hi Buzz,

It's difficult to tell which ( it's complaining about, but I noticed that

Substr(readDt,1,4)=x'00403F


is problematic because x'00403F' is only 3 characters, and the substring is expecting 4.

--
*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
petercdow@xxxxxxxxx <mailto:petercdow@xxxxxxxxx>
pdow@xxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxx> /

On 4/6/2020 1:34 PM, Buzz Fenner wrote:

On Mon, 6 Apr 2020, Vernon Hamberg wrote:

Hey Buzz - how about making it a capital F? and capital X?

No joy, Vern. The syntax checker starts slapping my hand right after the first '(' so that suggests nothing other than the column name is a valid token after 'SET'.

Here's the output:

Update biltst.lmetrp1 Set Substr(readDt,1,4)=x'00403F',Substr(readTp,1,1)='S' Where Substr(Char(mtrLoc),1,4)='2190' And mtrTyp='W' And Substr(readTp,1,1)=' '

SQL State: 42601
Vendor Code: -104
Message: [SQL0104] Token ( was not valid. Valid tokens: =. Cause . . . . . : A syntax error was detected at token (. Token ( is not a valid token. A partial list of valid tokens is =. This list assumes that the statement is correct up to the token. The error may be earlier in the statement, but the syntax of the statement appears to be valid up to this point. Recovery . . . : Do one or more of the following and try the request again: -- Verify the SQL statement in the area of the token (. Correct the statement. The error could be a missing comma or quotation mark, it could be a misspelled word, or it could be related to the order of clauses. -- If the error token is <END-OF-STATEMENT>, correct the SQL statement because it does not end with a valid clause.

I had tried various combos of upper/lower 'x' & 'f'.

--Buzz


________________________________

This electronic mail transmission may contain confidential or privileged information. If you believe that you have received this message in error, please notify the sender by reply transmission and delete the message without copying or disclosing it.