Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Yes. It is bad practice. It will compile and run just fine, but in answer to your question, it is bad practice.</p> <p>If you want to manually update your iterator, use a <code>while</code> loop.</p> <p>Anything you can do with a <code>for</code> loop can also be done with a <code>while</code> loop. The choice in what loop to actually implement is a matter of readability. In <code>for</code> loops, people expect the iterator to be updated in the update statement and only in the update statement.</p> <p>If you can't figure out how to rewrite your loop so your iterator is updated only in the update statement, consider something like this:</p> <pre><code>for(int i=0; i&lt;someValue; ++i /*i also updated at line 18*/) </code></pre> <p>Just as an example. This is still worse than rewriting the code so it's not updated at line 18 (or whatever line) but far better than updating it at line 18 and not leaving the comment here in the update statement.</p> <p>Alternatively, per comments on this answer, try this:</p> <pre><code>for(int i=0; i&lt;someValue; /*see body*/) { //do stuff //update i //do stuff } </code></pre> <p>Now in this case, your update statement is completely empty, so even without the <code>/*see body*/</code> comment, anyone maintaining your code already know that <code>i</code> must be modified somewhere within the body. And the <code>++i</code> behavior from the update statement can be recreated simply by adding <code>++i</code> as the last line of the <code>for</code> loop.</p>
    singulars
    1. This table or related slice is empty.
    1. POIs manually updating a for loop iterator bad practice?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USnhgrif
    1. USnhgrif
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POIs manually updating a for loop iterator bad practice?
      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. COI sometimes use the syntax: `for (int i = 0; i < LatLngSize; /*see body*/ ) { /* modify i in here */ }`
      singulars
      1. PO
      1. USazz
    2. CO@DerFlatulator Haha, I must've been editing that in as you left the comment. I've never done that myself personally, but just had that thought after posting my answer. Although, your version actually has an empty update statement, which is probably the best version.
      singulars
      1. PO
      1. USnhgrif
    3. COI do pay special attention to leave a brief comment to make sure that people reading it note that the iterating value is modified inside the body of the loop. Unfortunately people see a for loop and make assumptions.
      singulars
      1. PO
      1. USazz
 

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