Open alexbruy opened 2 years ago
Normally this should not happen, only with invalid diffs (where update
entry has no actual changes recorded), so when this happens, the actual underlying issue is somewhere else...
@alexbruy do we have some data to replicate the issue?
If there are no changes in the PostgreSQL table, geodiff generates wrong query to fetch updated columns:
As a result it fails to create changeset with the error