@supabase/lite 0.2.1-next.2 → 0.3.1-next.1

package/README.md

@@ -174,7 +174,6 @@ supabase/
 ```toml
 [api]
 port = 54321
-max_rows = 1000
 
 [db]
 driver = "sqlite-postgres"    # or "sqlite" | "pglite" | "postgres"
@@ -204,7 +203,7 @@ enable_confirmations = false
 
 Write **Postgres DDL** in `supabase/schemas/*.sql`. When the DB driver is SQLite, DDL is translated on the fly (`SERIAL` → `INTEGER PRIMARY KEY AUTOINCREMENT`, `NOW()` → `datetime('now')`, `JSONB` → `TEXT` with a `json_valid()` check, and so on). Postgres-only features that don't translate (ranges, `LATERAL`, table inheritance) throw a descriptive error.
 
-RLS works across all backends: on SQLite, policies are extracted from DDL and enforced at the application layer by rewriting the query AST; on PGlite/Postgres, native RLS is used. `auth.uid()`, `auth.jwt()`, and roles (`anon`, `authenticated`) resolve from the JWT.
+RLS works across all backends: on SQLite, policies are extracted from DDL and enforced at the application layer by rewriting the query AST; on PGlite/Postgres, native RLS is used. `auth.uid()`, `auth.jwt()`, and roles (`anon`, `authenticated`, `service_role`) resolve from the JWT.
 
 Full translation reference: [STATUS.md#postgres-to-sqlite-translation](https://github.com/supabase-community/lite/blob/HEAD/STATUS.md#postgres-to-sqlite-translation) and [`app/POSTGRES-SQLITE-COMPAT.md`](https://github.com/supabase-community/lite/blob/HEAD/app/POSTGRES-SQLITE-COMPAT.md).
 

package/STATUS.md

@@ -34,9 +34,9 @@ Feature and API compatibility tracking for @supabase/lite. For usage docs, see [
 
 ## Postgres-to-SQLite Translation
 
-When using SQLite databases, SQL schemas written in Postgres dialect are translated on the fly. The translator extends the Postgres deparser. It passes through 1:1 compatible syntax unchanged, rewrites constructs that have SQLite equivalents (for example `SERIAL` → `INTEGER PRIMARY KEY AUTOINCREMENT`, `NOW()` → `datetime('now')`), silently drops Postgres-only decorators (storage parameters, locking clauses), and errors on features that have no SQLite counterpart (`LATERAL` joins, table inheritance).
+When using SQLite databases, SQL schemas written in Postgres dialect are translated on the fly. The translator extends the Postgres deparser. It passes through 1:1 compatible syntax unchanged, rewrites constructs that have SQLite equivalents (for example `SERIAL` → `INTEGER PRIMARY KEY AUTOINCREMENT`, `NOW()` → `datetime('now')`), silently drops Postgres-only decorators and relation/schema privilege metadata (storage parameters, locking clauses, table/schema/sequence grants), and errors on features that have no SQLite counterpart (`LATERAL` joins, table inheritance, function grants).
 
-📋 See [`app/POSTGRES-SQLITE-COMPAT.md`](https://github.com/supabase-community/lite/blob/HEAD/app/POSTGRES-SQLITE-COMPAT.md) for the full auto-generated compatibility reference (82 entries).
+📋 See [`app/POSTGRES-SQLITE-COMPAT.md`](https://github.com/supabase-community/lite/blob/HEAD/app/POSTGRES-SQLITE-COMPAT.md) for the full auto-generated compatibility reference (71 entries).
 
 Here is an example of a Postgres schema that is translated to SQLite:
 
@@ -190,7 +190,7 @@ RLS is supported on all database backends. The enforcement strategy differs by d
 
 📖 See [`internal/docs/postgres/rls.md`](https://github.com/supabase-community/lite/blob/HEAD/internal/docs/postgres/rls.md) for the full RLS reference and behavior matrix.
 
-**PGlite / PostgreSQL auto-setup:** When any table has `ENABLE ROW LEVEL SECURITY`, supalite creates `anon` and `authenticated` roles (if missing) and grants default privileges on all tables and sequences in the relevant schemas. No manual `CREATE ROLE` or `GRANT` statements needed.
+**PGlite / PostgreSQL auto-setup:** When any table has `ENABLE ROW LEVEL SECURITY`, supalite creates `anon`, `authenticated`, and `service_role` roles (if missing; `service_role` uses `BYPASSRLS`) and grants default privileges on all tables and sequences in the relevant schemas. No manual `CREATE ROLE` or `GRANT` statements needed for these built-in roles.
 
 ### PL/pgSQL Trigger Functions
 
@@ -394,31 +394,18 @@ All operators are parsed into the AST. The "Status" column reflects whether a wo
 
 ### PostgREST spec: SQLite skip breakdown
 
-The 263 cases skipped on SQLite (out of 1,702) cluster into a small set of upstream Postgres features that have no SQLite analogue. Generated by `cd app && bun run test:spec:analyze:sqlite` (writes `.context/sqlite-analysis.json`).
+The 25 cases skipped on SQLite (out of 1,702) cluster into a small set of upstream Postgres features that have no SQLite analogue, would require generic product work, or remain tracked REST-spec deltas. Generated from the **actual skipped cases by code** section in `cd app && bun run test:spec:status`.
 
 | Category | Skipped | Why                                                                                  |
 |----------|--------:|--------------------------------------------------------------------------------------|
-| `feature_haskell_divergence_strict` | 46 | Strict Haskell PostgREST behaviour (header parsing, prefer modes) lite intentionally diverges from |
-| `domain_type`                       | 37 | Postgres `CREATE DOMAIN` types; no SQLite equivalent                                |
-| `pg_only_operators`                 | 36 | Postgres-specific operator syntax (`~`, `~*`, dictionary FTS, etc.)                  |
-| `tx_preferences`                    | 36 | `Prefer: tx=commit/rollback` and pre-request GUCs; no SQLite txn boundary           |
-| `cache_fk_names`                    | 23 | FK disambiguation paths exercising specific PG catalog metadata                      |
-| `pg_dictionary_fts`                 | 16 | Language-tagged full-text search dictionaries                                        |
-| `feature_error_codes`               | 11 | PostgREST/PG-specific SQLSTATE shapes                                                |
-| `cache_pg_types`                    | 10 | JSON operator behaviour tied to PG type cache                                        |
-| `pg_extension_specific`             | 10 | CORS / custom media types relying on PG extensions                                   |
-| `view_embedding`                    | 10 | View-FK resolution in PG-only metadata                                               |
-| `state_dependent`                   |  8 | Cases dependent on connection-pool/session state                                     |
-| `pg_role_set`                       |  4 | `SET LOCAL role` / JWT-driven role switching                                         |
 | `lite_anon_bearer_fallback`         |  4 | Lite-specific JWT fallback handling                                                  |
-| `computed_column`                   |  3 | PG `STORED`/`VIRTUAL` generated columns                                              |
-| `mutating_views`                    |  1 | Updatable view rules                                                                 |
-| `postgis`                           |  1 | PostGIS spatial types                                                                |
-| `xml_io`                            |  1 | XML output                                                                           |
-| `mutation_embed_two_query_limit`    |  2 | Embedded mutation w/ two-query plan                                                  |
-| `computed_relations`                |  1 | PG computed relationship overrides                                                   |
+| `computed_column`                   |  4 | PostgREST computed columns require PG function metadata                              |
+| `custom_media_handlers`             | 10 | Fixture raw-media handlers require generic custom media metadata/config             |
+| `pg_role_set`                       |  2 | `SET LOCAL role` / JWT-driven role switching                                         |
+| `private_schema_visibility`         |  2 | Private-schema junction visibility must not be emulated via `private_*` names       |
 | `collation_locale`                  |  1 | Locale-sensitive ordering                                                            |
-| `jsonb_dedup`                       |  2 | PG `jsonb` duplicate-key dedup semantics                                             |
+| `computed_relations`                |  1 | PG computed relationship overrides                                                   |
+| `mutation_embed_two_query_limit`    |  1 | Embedded mutation w/ two-query plan                                                  |
 
 Run `bun run test:spec:analyze` (or `:sqlite-postgres`, `:pglite`, `:postgres`) to regenerate per backend.
 
@@ -644,7 +631,7 @@ Help groups match upstream: **Local Development** (commands you run from a proje
 
 | Command   | Status | Notes                                                              |
 |-----------|--------|--------------------------------------------------------------------|
-| `init`    | ✅      | Parity at verb level; flags differ from upstream                   |
+| `init`    | ✅      | Scaffolds API, migration/seed paths, and auth defaults; flags differ upstream |
 | `start`   | ✅      | In-process; no Docker stack flags (`-x`, `--ignore-health-check`)  |
 | `status`  | 🧪      | `[experimental]` `[lite]`: shows linked project metadata          |
 | `login`   | 🧪      | `[experimental]` Email/password against supalite cloud             |
@@ -667,11 +654,12 @@ Help groups match upstream: **Local Development** (commands you run from a proje
 
 | Command       | Status | Notes                                                                |
 |---------------|--------|----------------------------------------------------------------------|
-| `db diff`     | ✅      | Re-export of `db schema --diff` handler; `--local` semantics only    |
+| `db diff`     | ✅      | `--local` semantics; `-f` emits pg-DDL migrations from declarative schemas |
 | `db query`    | ✅      | Renamed from top-level `exec`; supports `--remote` and `--config`    |
 | `db schema`   | ✅      | `[lite]`: moved from top-level; `--diff` and `--sql` modes          |
 | `db push`     | 🔄     | Not registered; use `lite cloud deploy`                             |
-| `db pull`, `db reset`, `db dump`, `db lint`, `db advisors` | 🔄 | Not registered                       |
+| `db reset`    | ✅      | Replays migrations + seed; does not apply declarative schema_paths   |
+| `db pull`, `db dump`, `db lint`, `db advisors` | 🔄 | Not registered                       |
 | `db start`    | 🚫     | Not applicable; in-process, no separate DB start                    |
 
 ### `migration` group
@@ -776,10 +764,10 @@ PostgREST spec status (`cd app && bun run test:spec:status`):
 
 | Backend | Total | Passing | Pass % | Skipped | Skip % | Failed |
 |---------|------:|--------:|-------:|--------:|-------:|-------:|
-| Postgres | 2,460 | **1,752** | 71.2% | 708 | 28.8% | 0 |
-| PGlite | 2,460 | **1,746** | 71.0% | 714 | 29.0% | 0 |
-| SQLite | 1,702 | **1,439** | 84.5% | 263 | 15.5% | 0 |
-| SQLite-Postgres | 1,702 | **1,479** | 86.9% | 223 | 13.1% | 0 |
+| Postgres | 2,460 | **1,923** | 78.2% | 537 | 21.8% | 0 |
+| PGlite | 2,460 | **1,933** | 78.6% | 527 | 21.4% | 0 |
+| SQLite | 1,702 | **1,677** | 98.5% | 25 | 1.5% | 0 |
+| SQLite-Postgres | 1,702 | **1,677** | 98.5% | 25 | 1.5% | 0 |
 
 Auth supabase-spec status (`cd app && bun run test:spec:auth`):
 

package/dist/{Connection-CSVCuMv-.d.ts → Connection-DF_xKWko.d.ts}

@@ -246,7 +246,9 @@ type TranslatorConfig = {
     parseBody?: (req: Request) => Promise<BodyResult>;
     parseQueryParams?: (req: Request) => QueryParamsResult;
     resolveType?: (route: RouteResult, method: string, headers: HeadersResult) => ASTType;
-    resolveFilters?: (queryParams: QueryParamsResult, embeddedAliases: Set<string>) => FiltersResult;
+    resolveFilters?: (queryParams: QueryParamsResult, embeddedAliases: Set<string>, fromTable?: string, parentColumns?: ReadonlySet<string>) => FiltersResult;
+    /** Physical columns on the request table (for embed/column homonym filters). */
+    parentColumns?: ReadonlySet<string>;
     resolveTransforms?: (queryParams: QueryParamsResult, embeddedAliases: Set<string>) => TransformsResult;
     resolveMeta?: (headers: HeadersResult, queryParams: QueryParamsResult, method: string) => Meta;
     resolveRpcParams?: (route: RouteResult, method: string, queryParams: QueryParamsResult, body: BodyResult) => RpcResult;
@@ -299,6 +301,8 @@ interface ForeignKeyInfo {
     schema: string;
     ref_schema?: string;
     foreign_key_name: string;
+    /** Internal grouping key for derived FK paths that share a display constraint name. */
+    foreign_key_group?: string;
     fk_def: string;
     is_visible?: boolean;
 }