Database writer feature operation should take precedence over fme_db_operation

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.

I don’t think the help is very clear for this.

It should be explicit that if fme_db_operation exists on a feature and Feature Operation is set to Insert then an error will be raised if the value of the fme_db_operation conflicts with the Feature Operation set in the writer.

I would agree with ​@nic_ran that expected behaviour would be to use the setting in the writer and ignore any attribute value but that’s not the case