The current logic for storing and updating Durable State decides based on revision=1 to INSERT, otherwise to UPDATE.
This logic works for a production application but not for a migration where the state could come already with an updated revision which would cause an UPDATE query on the new table - which fails since there is no state to update.
The current logic for storing and updating Durable State decides based on revision=1 to
INSERT, otherwise toUPDATE.This logic works for a production application but not for a migration where the state could come already with an updated revision which would cause an
UPDATEquery on the new table - which fails since there is no state to update.