Hi,
I have a job where i read the records from dataset, sort using sort stage, join with a table, then add some extra columns in a transformer and insert the records in the target Oracle table.
Even if there are null values in the input columns, i just pass it as it is to the output table.
do i need to do any null handling before inserting..i see in some of the existing jobs that they have done something like If isnull(col) then setnull else col.
but i dont see a need of it..i dont see any reject records because of null values in some of the columns, but want to check if it is a best practice to do that.
null handling in transformer/join stages
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
You will, however, need to prevent functions in the Transformer stage from receiving NULL as an argument.
(Relaxing this restriction is on the road map, maybe even in the next version of Information Server.)
Code: Select all
If IsNull(inlink.fieldname) Then SetNull() Else function(inlink.fieldname)
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.