Skip to content

fix "accessor" name migrations - #5544

Open
Shubham8287 wants to merge 9 commits into
masterfrom
shub/fix-table-migration-index-migration-step
Open

fix "accessor" name migrations#5544
Shubham8287 wants to merge 9 commits into
masterfrom
shub/fix-table-migration-index-migration-step

Conversation

@Shubham8287

@Shubham8287 Shubham8287 commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

Description of Changes

Fixes: #5132.

It makes migration to notice "accessor" name changes and update "st_*_accessor" tables accordingly.

Not doing so results in runtime panic as module depends on accessor names to use exposed ABIs.

API and ABI breaking changes

NA

Expected complexity level and risk

2

Testing

Tests has been added.

These tests verify that changing a table or column accessor_name in a module
schema triggers ChangeTableAccessorName and ChangeColumnAccessorName steps.
They currently fail because the auto-migration logic is not yet implemented.
Add ChangeTableAccessorName and ChangeColumnAccessorName step variants and
their full execution pipeline: auto-migration planning, datastore mutations
(updating st_table_accessor / st_column_accessor system tables and in-memory
schema), rollback support, formatter rendering, and step execution handlers.
@Shubham8287
Shubham8287 marked this pull request as draft July 15, 2026 11:17
@Shubham8287
Shubham8287 marked this pull request as ready for review July 29, 2026 14:00
@Shubham8287 Shubham8287 changed the title fix table migration index migration step fix "accessor" name migrations Jul 29, 2026
@Shubham8287 Shubham8287 self-assigned this Jul 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Migration can leave generated index accessors pointing at missing index names

1 participant