Repository navigation
feat: expose native driver failures through public modules - #529
Conversation
✅ Deploy Preview for prisma-dart canceled.
|
|
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 37 minutes. View limit detailsLimit details: You’ve used all 2 included reviews currently available. Review configuration: ⚙️ Run configuration
📒 Files selected for processing (8)
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 |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Refs #516
Driver exceptions already propagated unchanged, but ORM consumers could not name them through the public driver modules. Re-export PostgreSQL's native error types and SQLite's exception, primary-code constants and extended-code constants through each module's implementation and explicit public entrypoint.
Applications can catch native failures outside a transaction using only ORM public imports. SQLSTATE, severity, table/constraint metadata and SQLite result codes retain their native meanings. Expected registration conflicts still use
createIfAbsentwith an explicit target. StandardTimeoutExceptionstays indart:async; no wrapper, error remapping or retry behavior is added.Validation: twenty live SQLite/PostgreSQL business tests pass and analysis is clean. Two new cases provoke unique and missing-parent failures, check the actual public types/codes, verify an earlier write rolls back and confirm subsequent root queries remain usable. The independent archive consumer now compiles all eight native symbols from ORM-only dependencies and repeats those real rollback checks. Model generation and reviewed migration definitions/fingerprints are unchanged.