Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Don't ignore exceptions, for exceptional and unexpected errors.</p> <p>However, just answering your points, the question is ultimately subjective. The key issue is to consider what will be easier for your consumers to work with, whilst quietly nudging them to remember to check error conditions. In my opinion, this is nearly always the "Return a status code, and put the value in a separate reference", but this is entirely one mans personal view. My arguments for doing this...</p> <ol> <li>If you choose to return a mixed value, then you've overloaded the concept of return to mean "Either a useful value <em>or</em> an error code". Overloading a single semantic concept can lead to confusion as to the right thing to do with it.</li> <li>You often cannot easily find values in the function's codomain to co-opt as error codes, and so need to mix and match the two styles of error reporting within a single API.</li> <li>There's almost no chance that, if they forget to check the error status, they'll use an error code as if it were actually a useful result. One can return an error code, and stick some null like concept in the return reference that will explode easily when used. If one uses the error/value mixed return model, it's very easy to pass it into another function in which the error part of the co-domain is valid input (but meaningless in the context).</li> </ol> <p>Arguments for returning the mixed error code/value model might be simplicity - no extra variables floating around, for one. But to me, the dangers are worse than the limited gains - one can easily forget to check the error codes. This is one argument for exceptions - you literally can't forget to handle them (your program will flame out if you don't).</p>
    singulars
    1. This table or related slice is empty.
    1. POWhich school of reporting function failures is better
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USAdam Wright
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhich school of reporting function failures is better
      singulars
      1. PTQuestion
    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. CO+1 - so long as you only use exceptions for truely exceptional cases. Their unwind and clean-up is an expensive operation (relatively). The clue is in the name.
      singulars
      1. PO
      1. USRagster
    2. COIf there is a well-defined notion of an invalid return value, then overloading this way isn't a big deal. For example `CreateFile` returns a NULL handle on failure, where NULL is always understood to be invalid. When there is no such notion, such as `atoi` returning 0 on failure, it's not so great.
      singulars
      1. PO
      1. USSteven Sudit
    3. COIn addition, some API's return a success/failure code with each call. The problem is that this combines *whether* a function worked with the details of how it worked. For example, ODBC returns a code where positive values are different types of success and negatives are different types of errors. This is not good, either.
      singulars
      1. PO
      1. USSteven Sudit
 

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