marcopaggioro commented on PR #363:
URL:
https://github.com/apache/pekko-persistence-jdbc/pull/363#issuecomment-3526628620
I was fixing the tests when I realized that my code doesn't cover the case
of "update the durable state record whose revision is -1 compared to the one
I'm passing to the update" (WHERE clause in UPDATE
`#${durableStateTableCfg.columnNames.revision} = ${row.revision} - 1`).
This is something you can't do with the `REPLACE` query.
Doing a `SELECT` before the `REPLACE` query isn't safe, and doing it within
the `REPLACE` query isn't efficient.
I missed this point, so these changes aren't enough.
Honestly, I've found several workarounds to do this, but none that don't use
locking, secondary tables, or inefficient query usage.
I have to retire from this PR, thanks for your time!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
