Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The idiomatic way to solve the problem is not to indicate that your code can throw exceptions, but to implement exception safety in your objects. The standard defines several exception guarantees objects should implement:</p> <ul> <li>No-throw guarantee: The function will <em>never</em> throw an exception</li> <li>Strong exception safety guarantee: If an exception is thrown, the object will be left in its initial state.</li> <li>Basic exception safety guarantee: If an exception is thrown, the object be left in a valid state.</li> </ul> <p>And of course, the standard documents the level of exception safety for every standard library class.</p> <p>That's really the way to deal with exceptions in C++. Rather than marking which code can or can not throw exceptions, use RAII to ensure your objects get cleaned up, and put some thought into implementing the appropriate level of exception safety in your RAII objects, so they're able to survive without special handling if an exception is thrown.</p> <p>Exceptions only really cause problems if they allow your objects to be left in an <em>invalid</em> state. That should never happen. Your objects should <em>always</em> implement at least the basic guarantee. (and implementing a container class which provides the proper level of exception safety is an enlightening C++ exercise ;))</p> <p>As for documentation, when you're <em>able</em> to determine for certain which exceptions a function may throw, by all means feel free to document it. But in general, when nothing else is specified, it is assumed that a function may throw. The empty throw specfication is sometimes used to document when a function <em>never</em> throws. If it's not there, assume that the function may throw.</p>
    singulars
    1. This table or related slice is empty.
    1. POIs there a generally accepted idiom for indicating C++ code can throw exceptions?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USjalf
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POIs there a generally accepted idiom for indicating C++ code can throw exceptions?
      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. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO"Exceptions only really cause problems if they allow your objects to be left in an invalid state." > No, they are also a problem when the caller does not know what a method throws and does not handle every exception properly.
      singulars
      1. PO
      1. USfnieto - Fernando Nieto
    2. CODepends on the kind of problem we're talking about. I'm talking about the most fundamental problem: Your program is left in an invalid or indeterminate state. That won't happen if your objects are individually exception-safe. And that means you can simply handle the exception whereever it makes sense, without having to worry about correctness.
      singulars
      1. PO
      1. USjalf
 

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