AI & Agent Dev Bug Sandbox Back to Radar

Table Editor Save Falsely Drops And Recreates Primary Key On Rename Or Out-Of-Order Composite Key

updateTable compares PK column names in display order with primary_keys from the database (key order), causing a name change or an out-of-order composite PK to be treated as a PK change. Studio then drops and re-adds the PK in separate transactions, which fails when foreign keys reference it or silently reorders the PK.

highConfidence 82%React

Origin Analysis

updateTable compares PK membership by column names in display order against primary_keys in key order (#39414). This string-based comparison is order-sensitive and ignores stable column identity, so a rename or a composite PK like (b,a) appears different from (a,b) even when the set of columns is identical.

1. Create a table with a composite primary key (b, a) and a foreign key referencing that PK. 2. Open the Supabase Studio Table Editor and modify only a description or column comment without changing the PK. 3. Save the table. 4. Observe: save fails with 'cannot drop constraint ... other objects depend on it' if an FK references the PK, or the PK is silently rebuilt and the order changes 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

Ensure column IDs are present and stable for all tables; for imported or legacy schemas with missing IDs, a fallback to name comparison may still reproduce the original bug. The drop/recreate itself still runs in separate transactions, so keep the change minimal and consider a future single-statement ALTER TABLE. Roll back by reverting to the previous order-sensitive comparison or pinning the Studio version if this fix causes unintended behavior.