Ok, as a newbee I have a question about this null handling. I was not doing anything on null handling and the job started to give a lot of null errors. So, after doing a search on the board here, I decided to try null field length = 0 approach.
the designer of the PX null handing system (an illegitimate issue from Mary Shelley and Freddy Kruger) has come up with some really wonderful ideas for torture - and when combined with the PX Sequential file stage (coded by a temporary resident from the depths of the 7th level of hell who was banished from there for cruelty) it is enough to drive even grown men to drink!
Take out the null_length in your case. Which null error handling message are you getting? Normally it should suffice to set the row attributes for null_value to what you want.
Last edited by ArndW on Fri Oct 28, 2005 10:04 am, edited 1 time in total.
I must agree with Arnd on the developer of null handling capabilities in PX. However, what are you trying to do (read or write the file), and what is your desired outcome (leave an empty string, print a specific string, etc)?
track_star wrote:I must agree with Arnd on the developer of null handling capabilities in PX. However, what are you trying to do (read or write the file), and what is your desired outcome (leave an empty string, print a specific string, etc)?
My desire is simple, to read data from a SQL table into a sq file. Period.
I also noticed that there are some problems with metadata imports. The fields that I import the metadata from Oracle table have "Yes" in Oracle. When I import them DS puts "No" in the column definition. I have to go and correct the fields manualy after the import.
Arnd is right, a beer or ten can make a fat girl look like a model but won't cure the blues for null fields..
Ray, you make me want to come to Vegas and get into "silly jokes" contests with you
OE_PRTIMESHEET: When checking operator: When binding output interface field "PRID" to field "PRID": Implicit conversion from source type "int64" to result type "decimal[10,0]": Possible range limitation.
both are valid in the PX world, the warning can avoided by doing an explicit conversion in a modify stage, and the latter error needs to be dealt with in an explicit handler - either for that specific column (edit row attributes) or for that datatype.
If u want handle nulls and assign default value, go for NullToValue function.
If u want to assign null value to target column, u dont need to handle at all in px.
Thx,
Rao.
PilotBaha wrote:Ok, as a newbee I have a question about this null handling. I was not doing anything on null handling and the job started to give a lot of null errors. So, after doing a search on the board here, I decided to try null field length = 0 approach.
OE_PRTIMESHEET: When checking operator: When binding output interface field "PRID" to field "PRID": Implicit conversion from source type "int64" to result type "decimal[10,0]": Possible range limitation.