zio-jdbc icon indicating copy to clipboard operation
zio-jdbc copied to clipboard

Effectively leverage typed errors by defining precise sealed hierarchy of errors

Open jdegoes opened this issue 2 years ago • 5 comments

Ideally, we would have a sealed trait that defines every possible error that can result from JDBC, each as a case class that stores relevant context, including any underlying Throwable. The sealed trait should be engineered to group related exceptions into a finite number of logical categories. We need confidence that we have done enough research to perform this grouping and that it is necessary and sufficient for all JDBC methods. Finally, we need to update all query methods to return the more precise error type, using refineToOrDie, etc.

jdegoes avatar Nov 01 '22 10:11 jdegoes

/bounty $100

jdegoes avatar May 05 '23 08:05 jdegoes

💎 $100 bounty • ZIO

Steps to solve:

  1. Start working: Comment /attempt #74 with your implementation plan
  2. Submit work: Create a pull request including /claim #74 in the PR body to claim the bounty
  3. Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts

Thank you for contributing to zio/zio-jdbc!

Add a bountyShare on socials

Attempt Started (GMT+0) Solution
🟡 @pablf May 24, 2023, 11:12:03 AM #142

algora-pbc[bot] avatar May 05 '23 08:05 algora-pbc[bot]

/attempt #74

pablf avatar May 24 '23 11:05 pablf

💡 @pablf submitted a pull request that claims the bounty. You can visit your org dashboard to reward.

algora-pbc[bot] avatar May 27 '23 19:05 algora-pbc[bot]

💡 @pablf submitted a pull request that claims the bounty. You can visit your org dashboard to reward.

algora-pbc[bot] avatar Jun 14 '23 15:06 algora-pbc[bot]