Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Although there are certainly good articles on that topic, none of them is a substitute of real-world experience.</p> <p>Maintainability is nothing you can plan straight ahead, except on very small projects. It is something you need to take care of during the whole project. In fact, creating loads of classes and infrastructure code in advance can produce code which is even harder to understand than naive spaghetti code.</p> <p>So my advise is to <b>clean up your existing projects</b>, by continuously refactoring them. Look at the parts which were a pain to change, and strive for simpler solutions that are easier to understand and to adjust. If the code is even too bad for that, consider rewriting it from scratch.</p> <p>Don't start new projects and expect them to succeed, just because your read some more articles or used a new framework. Instead, identify the failures of your <i>existing</i> projects and fix their <i>specific</i> problems. Whenever you need to change your code, ask yourself how to restructure it to support similar changes in the future. This is what you need to do anyway, because there <i>will</i> be similar changes in the future.</p> <p>By doing those refactorings you'll stumble across various <i>specific questions</i> you can ask and read articles about. That way you'll learn more than by just asking general questions and reading general articles about maintenance and frameworks.</p> <p>Start cleaning up your code <b>today</b>. Don't defer it to your future projects.</p> <hr> <p>(The same is true for documentation. Everyone's first docs were very bad. After several months they turn out to be too verbose and filled with unimportant stuff. So complement the documentation with solutions to the problems you <i>really</i> had, because chances are good that next year you'll be confronted with a similar problem. Those experiences will improve your writing style more than any "how to write good" style guide.)</p>
    singulars
    1. This table or related slice is empty.
    1. POHow do I plan an enterprise level web application?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USvog
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow do I plan an enterprise level web application?
      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. 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