Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Exceptions are for exceptional cases, so using exceptions on a <em>known</em> and <em>expected</em> error situation is "bad". You also are more likely, now, to have try-catches everywhere to handle this error specifically because you expect this error situation to happen.</p> <p>Making your return value a parameter is acceptable if your only error condition (say -1) is confusable with a real value. If you can have a negative tile number then this is a better way to go.</p> <p>A nullable int is a possible alternative to a reference parameter but you are creating objects with this so if an "error" is routine they you may be making more work this way than a reference parameter. As Roman pointed out in a comment elsewhere you will have C# vs. VB issues with <a href="http://www.panopticoncentral.net/archive/2004/06/04/1180.aspx" rel="nofollow noreferrer">the nullable type</a> being introduced too late for VB to provide nice syntactic sugar like C# has.</p> <p>If your tiles can only be non-negative then returning -1 is an acceptable and traditional way to indicate an error. It would also be the least expensive in terms of performance and memory.</p> <hr> <p>Something else to consider is self-documentation. Using -1 and an exception are convention: you'd have to write documentation to make sure the developer is aware of them. Using an <code>int?</code> return or a reference parameter would better self-describe itself and wouldn't <em>require</em> documentation for a developer to know how to handle the error situation. Of course :) you should always write the documentation, just like how you should floss your teeth daily.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhich style of return should I use?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USColin Burnett
    1. USColin Burnett
    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. COI disagree with your first statement. Exceptions are for situations where your method cannot do what it promises to do. The fact that this should be a rare case is secondary. Of course, allowances should be made for performance.
      singulars
      1. PO
      1. USAri Roth
    2. CO+1 By far the best and most clear explanation.
      singulars
      1. PO
      1. USRyan Rodemoyer
    3. COPyran, you're splitting hairs. undsoft *knows* that a non-found tile will be common and it is *supposed* to handle missing tiles with grace. If, for example, the coordinates were out of bounds then that would be exceptional. However, if this was a method close to user-input and out-bounds errors were expected to be often then, again, an exception would be the wrong way to go.
      singulars
      1. PO
      1. USColin Burnett
 

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