Skip to main content
  • EN

Hey there,

What effect does the parameter 'Ignore Nulls' in SQLExecutor have?

Or in other words: What happens when the SQL statement doesn't give a result? In my workspace these features are not going through the Result-output. In fact, they get lost 😞.

I know I can do several workarounds, e.g. merge the output with the initiator via an unique attribute or modify my SQL statement (which will be something like 'select nvl(min(ATTR),'doe') from ...'), but I expected the parameter 'Ignore Nulls' might give me the non-resulting features with a NULL-value in the result.

 

-Maria (using FME 2021.0)

@gpt_geoinfo​ The Ignore Nulls: Yes|No applies to the attribute handling only, not the SQL. When Combine Attributes is either Keep Initiator | Keep Results Attributes then you can set Ignore Nulls: Yes | No. If there are attributes with the same name on both Initiator & Result feature, if one of the is NULL then the other attribute value will be used.

Reply


Community Stats

30,177
Posts
114,554
Replies
37,842
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.