Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Addressing your points in order:</p> <ol> <li>Well-designed types usually render Doxygen format comments a waste of time.</li> <li>While true as stated ("shenanigans" are bad by definition), not all use of globals is really as bad as many people imply. If you have to pass a parameter more than about four times before it's really used, chances are that a global will be less error prone.</li> <li>Eight or even six parameters is usually excessive. Any more than two or three starts to indicate that the function is doing more than one thing. One obvious exception is a constructor that aggregates a number of other items into an object (e.g. an address object that takes a street name, number, city, country, postal code, etc., as inputs).</li> <li>Better stated as "write const-correct code."</li> <li>Given C++'s default parameter capability, it's generally best to sort in ascending order of likelihood to use a default value.</li> <li>Don't. Just don't! If it's not obvious what are inputs and what are outputs, that pretty much proves that the basic design is fatally flawed.</li> </ol> <p>As for ideas I think are actually good:</p> <ol> <li>As implied in the first point, concentrate on types. Once you get them right, most of the other problems just disappear. </li> <li>Use a few (even just one) central theme(s). For Lisp, everything is a list. For Unix, everything is a file (and files are all simple streams of bytes). Emulate this simplicity.</li> </ol> <p>Edit: replying to comments:</p> <ol> <li>While you do have something of a point, my experience still indicates that documentation produced with Doxygen (and similar such as javadoc) is almost universally useless. In theory the tool doesn't prevent decent documentation, but in fact it's rare at best.</li> <li>Globals certainly can cause problems -- but I'm old enough to have used Fortran back before it provided much alternative, and with some care it really wasn't nearly as bad as many people imply. A lot of the stories seem to be at least third hand, with a bit of extra "spice" added each time they're re-told. I've seen one story that sounds a lot like an exaggerated version of one I told a couple decades ago or so...</li> <li>Hm...Markdown formatting doesn't seem to approve of my skipping numbers.</li> <li>And again...</li> <li>My comment was specific to C++, but quite a few other languages also support default parameters and/or overloading, and it can apply about as well to most of them. Even without it, a call like <code>f(param1, param2, 0,0,0);</code> is pretty easy to see as having default parameters. To an extent, ordering by usage is handy, but when you do the order you pick doesn't matter nearly as much as simply being consistent.</li> <li>True, a <code>void *</code> parameter doesn't tell you much -- but a <code>MODIFY void *</code> is little better. A real type and consistent use of <code>const</code> provides far more information and gets checked by the compiler. Other languages may not have/use const, but they probably don't have macros either. OTOH, some directly support what you want -- e.g., Ada has <code>in</code>, <code>out</code> and <code>inout</code> specifiers.</li> </ol>
    singulars
    1. This table or related slice is empty.
    1. POHow to improve maintainability of functions
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJerry Coffin
    1. USJerry Coffin
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to improve maintainability of functions
      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 for comments on types. While everything is not necessarily a list in Lisp this is still a good point.
      singulars
      1. PO
      1. USasm
    2. CO@Andrew: My oversimplification is merely another example of the same idea. That's my story and I'm stickin' to it!
      singulars
      1. PO
      1. USJerry Coffin
    3. CO1 "Well-designed types usually render Doxygen format comments a waste of time" - perhaps if you are looking in the code. Perhaps not if you are looking on the company's itra-web for interface documentation (which is easier to navigate with hyperlinks). 2 - globals not bad?? Hmm, ok, make that "naked" globals. If not wrapped in a fucntion, globals are A Bad Thing. YMMNV. 3 - yes, I tend to smell bad code at about 4. 5 - excellent point!! (although the post is language agnostic) IS it enough if I reorder to output, modify, input? contd...
      singulars
      1. PO
      1. USMawg
 

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