Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I agreee that your question does have most of the answers. </p> <p>This is what I would probably do. I would probably start with Sebastian Bergman's tools, especially phploc so you can get an idea of the scope of the mess (codebase) you are looking at. It gives you class, function counts, etc not just lines of code.</p> <p>Next I would look in the apache logs or google analytics and get the top 10 most requested php url's. I'd setup XDebug with profiling and run through those top 10 requests and get the files, call tree. (You can view these with a cachegrinder tool)</p> <p>Finally, I'd read through the entire execution path of 1 or two of those traces, that is most representative of the whole. I'd use my Eclipse IDE but print them out and go to town with a highlighter is valid as well.</p> <p>The top 10 method might fail you if there are multiple systems cobbled together. You should see quickly with Xdebug whether the top 10 are coded similarliy are if each is a unique island. </p> <p>I would look at the mysql databases and try to understand what they are all for, espacially looking at table prefixes, you may have a couple of different apps stacked on top of each other. If there are large parts of the db not touched by the top 10 you need to go hunting for the subapps. If you find other sub apps run them through the xdebug profiler and then read through one of the paths that is representative of that sub app.</p> <p>Now go back and look at your scope numbers from phploc and see what percentage of the codebase (probably count classes, or functions) was untouched during your review. </p> <p>You should have a basic understanding of the most often run code and and idea of how many nooks and crannies and closets for skeleton storage there are.</p>
    singulars
    1. This table or related slice is empty.
    1. POEfficiently gathering information about the inner workings of a new PHP project. Tools? Techniques? Scripts?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USBryan Waters
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POEfficiently gathering information about the inner workings of a new PHP project. Tools? Techniques? Scripts?
      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. COphploc is a GOLD-suggestion! This is just the tool I was already thinking about how to write it myself. / Looking for similarities in the code pathes for the top 10 is also gold - intuitive, yet, easy to neglect. / Relating app to code to db, then looking for unused parts in DB and figuring out to what code/app they are related to - interesting strategy! - Thanks!
      singulars
      1. PO
      1. USRaffael
    2. COThanks for the points! I hope you get things sorted out on your new project quickly, and I hope the previous php coders were better than most :)
      singulars
      1. PO
      1. USBryan Waters
 

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