Is it correct that in a table output step, the truncate table checkmark is supposed to truncate the table even though no rows enter that step? That is how it works in 2.5.0, but i'm wondering if that is a bug.
The issues is that I'm using a filter to check whether I will use an insert step or an insert/update step. The filter checks an environment variable which indicates what direction to "send" the data.
However, the truncate part seems to initialize even though i'm not passing rows to that step.
If this is not a bug, doesn't it seem to hinder flexibility?

sboden

07-09-2007, 11:33 AM

In a transformation all steps starts at the same time and run concurrently, this is why the truncate happens. You can work around it by using by e.g. using different transformations.