Director warning Implicit conversion
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 7
- Joined: Mon Jul 11, 2011 6:20 am
Director warning Implicit conversion
Hi all,
i've following warning running a job with the Director:
"Implicit conversion from source type "decimal[38,10]" to result type "decimal[3,0]": Possible range/precision limitation" located in the initial OCI.
The OCI is binded to a View with a join and, in this case, we noticed that metadata of number fields are not recognized properly.
The original datatype was number (3,0) but with the join become number () and Director consider those fields as (38,10) so it is warning.
We tried to put a cast into the View to force metadata to be Number (3,0) but it's still warning.
Any help to remove those warnings would be appreciated
Thanks
Tony
i've following warning running a job with the Director:
"Implicit conversion from source type "decimal[38,10]" to result type "decimal[3,0]": Possible range/precision limitation" located in the initial OCI.
The OCI is binded to a View with a join and, in this case, we noticed that metadata of number fields are not recognized properly.
The original datatype was number (3,0) but with the join become number () and Director consider those fields as (38,10) so it is warning.
We tried to put a cast into the View to force metadata to be Number (3,0) but it's still warning.
Any help to remove those warnings would be appreciated
Thanks
Tony
-
- Premium Member
- Posts: 353
- Joined: Mon Jan 17, 2011 5:03 am
- Location: Mumbai, India
-
- Participant
- Posts: 7
- Joined: Mon Jul 11, 2011 6:20 am
Hi,
the best practice is fixing the real issue rather than avoiding them by using message handler.
In your case try to use the function so that you can avoid the warning,.
the best practice is fixing the real issue rather than avoiding them by using message handler.
In your case try to use the function
Code: Select all
DecimalToDecimal()
pandeeswaran
-
- Participant
- Posts: 7
- Joined: Mon Jul 11, 2011 6:20 am
pandeesh wrote:Hi,
the best practice is fixing the real issue rather than avoiding them by using message handler.
In your case try to use the functionso that you can avoid the warning,.Code: Select all
DecimalToDecimal()
I thought that but the warning is in the initial OCI so i can't put any transformer before...
-
- Participant
- Posts: 597
- Joined: Fri Apr 29, 2005 6:19 am
- Location: Singapore
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
I would be very concerned to verify that every single source value (irrespective of its metadata) could be shoehorned into the target data type. I'd be throwing an IsValid() check in there somewhere.
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.