You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to reproduce the issue mentioned in the report using MySQL. Currently, I found that when performing operations on a table without a primary key, it immediately gets blocked and prompts: "Could not find any index in the table: xxx."
The relevant part of the code is as follows:
`
indexes, err := m.getIndexes(ctx, dbName, tableName, conn)
if err != nil {
return nil, errors.Wrapf(err, "Could not found any index in the table: %s", tableName)
}
`
Therefore, I believe this issue might not exist in seata-go, or you could provide additional information for me to attempt reproducing it again.
What happened:
apache/incubator-seata#5078
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
The text was updated successfully, but these errors were encountered: