fix: migration#30720
Conversation
|
Thanks for your contribution! This PR doesn't have a linked issue. All PRs must reference an existing issue. Please:
See CONTRIBUTING.md for details. |
|
This PR doesn't fully meet our contributing guidelines and PR template. What needs to be fixed:
Please edit this PR description to address the above within 2 hours, or it will be automatically closed. If you believe this was flagged incorrectly, please let a maintainer know. |
|
The following comment was made by an LLM, it may be inaccurate: Found a potentially related PR: PR #30705: Why it might be related: This PR also addresses session migration issues with |
|
This pull request has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window. Feel free to open a new pull request that follows our guidelines. |
Issue for this PR
Closes #
Type of change
What does this PR do?
Fixes migration regression introduced in #30632
Previously,
20260603040000_session_message_projection_orderassumed every existing session_message projection had a matching durable event row. Getting errorCannot migrate session_message projections without matching durable eventsNow the migration does this:
session_message.seq.event.seqwhen the matching event exists.time_created,id.seqvalues back to zero-based order.event_sequence.seqto at least the max projected message seq, so future durable events do not reuse a sequence number.If you paste a large clearly AI generated description here your PR may be IGNORED or CLOSED!
How did you verify your code works?
Screenshots / recordings
If this is a UI change, please include a screenshot or recording.
Checklist
If you do not follow this template your PR will be automatically rejected.