Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I once heard a saying something like "If your class is getting too big and too complex, then refactor it into a couple or a few smaller classes."</p> <p>I would strongly suggest you take something along this approach until you are more experienced. This will allow you to really get a feel for when functionality needs to be broken up. If you try to over-engineer your project without any experience to guide you, then you are sure to make lots of missteps. I found that some people get so caught up in the principles and practices they start implementing designs that are very speculative. By speculative I mean that they might think "well later on we might want to add robust authentication", so they design everything to support that. The "additional anticipated future" features list quickly grows huge, and you will find yourself designing for all kinds of scenarios. You will run into problems like "how do I get this particular class to both be compatible with my future authentication service and my future monitoring service." You will bang your head against the wall trying to solve problems which are not even relevant to your first release.</p> <p>If you take my advice though, it is important that after you get a prototype up in running, that you then take a serious look at your design. Now is the time that you can look at larger classes, and ask yourself if they make sense. One test is to imagine how easy it would be to explain the usage of the class to someone else. If it is complex or quirky, then a redesign may be in order. If they are too big and serving more than one purpose, then breaking it apart is probably appropriate.</p> <p>The important thing to remember about design practices is that certain techniques should only be applied where appropriate. Don't try to force your application into a certain architecture or design if it doesn't fit well. You will learn these things with experience and time. The best thing you can do is practice. Don't spend too much time over thinking things, if you dive right in, you will find plenty of opportunities to reflect on your techniques. You obviously have the right mindset already of trying to do things the "right" way, which is good. Just don't over do it.</p> <p>There are lots of "patterns and practices" out there. </p>
    singulars
    1. This table or related slice is empty.
    1. POWhat is your way to design a program?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAaronLS
    1. USAaronLS
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhat is your way to design a program?
      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. VTAcceptedByOriginator
    1. COIn addition to what @AaronLS said above, you must be careful not to start too big too quickly. What I mean by this is, in the beginning, don't try to design the structure of a very large system (20, 30, 50 classes). Start with smaller applications (like a Calculator or unit convertor, for example) and only after move on to bigger systems. The last thing I will say is that maybe it's not a bad idea to ask a friend to look over your design and give you some tips... you will be more motivated that way :) . Good luck.
      singulars
      1. PO
      1. USRadu Murzea
 

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