sqlt-graph1p
Automatically create a graph from a database schema
Usage
Options: {-l | --layout
Layout
schema
for
GraphViz}
set to
"0"
to
undefine)
--fontsize
custom
font
size
for
node
and
edge
labels
--fontname
name
of
custom
font
(or
full
path
to
font
file)
for
multiple {node
attributes
--edgeattr
same
as
--nodeattr,
but
for
edge
attributes
--graphattr
same
as
--nodeattr,
but
for
graph
attributes
--natural-join
Perform
natural
joins
--natural-join-pk
Perform
natural
joins
from
primary
keys
only
--show-datatypes
Show
datatype
of
each
field
--show-sizes
Show
column
sizes
for
VARCHAR
and
CHAR
fields
--show-constraints
Show
list
of
constraints
for
each
field
-s | --skip
Fields
to
skip
in
natural
joins
--skip-tables
Comma-separated
list
of
table
names
to
exclude
--skip-tables-like
Comma-separated
list
of
regexen
to
exclude
tables
--debug
Print
debugging
information
--trace
Print
parser
trace
info}
Overview
This script will create a graph of your schema. Only the database driver argument (for SQL::Translator) is required. If no output file name is given, then image will be printed to STDOUT, so you should redirect the output into a file.
The default action is to assume the presence of foreign key relationships defined via "REFERNCES" or "FOREIGN KEY" constraints on the tables. If you are parsing the schema of a file that does not have these, you will find the natural join options helpful. With natural joins, like-named fields will be considered foreign keys. This can prove too permissive, however, as you probably don't want a field called "name" to be considered a foreign key, so you could include it in the "skip" option, and all fields called "name" will be excluded from natural joins. A more efficient method, however, might be to simply deduce the foreign keys from primary keys to other fields named the same in other tables. Use the "natural-join-pk" option to achieve this.
If the schema defines foreign keys, then the graph produced will be directed showing the direction of the relationship. If the foreign keys are intuited via natural joins, the graph will be undirected.
Clustering of tables allows you to group and box tables according to function or domain or whatever criteria you choose. The syntax for clustering tables is:
cluster1=table1,table2;cluster2=table3,table4Releases
10 releases since Debian 4.0 (Etch); the text changed 9 times.