Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>Developers should understand the performance <em>implications</em> of <em>their</em> coding choices.</strong></p> <p><strong>It's not terribly difficult to write an algorithm that results in non-linear performance</strong> - polynomial, exponential or worse. If you don't understand to some extent how the language, compiler, and libraries support your algorithm you can fall into trap that no amount of processing power will dig you out of. Algorithms whose runtime or memory usage is exponential can quickly exceed the ability of <em>any</em> hardware to execute in a reasonable time.</p> <p><strong>Assuming that hardware can scale to a poorly designed algorithm/coding choice is a bad idea.</strong> Take for example a loop that concatenates 100,000 small strings together (say into an XML message). This is not an uncommon situation - but when implementing using individual string concatenations (rather than a StringBuffer) this will result in 99,999 intermediate strings of increasing size that the garbage collector has to dispose of. This can easily make the operation fail if there's not enough memory - or at best just take forever to run.</p> <p>Now in the above example, some Java compilers can usually (but not always) rewrite the code to use a StringBuffer behind the scenes - but <em>this is the exception, not the rule</em>. In many situations the compiler simply cannot infer the intent of the developer - and it becomes the <em>developer's</em> responsibility to write efficient code.</p> <p><strong>One last comment - writing efficient code does not mean spending all your time looking for micro-optimizations.</strong> <em>Premature optimization is the enemy of writing good code</em>. However, you shouldn't confuse premature optimization with understanding the O() performance of an algorithm in terms of time/storage and making good choices about which algorithm or design to use in which situation.</p> <p><em>As a developer you cannot ignore this level of knowledge and just assume that you can always throw more hardware at it.</em> </p>
    singulars
    1. This table or related slice is empty.
    1. POWhat's wrong with my logic here?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USLBushkin
    1. USLBushkin
    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. This table or related slice is empty.
 

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