[ditadi]

🥞 Stacked PR (generated by Stack)

Use this link to review incremental changes.

• stack/database-dev-flow/00-design [Files changed]
• stack/database-dev-flow/01-migrations-on-deploy [Files changed]
  • stack/database-dev-flow/02-default-app-schema [Files changed] ← this PR
    • stack/database-dev-flow/03-db-migrate [Files changed]
      • stack/database-dev-flow/04-db-introspect [Files changed]
        • stack/database-dev-flow/05-db-init [Files changed]
          • stack/database-dev-flow/06-db-verify [Files changed]
            • stack/database-dev-flow/07-apps-init [Files changed]
              • stack/database-dev-flow/08-db-check [Files changed]

---

Stacked on #654. The design is #677.

What did you change, and why?

On Lakebase, the deployed app's service principal has no CREATE on public, but it can create and own a schema of its own. #654 applies migrations on start as that service principal, so with public as the default the first deploy would fail until someone ran a grant by hand.

• defineSchema() without a schemaName puts its tables in the Postgres schema app. The service principal creates app on its first start and owns everything in it, including the migration journal. DEFAULT_SCHEMA_NAME in define-schema.ts is the only place the default is set.
• An explicit { schemaName: "public" } still produces unqualified SQL (pgTable and pgEnum).
• Beta apps whose tables are in public now look in app and fail setup. When every missing table exists in public, the error says so and shows { schemaName: "public" }. It leaves out the usual advice to commit migrations, which would create a second, empty copy in app.
• A 42501 while migrating into public gets its own hint. It says to grant CREATE ON SCHEMA public to the service principal, or to use the default app.
• The plugin docs explain the default, say each app needs its own schema, and cover upgrading an app with tables in public.
• The dev-playground passes { schemaName: "public" }, because its tables were created by hand in public.

Apps that name their schema are unchanged, and apps on the old default get an error that says what to change. This revision only merges the corrected #654 and current main. The diff of this PR is unchanged.

How do you know it works?

• define-schema.test.ts checks that tables and enums go to app by default and stay unqualified with an explicit public.
• schema-check.test.ts checks that the error names public when every missing table is there, and keeps the usual advice when only some are there or the declared schema is public.
• ownership.test.ts checks the public hint. migrate-on-start.test.ts uses the default, so it checks that the journal goes to app.
• At this PR's head, the history tests passed, and a repeated start against a local PostgreSQL 14 applied nothing the second time. The full vitest suite, a clean build, the docs build and typecheck passed at the top of the stack (feat(appkit): add appkit db check #678), which contains this PR, and its packed tarballs export the same root and ./beta names as main. CI runs the full suite on this PR.
• This revision was not run against a real Lakebase workspace.

[github-actions]

📦 Bundle size report

Compared against bundle-size-baseline.json (main).

@databricks/appkit

npm tarball (packed): 1.3 MB (+26 KB) — gzipped download (dist + bin; excludes release-only docs/NOTICE).

dist	raw	gzip
JS (runtime)	1.3 MB (+30 KB)	469 KB (+11 KB)
Type declarations	464 KB (+59 B)	168 KB (+28 B)
Source maps	2.6 MB (+54 KB)	874 KB (+18 KB)
Other	11 KB	3.7 KB
Total	4.3 MB (+84 KB)	1.5 MB (+29 KB)

Per-entry composition (own code — deps external (as shipped))

Entry	Initial (gz)	Lazy (gz)	Total (gz)	node_modules (min)	Own code (min)
.	106 KB (-1 B)	2.5 KB (+1 B)	108 KB	external	343 KB
./beta	108 KB (+5.1 KB)	485 B	108 KB (+5.1 KB)	external	323 KB (+14 KB)
./testing	45 KB (+1 B)	32 KB (-3 B)	77 KB (-2 B)	external	223 KB
./tsdown	520 B	0 B	520 B	external	813 B
./type-generator	26 KB	0 B	26 KB	external	74 KB

Chunks:

Entry	Chunk	Load	Size (gz)
.	index.js	initial	101 KB
.	utils.js	initial	4.6 KB
.	remote-tunnel-manager.js	lazy	2.5 KB
./beta	beta.js	initial	88 KB
./beta	modular.js	initial	6.0 KB
./beta	stream-manager.js	initial	5.9 KB
./beta	service-context.js	initial	4.2 KB
./beta	databricks.js	initial	3.3 KB
./beta	client.js	initial	647 B
./beta	index.js	initial	20 B
./beta	supervisor-api.js	lazy	192 B
./beta	databricks.js	lazy	178 B
./beta	index.js	lazy	115 B
./testing	manifest.js	initial	32 KB
./testing	index.js	initial	10 KB
./testing	wide-event-emitter.js	initial	2.9 KB
./testing	index.js	lazy	28 KB
./testing	remote-tunnel-manager.js	lazy	2.5 KB
./testing	utils.js	lazy	1.8 KB
./tsdown	index.js	initial	520 B
./type-generator	index.js	initial	26 KB

@databricks/appkit-ui

npm tarball (packed): 397 KB (+4 B) — gzipped download (dist + bin; excludes release-only docs/NOTICE).

dist	raw	gzip
JS (runtime)	429 KB	147 KB
Type declarations	267 KB	98 KB (+1 B)
Source maps	853 KB	286 KB
CSS	16 KB	3.2 KB
Total	1.5 MB	534 KB (+1 B)

Per-entry composition (consumer bundle — deps bundled, peerDeps external)

Entry	Initial (gz)	Lazy (gz)	Total (gz)	node_modules (min)	Own code (min)
./js	5.3 KB	49 KB	55 KB	208 KB	14 KB
./js/beta	2.1 KB	0 B	2.1 KB	0 B	5.0 KB
./react	433 KB	49 KB	481 KB	1.3 MB	177 KB
./react/beta	4.9 KB	0 B	4.9 KB	0 B	12 KB

Chunks:

Entry	Chunk	Load	Size (gz)
./js	index.js	initial	5.2 KB
./js	chunk	initial	120 B
./js	apache-arrow	lazy	49 KB
./js/beta	beta.js	initial	2.1 KB
./react	index.js	initial	431 KB
./react	tslib	initial	2.1 KB
./react	apache-arrow	lazy	49 KB
./react/beta	beta.js	initial	4.9 KB

[github-actions]

🤖 AppKit PR bot

🔬 Run evals

Start an eval for this PR from the evals-monitor app: Go to Evals Monitor →

📦 Try this PR's app template

Scaffolds a new app from this PR's SDK build. Run it in any folder (requires the GitHub CLI — gh auth login — and the Databricks CLI):

gh run download 41109404652 -R databricks/appkit -n appkit-template-0.89.0-pr.6cf499b-stack-database-dev-flow-02-default-app-schema-655 -D appkit-pr-655 \
  && unzip -o "appkit-pr-655/appkit-template-0.89.0-pr.6cf499b-stack-database-dev-flow-02-default-app-schema-655.zip" -d "appkit-pr-655" \
  && databricks apps init --template "appkit-pr-655"

The template pins @databricks/appkit and @databricks/appkit-ui to tarballs built from this branch, so the scaffolded app runs against this PR's code.