This is not entirely true. A lot of components throws an error if you configure the schema column as not nullable. Example: most input and output components doing that!
Thanks, i was building a custom component and using tPostgresqlOutputBulk as an example and notice that it excepts nulls even if the schema field is not nullable. It does convert the null to a string value... so a null integer would be "0". But for type String, it outputs a null which crashes on the bulkload component. Another note about this component - it is impossible to get an empty string value, both null strings and empty strings end up as null in the output. Must be a bug?
My main goal is to follow the existing standard if there is one.
