Dialect Desk - the Oracle-to-PostgreSQL difference that compiles and returns another value

Paste one Oracle table and the SQL your code runs against it, and work the migration in one sitting: every Oracle-to-PostgreSQL difference sorted by whether it will refuse to compile or compile and quietly return a different value. Five lanes over one migration sheet - turn a table and its queries into a sheet, read every difference with the exact rows it changes and the one-line rewrite, enumerate every combination of every || chain (3^k of them, and 3^k - 2^k differ because Oracle has no empty string), count every declared value four ways to find the byte-counted column that becomes 4x wider, and triage what a target type fixes, what only a rewritten query fixes and what nothing fixes because the application has to decide. A free in-browser engine does the UTF-8, IEEE-754, three-valued-logic and collation arithmetic before anything is spent - VARCHAR2(40) is 40 BYTES and varchar(40) is 40 CHARACTERS, NUMBER(10) to integer makes 10/4 return 2, DATE to date drops the time, SYSDATE advances inside a transaction and now() does not, and Oracle's binary sort reorders page one. It reads a sheet, not a database. Derived from the reviewing-oracle-to-postgres-migration, creating-oracle-to-postgres-migration-bug-report and scaffolding-oracle-to-postgres-migration-test-project skills in github/awesome-copilot (github.com/github/awesome-copilot). Not affiliated with or endorsed by their authors.

Every public app is built from a security-scanned skill and must pass a clean scan — skill and frontend — before it can be listed. Have a skill of your own? Turn it into an app — or read the step-by-step walkthrough.