Home Page for the TeradataForum

Archives of the TeradataForum

Message Posted: Tue, 02 Apr 2002 @ 14:11:56 GMT

  <Prev Next>   <<First <Prev

Subj:   Re: Numeric Value Validation
From:   Dieter Nöth

  I totally agree - position is nicer. But we have to add two more conditions on + and - (both assume that + or - have to be on the first position of the string (after applying the trim function)).  

Forgot about that ;-(

  I disagree in waiting for User Defined Functions - Teradata already checks for if the strings can be converted into what ever - so why is it not possible to implement an function which return the result of the check as true or false? Why should every Teradata implementation program the checks for every data type and format on there own? Would it not be better if NCR does the job once?  

I just wanted to say, that it will be easy to create all the missing functions when UDFs are available. The reason _not_ to implement something is always "It's not an ANSI standard" :-((

But ANSI is weak in different parts, especially string-handling. I'm waiting for some stuff, e.g. CAST bytes into something else REPLACE a substring with a new one extended EXTRACT(day of week) extended POSITION: the 2nd/3rd occurance of a substring or finding backwards...


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