Skip to content

feat(sql-editor): key-align Compare for friendlier side-by-side diffs - #189

Merged
huyplb merged 3 commits into
mainfrom
cursor/query-data-compare-7e48
Aug 7, 2026
Merged

feat(sql-editor): key-align Compare for friendlier side-by-side diffs#189
huyplb merged 3 commits into
mainfrom
cursor/query-data-compare-7e48

Conversation

@huyplb

@huyplb huyplb commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Summary

Follow-up after #188 (already on main). This PR is rebased clean onto main — 3 commits only:

  • Key-aligned Compare — matching Keys share a row (same as Data migrate); only-here rows pad as missing/extra
  • Original Server naming — Schema Sync left side and Compare source/baseline labels → Original Server / original

Compare remains off by default; Add / Edit / Delete stay user-opt-in.

Test plan

Open in Web Open in Cursor 

Comment thread apps/web/src/frontend/lib/dataMigratePlans.ts Fixed
cursoragent and others added 3 commits August 7, 2026 05:59
Compare was index-aligned so mismatched ORDER BY made every row look wrong
even when keys matched. Align source/dest rows by the same Keys as Data
migrate, pad only-here rows, and tint real edits/adds/deletes.

Co-authored-by: huy.phan9 <huyplb@users.noreply.github.com>
Schema Sync and Compare data now say Original Server instead of Source/
baseline so the read-from side is clearer next to Target/Destination.

Co-authored-by: huy.phan9 <huyplb@users.noreply.github.com>
Align Object Detail column labels with Schema Sync naming.

Co-authored-by: huy.phan9 <huyplb@users.noreply.github.com>
@cursor
cursor Bot force-pushed the cursor/query-data-compare-7e48 branch from 506f0d8 to 2cb0ad9 Compare August 7, 2026 05:59
@huyplb
huyplb marked this pull request as ready for review August 7, 2026 17:08
@huyplb
huyplb merged commit 8e3e81f into main Aug 7, 2026
6 of 7 checks passed
@huyplb
huyplb deleted the cursor/query-data-compare-7e48 branch August 7, 2026 17:08
@cursor

cursor Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_b663c7b7-9501-42b3-bde9-f00155c92789)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants