Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>In my experience using graphviz to render graphs of that size (~ 700 nodes), minimal trial-and-error adjustment to this combination of attribute settings--some structural, some purely aesthetic--for all three objects (graph, nodes, and edges) should do what you want:</p> <p><strong>reduce the minimum separation between nodes</strong>, via 'nodesep'; e.g., <em>nodes[nodesep=0.75]</em>; this will make your graph being "too compact." (<em>nodesep</em> and <em>ranksep</em> probably affect how dot draws a graph more than any other adjustable parameter)</p> <p><strong>reduce the minimum distance between nodes of different ranks</strong>, e.g, <em>nodes[ranksep=0.75]</em>; 'ranksep' sets the minimum distance between nodes of different ranks--this will affect your graph layout significantly if your graph is comprised of many ranks</p> <p><strong>increase the edge weights</strong>, eg, <em>edge[weight=1.2]</em>; this will make the edges shorter, in turn making the entire graph more compact</p> <p><strong>remove node borders and node fill</strong>, e.g., <em>nodes[color=none; shape=plaintext]</em>, especially for oval-shaped nodes, a substantial fraction of the total node space is 'unused' (ie, not used to display the node label); each node's footprint is now reduced to just its text</p> <p><strong>explicitly set the font size for the nodes</strong> (the node borders are enlarged so that they surround the node text, which means that the font size and amount of text for a given node has a significant effect on its size); [fontsize=11] should be large enough to be legible yet also reduce the 'cluttered' appearance (the default size is 14)</p> <p><strong>use different colors for nodes and edges</strong>--this will make your graph easier to read; e.g., set the node 'text' fontcolor to blue and the edge fontcolor to "grey" to help the eye distinguish the two sets of graph structures. This will make a bigger difference than you might think.</p> <p><strong>explicitly set total graph size</strong>, eg, <em>graph[size="7.75,10.25"]</em> (ensures that your graph fits on an 8.5 x 11 page and that it occupies the entire space)</p>
    singulars
    1. This table or related slice is empty.
    1. POReducing the size (as in area) of the graph generated by graphviz
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USStuart Golodetz
    1. USdoug
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POReducing the size (as in area) of the graph generated by graphviz
      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. VTAcceptedByOriginator
    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. COThanks for the detailed response. The only problem I have is that setting the font size doesn't seem to reduce the overall node size for it. It seems like the only thing that gets smaller is the font.
      singulars
      1. PO
      1. USgarsh0p
    2. COno problem. Regarding 'fontsize', if you removed the node borders and node fill *first*, so that the representation of each node is just the node text, then reducing the text size is exactly what you want, because it reduces the 'apparent' node size. (Granted, removing the node borders/fill doesn't always improve overall 'resolution'--just depends on your graph, but you'll know as soon as you try it).
      singulars
      1. PO
      1. USdoug
    3. COThe suggestions above are great and provide much more power than what I do... `cat [something.dot] | dot-Gdpi=64 -Tpng:cairo:cairo > [outfile.png]` which just scales the graph...
      singulars
      1. PO
      1. USForbesmyester
 

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