Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

2
  • Great answer. Unfortunately my codebase has zero technical documentation so contracts aren't present. To clarify: Yes, null will be returned from userDb.Get if there is no matching entry in the database. Commented Oct 2, 2016 at 16:04
  • 3
    @Frayt Okay, but is a NullPointerException really what you want in this case? Wouldn't is be better to throw a (checked?) UnknownUserException or return a status code from UpdateUser? A non-existing user seems like a fairly normal case that shouldn't crash your application – which an NPE usually does (or, at least, should, as it indicates a bug). Commented Oct 2, 2016 at 16:08