Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I had a similar situation. I'd say you go like this:</p> <ul> <li>If its a database driven application, start from the database and try to make sense of each table, its fields and then its relation to the other tables. </li> <li> Once fine with the underlying store, move up to the ORM layer. Those table must have some kind of representation in code. </li> <li> Once done with that then move on to how and where from these objects are coming from. Interface? what interface? Any validations? What preprocessing takes place on them before they go to the datastore? </li> </ul> <p>This would familiarize you better with the system. Remember that trying to write or understand unit tests is only possible when you know very well <em>what</em> is being tested and <em>why</em> it needs to be tested in <em>only</em> that way.</p> <p>And in case of a large application that is not driven towards databases, I'd recommend an other approach:</p> <ul> <li>What the main goal of the system?</li> <li>What are the major components of the system then to solve this problem?</li> <li>What interactions each of the component has among them? Make a graph that depicts component dependencies. Ask someone already working on it. These componentns must be exchanging something among each other so try to figure out those as well (like IO might be returning File object back to GUI and like)</li> <li>Once comfortable to this, dive into component that is least dependent among others. Now study how that component is further divided into classes and how they interact wtih each other. This way you've got a hang of a single component in total</li> <li>Move to the next least dependent component</li> <li>To the very end, move to the core component that typically would have dependencies on many of the other components which you've already tackled</li> <li>While looking at the core component, you might be referring back to the components you examined earlier, so dont worry keep working hard!</li> </ul> <p><b>For the first strategy:</b> Take the example of this stackoverflow site for instance. Examine the datastore, what is being stored, how being stored, what representations those items have in the code, how an where those are presented on the UI. Where from do they come and what processing takes place on them once they're going back to the datastore.</p> <p><b>For the second one</b> Take the example of a word processor for example. What components are there? IO, UI, Page and like. How these are interacting with each other? Move along as you learn further.</p> <p>Be relaxed. Written code is someone's mindset, froze logic and thinking style and it would take time to read that mind.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhat's the best way to become familiar with a large codebase?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USMohsin Shafique
    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. This table or related slice is empty.
    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