[Bug]: SQL parser error: table \"__mo_index_unique_0192748f-6868-7182-a6de-2e457c2975c6\" does not exist error is returned when running SQL

[DanielZhangQD]

Is there an existing issue for the same bug?

• I have checked the existing issues.

Branch Name

main

Commit ID

v2.0.0-e08947032-2024-10-09

Other Environment Information

- Hardware parameters:
- OS type:
- Others:

Actual Behavior

The SQL is executed in account 01927400-16b3-7d3a-b47b-7e405633af0f but returns the following error:

"error":"Error 1064 (HY000): SQL parser error: table \"__mo_index_unique_0192748c-a33a-756d-a04a-92998a6be15d\" does not exist","elapsed":"30.138120565s","rows":0,"sql":"ALTER TABLE `billing_records` MODIFY COLUMN `account_period` varchar(32)"

The application log: https://grafana.cn-dev.matrixone.tech/goto/J7QXHCkNg?orgId=1
The MO log: https://grafana.cn-dev.matrixone.tech/goto/oURjNCkHR?orgId=1

Expected Behavior

SQL succeeds

Steps to Reproduce

See detail in Actual Behavior

Additional information

Cloud dev env

[qingxinhome]

got it

[DanielZhangQD]

The same error is reported continuously in cloud env https://grafana.cn-dev.matrixone.tech/goto/xsuCkxiHg?orgId=1

[qingxinhome]

本地使用gorm程序验证没有复现，持续关注

[qingxinhome]

未复现，本地测试gorm程序能够成功

[qingxinhome]

等待韩枫侧对Relation()接口进行优化

[qingxinhome]

等待韩枫侧对Relation()接口进行优化

[daviszhen]

等hf优化后，再调整代码。2.0.1来不及

[aptend]

处理其它bug中

[qingxinhome]

#20194

[aptend]

pr #20145

[qingxinhome]

The issue has been resolved, please verify and test