That's just a placeholder issue to reference some examples of real SQL in the wild. So I can better prioritize which parts of syntax to support. ### PostgreSQL - https://github.com/giveffektivt/donation-platform/blob/main/db/migrations/99999999999999_views.sql features the following missing bits: - [x] `DROP FUNCTION` with multiple function names. - [ ] `CREATE RULE` statement - [x] interval literal with unit, e.g. `interval '1' month` - [x] `year` and `month` used as identifier - [x] `FULL [OUTER] JOIN` - Supabase SQL export. Contains the following unsupported bits: - [x] `SET row_security = off`, `SET standard_conforming_strings = on`, etc - [x] `RESET ALL` - [x] `CREATE EXTENSION IF NOT EXISTS "pg_net" WITH SCHEMA "extensions"` - [x] `COMMENT ON SCHEMA "public" IS 'standard public schema'` - [x] Namespaced data type name in table column definitions and elsewhere (like "public"."my_enum"). - [x] `ALTER PUBLICATION "supabase_realtime" OWNER TO "postgres"` - [x] `ALTER DEFAULT PRIVILEGES FOR ROLE "postgres" IN SCHEMA "public" GRANT ALL ON SEQUENCES TO "postgres"`
That's just a placeholder issue to reference some examples of real SQL in the wild. So I can better prioritize which parts of syntax to support.
PostgreSQL
DROP FUNCTIONwith multiple function names.CREATE RULEstatementinterval '1' monthyearandmonthused as identifierFULL [OUTER] JOINSET row_security = off,SET standard_conforming_strings = on, etcRESET ALLCREATE EXTENSION IF NOT EXISTS "pg_net" WITH SCHEMA "extensions"COMMENT ON SCHEMA "public" IS 'standard public schema'ALTER PUBLICATION "supabase_realtime" OWNER TO "postgres"ALTER DEFAULT PRIVILEGES FOR ROLE "postgres" IN SCHEMA "public" GRANT ALL ON SEQUENCES TO "postgres"