Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prefix RethinkDB server exceptions with RethinkDB server: #100

Merged
merged 1 commit into from
Nov 19, 2015

Conversation

danielcompton
Copy link
Collaborator

It is sometimes difficult for people to distinguish between an exception
thrown in the client library, and an exception from the server which is
sent back and thrown by the client library. This change prefixes
serverside exceptions to make this distinction clearer.

Fixes #95, fixes #94

@danielcompton
Copy link
Collaborator Author

I'm not 100% sure if I love this solution of stringly typed programming. However it's in a string error message already, so maybe this is OK. Feedback welcome :)

I haven't looked into #77 in too much depth yet, but I don't think this should cause a future conflict, one option for #77 is to add the error type as a keyword in the ex-info map.

It is sometimes difficult for people to distinguish between an exception
thrown in the client library, and an exception from the server which is
sent back and thrown by the client library. This change prefixes
serverside exceptions to make this distinction clearer.

Fixes #95, fixes #94
@danielcompton danielcompton merged commit 694266a into master Nov 19, 2015
@danielcompton danielcompton deleted the exception-prefix branch November 19, 2015 09:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Distinguish RethinkDB exceptions from Java exceptions java.lang.Exception: Array over size limit 100000.
1 participant