Repository navigation
Conversation
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 8 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A team that moves from Prisma or Drizzle has no map to effect-orm. It cannot see quickly which operations exist today and which are still open.
Closes #91.
Part of #52.
Changes
docs/coming-from-drizzle-prisma.md. A table maps the common Prisma and Drizzle operations to effect-orm: findUnique / findFirst / findMany, include,_count, some / none / every, create / createMany / upsert, update / updateMany, delete, transactions, raw SQL,FOR UPDATE, unique violations, cursor pagination, case-insensitive search, JSON fields, defaults,@updatedAt,@map, seeding, migrations, pull and drift.mainhas the operation, the table names it. Where only an open PR has it, the cell says "planned: #N" and gives today's workaround. The guide has no example for a planned API.coming-from-prisma.ts, runs most of the table on PGlite withrequireTenantScopeon.check-doc-examples.mjsnow asserts its full result.cafe-worker.tsis a fetch handler that builds aDatabasefor each request.cafe-worker-local.tsruns it on PGlite with no network, and the doc check asserts its responses (rows for one org, 401 with no org). The Hyperdrive wiring with@effect/sql-pgis shown as an unchecked block.docs/README.mdandREADME.md. Onepatchchangeset.Left out
alchemy.run.tsand Foldkit UI. D1 and DO wait for the SQLite / D1 dialect (feat: add SQLite and Cloudflare D1 query dialects #49). The Alchemy stack and UI come with that example, so one stack shows the whole CAFE layout.@effect/sql-pgand the Workers types are not dependencies of this package, and I did not add dev dependencies for one snippet.Validation
bun run build: ok.bun run typecheck: ok.bunx vitest run --testTimeout=60000 --hookTimeout=60000against ClickHouse 26.8.2.7: 60 files, 1034 tests passed, 0 skipped.node scripts/check-doc-citations.mjs: ok (26 files).node scripts/check-exports-documented.mjs: ok (287 /clickhouse, 205 /postgres exports).node scripts/check-doc-examples.mjs: ok (24 files typechecked, behavior checks passed, including the two new examples).bun scripts/check-package.ts: ok.Need help on this PR? Tag
@codesmith-botwith what you need.