Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.
Moderators: chulett , rschirm , roy
bikan
Premium Member
Posts: 128 Joined: Thu Jun 08, 2006 5:27 am
Post
by bikan » Mon Jun 16, 2008 12:20 am
hi I have value
2008-03-19
I am checking it in ISvalid function as timestamp. will this is valid will pass this value
Also I have value "2008-03-19 04:22:59" & i am checking it with DATE dataype in isvalid function. Will it will pass the value
ArndW
Participant
Posts: 16318 Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:
Post
by ArndW » Mon Jun 16, 2008 12:29 am
No & No. "2008-03-19" is not a valid timestamp, and "2008-03-19 04:22:59" is not a valid date.
kduke
Charter Member
Posts: 5227 Joined: Thu May 29, 2003 9:47 am
Location: Dallas, TX
Contact:
Post
by kduke » Mon Jun 16, 2008 8:48 am
I think it is a bug. It should validate in as a DATE.
Mamu Kim
Tej
Participant
Posts: 30 Joined: Tue May 20, 2008 11:44 pm
Location: hyderabad
Post
by Tej » Mon Jun 16, 2008 9:32 am
giving the date as value and ISvalid function assing to the timestamp how can it work
it is not a timestamp
kduke
Charter Member
Posts: 5227 Joined: Thu May 29, 2003 9:47 am
Location: Dallas, TX
Contact:
Post
by kduke » Mon Jun 16, 2008 2:20 pm
I misread the question. In server the oconv/iconv are smart enough to convert these. I am saying on the first one if we validate on a DATE type 2008-06-16 we are failing. The job is failing hard when it gets really bad values. The purpose of this function should be to tell us it will convert without errors.
Mamu Kim