Talend tmap nullable field usage - etl

Could you please explain the significance of nullable check box in various places?
In tmap, under middle section with heading Var
In tmap under Input/output sections at the bottom panel
In any other component where we define the schema
Also, could you please explain the significance of KEY field while defining any schema.

In tmap, under middle section with heading Var - it will accespt the null as value. if you are processing values which may result as null then check for nullable.
In tmap under Input/output sections at the bottom panel
it has the same meaning column can accept or recieved null values.
In any other component where we define the schema
very where it has the same meaning if you want to define a column with null acceptance then check this property other wise Talend will not accept null values and may raise the error.
Also, could you please explain the significance of KEY field while defining any schema.
Key filed denotes a Key column for database or any processing column, but most of time key property treated as KEY column(primary key..) for most of the databases.

Related

How do you show all rows with missing fields in Crystal Reports?

I'm struggling with Crystal Reports suppressing rows whenever I add a field that some rows may not have data in.
I've been able to fix some of the rows and make them show by using the formula:
if not isnull({field}) then {field} else "Arbitrary string to make row display"
This at least fills in the absent field with something and displays the row.
Do I really have to try and identify every field that may have incomplete data for some rows? Or is there some global method to make all rows show no matter what?
Something like: If isnull(ANYTHING) then " "?
you can do right click on the field, then under suppress, click the formula icon beside it and you can input there the conditions.
You can try the following in report options:
Convert Database NULL values to Default
Convert Other NULL values to Default.
This is hidden in File > Report Options. I have used Convert Database NULL Values to default to show 0's instead of blanks for null valued summaries

Storing and retrieving value inconsistency in a table in Oracle

I am facing a weird problem. I have a table (observation_measurement) in oracle DB and it has many fields. One field name is observation_name. this observation_name field stores different measurements with it's value from a text file.
For example, observation_name stores four measurements a,b,c,d (name of the measurements) and their corresponding values 1,2,3,4 (values of those measurements).
Later it is reading same text file. This time that text file has three measurements a,b,d (c is not there) and their values are 7,8,9 and then store in the table. So, if I need the latest values for all observation_names then I should get a=7,b=8,c=null,d=9. But it is giving me
a=7,b=8,c=3,d=9. I dont know why it is getting old data for c measurement.
Any ideas?
NULL has to be handled specially in Oracle, like IS NULL or IS NOT NULL.
Hope, your update logic involves some validation over the column and it leaves NULL values untreated.
Since, some validation fails because of NULL, the old value is retained in the table.
Can you please update your question with the Query used to UPDATE the table.

Explicit null string in flat files that are imported with SQL*Loader

I am using Oracle's SQL*Loader to import flat files into the database. Is there an explicit NULL string in SQL*Loader, like \N in PostgreSQL, that can be used instead of an empty string? Or is there an option in the control file that can be used to set a NULL string, e.g. NULL AS ''?
Like Alex said, empty fields are treated as NULL in Oracle. You may need to set default values or conditions on your table itself if you want to differentiate somehow. You might be able to find a solution to your issue from here using the WHEN, NULLIF, and DEFAULTIF Clauses.
Ex from the docs:
fixed_field CHAR(2) NULLIF fixed_field=BLANKS
But ultimately, I don't know how you differentiate between empty fields and null fields in a flat fixed-width file. Either the data is present or its position filled with white space. Unless you have specific rules that you're going to apply to make that determination, I don't see a difference between the two.

Queries with NSValueTransformer

1.In my application there is a requirement to display certain value (among the 3 different values) in each row of the table column,the value to be displayed in each row can be decided by checking the values of two different model key paths.
This i tried to implement using bindings,where i used "Display pattern Value1 with one key path and custom value transformer class" and "Display pattern Value2 with other key path and same value transformer".But i am not getting desired output value from the transformer class.Can anyone please help me in resolving this issue.
2.In the other application there is a table view with 3 columns,where the first column displays the complete word,second column displays the prefix of that word and the third column displays the suffix of that word.
I implemented this requirement using bindings and two custom value transformer classes.One for getting the prefix of the word(prefixExtractor) and the other for getting the suffix of the word(suffixExtractor).Can anyone suggest me how can i implement this requirement using only one custom value transformer class so that it optimizes my code.
Thanks in advance.

Oracle: error while trying to use formulas

I created an element with an input value of type "Day" , when i write a formula i get this error.
Any idea what's wrong?
APP-FF-33232:
EATC_EXTRA_DAYS_ENTRY_EFFECTIVE_DATE_ENTRY_VALUE has null or not found allowed, but no
default set specified.
Cause: If a Database Item has
null allowed, or not found allowed,
then the item must also specify a
default set to be used to provide
default values in the event of these
occurring. The item named has one of
these conditions allowed, but the
default set column in the
FF_DATABASE_ITEMS table is null.
Action: Please refer to your
local support representative.
-
I'm not an expert in Oracle Apps (to say the least) but the error message is fairly clear. You - or someone - have written a Fast Formula which references a database column EATC_EXTRA_DAYS_ENTRY_EFFECTIVE_DATE_ENTRY_VALUE. Apparently this column can be nullable, in which case your Formula needs to provide a default value. Something like:
default for EATC_EXTRA_DAYS_ENTRY_EFFECTIVE_DATE_ENTRY_VALUE is 01-JAN-2010
Or perhaps you can use SYSDATE or CURRENT_DATE rather than a fixed value.
Solution to error: You called database item in Fast formula,
you need to initialize the date to specific date
alias EATC_EXTRA_DAYS_ENTRY_EFFECTIVE_DATE_ENTRY_VALUE as day
default for day is 01-jan-2010

Resources