Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>With the background you give - mostly self-educated and no peers to discuss your current development - you should <strong>absolutely</strong> check out other libraries and tools. At the very least, get new input how code can be designed and problems can be solved. You may feel that you have achieved something - and you have, congratulations - but that's a plateau, not the peak.</p> <p><em>"I have no time to learn something new because I have so much to do"</em><br> - that's what I read in your rationale for more code. This is a warning sign - you are moving yourself into a dangerous position. No time to learn? No time to document? No time to think of all the implications? No time to do it right? No time to train a new employee? No time to call it a day?</p> <p>You won't solve this problem by learning prism, or any other library, but it's the wrong rationale.</p> <p>Third, code bogs you down. Having more code to maintain makes you slower. One-man-startups can crank out hundreds, even thousands of LOC per day for days and weeks. As projects and organizations get larger, you end up with an average of a few dozen. </p> <p>As a recommendation from personal experience: write bulding blocks, not frameworks. Frameworks are great when you have to make the same application with different company logos over and over. Or, as TDWTF's Alex says, <a href="http://thedailywtf.com/Articles/Patterns-of-Failure.aspx" rel="nofollow noreferrer">the key is in the differences</a> not the similarities. </p> <hr> <p>I don't want you to stop writing code, far from it. But you are discussing a tradeoff, and from the information you've given, I would recommend to put most weight on learning new things.</p>
    singulars
    1. This table or related slice is empty.
    1. POWriting extra code to avoid learning new frameworks
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USpeterchen
    1. USpeterchen
    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. CO"No time to do it right?" - Ouch. Thanks. +1
      singulars
      1. PO
      1. USPhil
    2. COConsider it the big evil looming at the horizon... ;) --- Code is never perfect, but there's some code that's good enough and a lot of code that isn't.
      singulars
      1. PO
      1. USpeterchen
 

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