Skip to content

fix: use PGlite by default for db generation - #65

Open
iliasaberkane6-lab wants to merge 1 commit into
seveibar:mainfrom
iliasaberkane6-lab:fix/pglite-default-generate
Open

fix: use PGlite by default for db generation#65
iliasaberkane6-lab wants to merge 1 commit into
seveibar:mainfrom
iliasaberkane6-lab:fix/pglite-default-generate

Conversation

@iliasaberkane6-lab

@iliasaberkane6-lab iliasaberkane6-lab commented Sep 10, 2026

Copy link
Copy Markdown

Summary

  • make the existing PGlite generation path the default, so db:generate does not require a running PostgreSQL server
  • keep external PostgreSQL generation available via --no-pglite
  • turn the PGlite generation test into a regression test that omits the flag
  • document the new default and escape hatch

Verification

  • bun test (3 pass, 0 fail)
  • bun run format:check
  • bun run build
  • git diff --check

@algora-pbc /claim #2

Closes #2

Copy link
Copy Markdown
Author

@algora-pbc /claim #2

Copy link
Copy Markdown
Author

Quick status note: all local verification passed (bun test, bun run format:check, bun run build, git diff --check). The three GitHub Actions runs currently show action_required with no jobs created, which appears to require maintainer approval before CI can execute for this first-time contribution. When convenient, could you approve the workflow runs and review the PR? Thanks!

@iliasaberkane6-lab
iliasaberkane6-lab force-pushed the fix/pglite-default-generate branch from 1c6e702 to fe429ad Compare September 11, 2026 10:06
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.

Use pglite so that postgres isn't required when generating types

1 participant