Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><a href="https://blogs.msdn.microsoft.com/ericlippert/2008/09/10/vexing-exceptions/" rel="noreferrer">Eric Lippert says</a> there are 4 kinds of exceptions.</p> <ul> <li>Fatal exceptions are not your fault, you cannot prevent them, and you cannot sensibly clean up from them.</li> <li>Boneheaded exceptions are your own darn fault, you could have prevented them and therefore they are bugs in your code.</li> <li>Vexing exceptions are the result of unfortunate design decisions. Vexing exceptions are thrown in a completely non-exceptional circumstance, and therefore must be caught and handled all the time.</li> <li>And finally, exogenous exceptions appear to be somewhat like vexing exceptions except that they are not the result of unfortunate design choices. Rather, they are the result of untidy external realities impinging upon your beautiful, crisp program logic.</li> </ul> <p>Your constructor should never throw a fatal exception on its own, but code it executes may cause a fatal exception. Something like "out of memory" isn't something you can control, but if it occurs in a constructor, hey, it happens.</p> <p>Boneheaded exceptions should never occur in any of your code, so they're right out.</p> <p>Vexing exceptions (the example is <code>Int32.Parse()</code>) shouldn't be thrown by constructors, because they don't have non-exceptional circumstances.</p> <p>Finally, exogenous exceptions should be avoided, but if you're doing something in your constructor that depends on external circumstances (like the network or filesystem), it would be appropriate to throw an exception.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhen is it right for a constructor to throw an exception?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJohn Weisz
    1. USJacob Krall
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COSo where does Argument[Null]Exception lie in this scheme? Is it a boneheaded exception, and so shouldn't be thrown? Or is it a fatal exception and is therefore ok to be thrown?
      singulars
      1. PO
      1. USalastairs
    2. COI realize now that I didn't include a link to the original article, http://blogs.msdn.com/b/ericlippert/archive/2008/09/10/vexing-exceptions.aspx Things like ArgumentException/ArgumentNullException are boneheaded: just plain bugs in the calling code. He says "Fix your code so that it never triggers a boneheaded exception – an 'index out of range' exception should never happen in production code."
      singulars
      1. PO
      1. USJacob Krall
    3. CO@alastairs: You should definitely *throw* ArgumentExceptions, because the only alternative is to pretend that the arguments are valid when they're not. (Leading to NullReferenceExceptions, or possibly much worse things.) But like Jacob says, you should **never** catch them.
      singulars
      1. PO
      1. USJoren
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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