github-actions[bot] commented on issue #1131: URL: https://github.com/apache/incubator-seata-go/issues/1131#issuecomment-4881845691
> Bot detected the issue body's language is not English, translate it automatically. # # # ✅ Validation Checklist - [x] 🔍 I've searched [existing issues] (https://github.com/apache/incubator-seata-go/issues) and I'm sure it's not a duplicate request - [x] 📋 I have reviewed the [release notes] (https://github.com/apache/incubator-seata-go/releases) and am confident that this feature has not been implemented - [] 🛠️ I am willing to take care of this on my own # # # 🎯 Function description Many production tables use a composite (multi-column) primary key instead of a single primary key column (e.g. `(tenant_id, id)`, `(order_id, user_id)`).AT mode has already laid some groundwork for composite primary keys (for example, support for building lock keys across multiple primary key columns), but support is not complete and inconsistent between different SQL actuators (insert, update, delete, insert... ON duplicate key: [redacted]... for update), especially in primary key metadata processing and automatic primary key generation scenarios.This Issue wants to do a systematic review and refinement of all relevant actuators in AT mode to ensure that tables using composite primary keys are fully and consistently supported: - anterior/posterior image construction; - Lock key: [redacted] - Rollback log build and rollback correctness. # # # 📋 Usage scenarios - multitenant systems using compound primary keys such as` (tenant_id, id) `; - Scenarios such as Association Tables/Intermediate Tables that use composite primary keys instead of single row proxy primary key designs. # # # ⚖️ Complexity and risk assessment The primary key metadata processing logic shared by most AT mode actuators is involved. Changes need to cover more comprehensive tests (insert/update/delete/select-for-update, and interaction with self-added, multi-line insertion scenarios in Issue 3) to avoid affecting the behavior of existing single primary key scenarios. # # # 🔗 External dependencies _No response_ # # # 📚 Additional information _No response_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
