concurrent update error
is the problem reproducible? That is, can you create a scripted scenario in which a view is updated, there are no updates to the underlying entities, yet you receive a concurrent update exception?
This issue persists. It changed where it failed (e.g., which query and view update). I was only able to overcome this by 'forcing' a table reindex ('select id from syn123 limit 1') before trying another query.
It is extremely unlikely that anyone is modifying this, as I'm the sole individual working on this project. Trying to figure out how I could be that 'other' person modifying it with the code I'm running.
I gather that what's missing is some sort of retry, to reapply the change when another party is not modifying the same entity.