Skip to main content
Question

Documentation about the writer's behavior when Truncate Table is "Yes" but no feature is written?


Forum|alt.badge.img

Hi! I am using a writer to write to a non-version ESRI SDE feature class. For now I pass some parameter to the "Truncate Table" of the writer. When the parameter is "Yes", the writer deletes everything in the feature class before writing new records, as expected.

When I tried a situation that the parameter is "Yes" but there is no feature to be written, the feature class is not going to be truncated. This is the behavior I want. However, I couldn't find any documentation about this scenario.

Is there any documentation I can use to verify my implementation is ok? I am trying to avoid using undocumented feature as much as possible.

Thank you!

4 replies

david_r
Celebrity
  • October 6, 2017

You are correct, if no feature enters the writer then the table will not be truncated (or dropped, if you activate that).


Forum|alt.badge.img
  • Author
  • October 6, 2017
david_r wrote:

You are correct, if no feature enters the writer then the table will not be truncated (or dropped, if you activate that).

Yes, this is the result from my experiment, and I want to use the fact in the FME workspace I am development. This is why I am looking for some documentation (help file) that tells (or implies) this, such that I can make sure the workspace is not using some undocumented functionality that can cause big consequence once the functionality no long present.

 


fmelizard
Safer
Forum|alt.badge.img+18
  • Safer
  • October 6, 2017

Hi @sui_huang, check out the documentation for the Geodatabase Writer. If you scroll down to the GEODB_TRUNCATE_TABLE, you'll see there is a note saying that a feature must reach the Writer for this parameter to be valid.


Forum|alt.badge.img
  • Author
  • October 6, 2017
fmelizard wrote:

Hi @sui_huang, check out the documentation for the Geodatabase Writer. If you scroll down to the GEODB_TRUNCATE_TABLE, you'll see there is a note saying that a feature must reach the Writer for this parameter to be valid.

Nice, thank you @TiaAtSafe

 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings