AI & Agent Dev Bug Sandbox Back to Radar

Table Editor Drops And Re-Adds Primary Key Due To Order-Sensitive Column Name Comparison

updateTable compares primary key column names in display order with the backend's primary_keys array (which comes back in key order). A rename or an out-of-order composite primary key like (b, a) is falsely detected as a PK change, causing Studio to drop and re-add the constraint in separate transactions. This fails when a foreign key references the primary key, blocking unrelated edits, or silently rebuilds the constraint and reorders columns when no FK exists.

highConfidence 85%Supabase-Studio

Origin Analysis

The PK change detection compares arrays of column names in display order against primary_keys in key order instead of comparing PK membership by column id, leading to false positives for renames and composite key ordering differences.

1. Create a table with a composite primary key (b, a) or a single primary key 'id'. 2. Create another table with a foreign key referencing that primary key. 3. Open the Table Editor and make an unrelated change (e.g., edit description) or rename a non-PK column. 4. Save; Studio erroneously drops the primary key constraint because it thinks the PK changed. 5. The save fails with 'cannot drop constraint ... other objects depend on it' if a FK exists, or silently rebuilds the PK and changes column order to (a, b) if no FK exists.

Fixing Code Block

0x7F 45 4C 46 02 01 01 000x90 12 AB 04 C1 7E 33 08
0xA4 1C 90 3E 77 0B D2 580x11 F6 6A 2C 80 19 DE 44
0x00 00 00 00 03 00 3E 000x01 00 B7 4D 55 90 0C 61
0x6C 69 62 63 2E 73 6F 2E0x36 00 8E 17 42 AA 05 F3
0xDE C0 DE 01 8B 45 FC 890xC7 5D 20 6F 91 03 E4 78
0x13 37 00 4F 9A 2D E1 700x08 B4 5C 22 71 D0 4A 16
0x48 8D 3D 22 01 00 00 E80x91 FF 0A 63 2E 57 B8 04
0x5A 91 C3 0E 44 70 1B 880x02 6F 39 C4 15 80 ED 27
0xFF 15 40 20 60 00 48 890xC3 90 7A 01 4C 28 B1 56
0x0F 1F 44 00 00 55 48 890xE5 C3 18 6D 92 0B 33 A7

Edge Case Audit

This fix relies on each primary key column having a stable `id` across renames; if the backend regenerates ids on rename, the comparison could still trigger false positives. Additionally, concurrent schema edits could produce stale `primary_keys` arrays, causing missed or duplicate drops. Rolling back this hotfix after upgrading would reintroduce the order-sensitivity bug for composite keys. Recommended: test with multi-column PKs and FK dependencies, and consider adding optimistic locking or schema version checks for concurrent edits.