If you call LocationService->updateLocation, and the details of your locationUpdateStruct match those already in the database, the LocationService will throw a NotFound exception, when in fact the record was found and no changes were made.

The issue stems from the way that the Legacy storage engine confirms the update:

https://github.com/ezsystems/ezpublish-kernel/blob/master/eZ/Publish/Core/Persistence/Legacy/Content/Location/Gateway/DoctrineDatabase.php#L1136

By performing a row count of affected rows, and assuming that a 0 means the object was missing, a misleading exception is generated. To allow for idempotent operation, updating a record with its existing values shouldn't generate an exception.

A possible correction would be to check the struct against the location in the location service, before the storage engine.