Skip to content

Allow string IDs in background migrations

What does this MR do and why?

Describe in detail what your merge request does and why.

This MR adjusts the logic in queue_background_migration_jobs_by_range_at_intervals so that it accepts string columns as ID columns. This will be required for !81991 (merged) where we want to iterate though runner registration tokens in the projects table, and iterating through the numeric ID would make the query unbearably slow.

Screenshots or screen recordings

These are strongly recommended to assist reviewers and reduce the time to merge your change.

Context from Slack thread:

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Merge request reports