Note that there are some explanatory texts on larger screens.

plurals
  1. USngreen
    primarykey
    data
    text
    plurals
    1. COThe problem with 404 is that it is cacheable. (See http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-25#section-6.1). Retrying a 404 until it succeeds is probably not a good pattern to use and seems very non-standard. 4xx errors are specifically client errors. 4xx errors imply that the client made a mistake or failed to pass some required piece of information needed to access a resource. In normal usage, getting a Location header that resolves to a 404 is a bug. (E.g. a race condition or database consistency issue.)
      singulars
    2. COFor printable URLs, minimize the probability of human error by using [Base32](http://en.wikipedia.org/wiki/Base32) encoding. Personally, I think the z-base-32 format is the best for this purpose because it was specifically designed to be used by humans.
      singulars
    3. COI would guess that getting the source for Microsoft's driver is probably not an option, so your only option, if you get a stack trace again, would be to contact Microsoft support. In terms of exception handling, it's generally a bad idea to just `catch (Exception)` because you also catch `RuntimeException` subclasses, and in this case it caused you to lose important information. Also, your `TableObjectException` class hopefully supports chaining, but you're not using that feature in your sample code either. Chaining is another important tool that keeps you from losing stack traces.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload