Skip to main content
  • EN
  • Home
  • Ideas
  • Database writer feature operation should take precedence over fme_db_operation

On database writers, if the "feature operation" parameter is explicitly set to insert/update/delete then it should force that operation and ignore any value in the feature's fme_db_operation attribute.

Currently [FME 2021.1], if the (Oracle) writer feature operation is set to "insert" but a feature enters the writer with fme_db_operation set to "UPDATE", the writer issues a warning and the feature does not get inserted.

The log message issued by FME is:

|WARN |Oracle Non-Spatial: The fme_db_operation attribute value 'UPDATE' on feature conflicts with Feature Operation 'Insert'. Rejecting feature

Hey Nic.

I think that's working as designed. The help doc says:

 

"To use fme_db_operation, you must set Feature Operation to this option. In previous versions of FME, you could set fme_db_operation when the destination feature type was set to Insert, Update, Upsert, or Delete. Doing this now will cause feature rejection."

 

I don't know if we'd force it to use the feature type parameter in preference. I think that partly because they could have made it work like then with the above change - but didn't - and partly because the old way used to give the attribute priority and it would be too confusing to reverse that completely.

 

But we can leave this idea open and see if it gets any traction. Who knows, it might be a big deal for a lot of users.

 

Open→Archived

Community Stats

30,149
Posts
114,444
Replies
37,794
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.