Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>IMHO, it shouldn't be an exception at all. An exception, in my mind, should be used when exceptional things happen, and not as flow controls.</p> <p>In your case, it isn't at all an exceptional status that someone tries to transfer more money than the balance allows. I figure these things happen very often in the real world. So you should program against these situations. An exception might be that your if-statement evaluates the balance good, but when the money is actually being subtracted from the account, the balance isn't good anymore, for some strange reason.</p> <p>An exception might be that, just before calling <code>transferTo()</code>, you checked that the line was open to the bank. But inside the <code>transferTo()</code>, the code notices that the line isn't open any more, although, by all logic, it should be. <em>THAT</em> is an exception. If the line can't be opened, that's not an exception, that's a plausible situation.</p> <p>IMHO recap: Exceptions == weird black magic.</p> <p><strong><em>being-constructive-edit:</em></strong></p> <p>So, not to be all too contradictive, the method itself might very well throw an exception. But the use of the method should be controlled: You first check the balance (outside of the <code>transferTo()</code> method), and if the balance is good, only then call <code>transferTo()</code>. If <code>transferTo()</code> notices that the balance, for some odd reason, isn't good anymore, you throw the exception, which you diligently catch. </p> <p>In that case, you have all your ducks in a row, and know that there's nothing more you can do (because what was <code>true</code> became <code>false</code>, as if by itself), other than log the exception, send a notification to someone, and tell the customer politely that someone didn't sacrifice their virgins properly during the last full moon, and the problem will be fixed at the first possible moment.</p> <p><strong><em>less-enterprisey-suggestion-edit:</em></strong></p> <p>If you are doing this for your own pleasure (and the case seems to be this, see comments), I'd suggest returning a boolean instead. The usage would be something like this:</p> <pre><code>// ... boolean success = transferTo(otherAccount, ONE_MILLION_DOLLARS_EXCLAMATION); if (!success) { UI.showMessage("Aww shucks. You're not that rich"); return; // or something... } else { profit(); } // ... </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POIn Java, when should I create a checked exception, and when should it be a runtime exception?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USHenrik Paul
    1. USHenrik Paul
    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. VTDownMod
    1. COThanks, but you took this much more seriously than I intended. Very informative nonetheless, but it doesn't really address my question. This is a very simple class that I'm doing for a personal budget tracking application, and it's more of a learning project than a full-fledged application.
      singulars
      1. PO
      1. USHosam Aly
    2. COBut what do you suggest to use other than the exception? Assuming the account doesn't allow negative balance, what should I do when the parameter would cause this situation?
      singulars
      1. PO
      1. USHosam Aly
    3. COOther than exception, you have only error codes. But exception gives you full object you can construct and return.
      singulars
      1. PO
      1. USPeter Štibraný
 

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