The following GDAL/OGR writers provide support for fme_db_operation writing. Unfortunately, it is only possible to match (UPDATE | DELETE) records against a [system id] field, which is internally generated. This issue affects the following formats:
spatialite
carto
cloudant
couchdb
elasticsearch
geopackage
mongodb
others?
In most of my scenarios, I am wanting to take incremental updates as "changeset" data from a data custodian and synchronise it as (UPDATEs | INSERTs| DELETEs) against the existing data in my tables. The new changeset data has no knowledge (in advance) of what the internal [system id] values are, so the UPDATEs and DELETEs can never be matched and processed.
The fme_db_operation format attribute does not behave like this on non-GDAL/OGR FME writers, i.e. this would be like only being able to do a fme_db_operation match on an Esri geodatabase [OBJECT_ID] field (which is also internally generated).
Can we have the Match-ID reference any "unique id" field when working with fme_db_operation writes to these formats please?