sql::translator::producer::diauml(3pm) [debian man page]
SQL::Translator::Producer::DiaUml(3pm) User Contributed Perl Documentation SQL::Translator::Producer::DiaUml(3pm)NAME
SQL::Translator::Producer::DiaUml -
Produces dia UML diagrams from schema.
SYNOPSIS
use SQL::Translator;
my $translator = SQL::Translator->new(
from => 'MySQL',
filename => 'foo_schema.sql',
to => 'DiaUml',
);
print $translator->translate;
DESCRIPTION
Currently you will get one class (with the a table stereotype) generated per table in the schema. The fields are added as attributes of the
classes and their datatypes set. It doesn't currently set any of the relationships. It doesn't do any layout, all the classses are in one
big stack. However it is still useful as you can use the layout tools in Dia to automatically arrange them horizontally or vertically.
Producer Args
AUTHOR
Mark Addison <grommit@users.sourceforge.net>.
TODO
* Add the foriegn keys from the schema as UML relations.
* Layout the classes.
SEE ALSO
SQL::Translator.
perl v5.14.2 2012-01-18 SQL::Translator::Producer::DiaUml(3pm)
Check Out this Related Man Page
SQL::Translator::Parser::DBIx::Class(3) User Contributed Perl Documentation SQL::Translator::Parser::DBIx::Class(3)NAME
SQL::Translator::Parser::DBIx::Class - Create a SQL::Translator schema from a DBIx::Class::Schema instance
SYNOPSIS
## Via DBIx::Class
use MyApp::Schema;
my $schema = MyApp::Schema->connect("dbi:SQLite:something.db");
$schema->create_ddl_dir();
## or
$schema->deploy();
## Standalone
use MyApp::Schema;
use SQL::Translator;
my $schema = MyApp::Schema->connect;
my $trans = SQL::Translator->new (
parser => 'SQL::Translator::Parser::DBIx::Class',
parser_args => {
dbic_schema => $schema,
add_fk_index => 0,
sources => [qw/
Artist
CD
/],
},
producer => 'SQLite',
) or die SQL::Translator->error;
my $out = $trans->translate() or die $trans->error;
DESCRIPTION
This class requires SQL::Translator installed to work.
"SQL::Translator::Parser::DBIx::Class" reads a DBIx::Class schema, interrogates the columns, and stuffs it all in an $sqlt_schema object.
Its primary use is in deploying database layouts described as a set of DBIx::Class classes, to a database. To do this, see "deploy" in
DBIx::Class::Schema.
This can also be achieved by having DBIx::Class export the schema as a set of SQL files ready for import into your database, or passed to
other machines that need to have your application installed but don't have SQL::Translator installed. To do this see "create_ddl_dir" in
DBIx::Class::Schema.
PARSER OPTIONS
dbic_schema
The DBIx::Class schema (either an instance or a class name) to be parsed. This argument is in fact optional - instead one can supply it
later at translation time as an argument to "translate" in SQL::Translator. In other words both of the following invocations are valid and
will produce conceptually identical output:
my $yaml = SQL::Translator->new(
parser => 'SQL::Translator::Parser::DBIx::Class',
parser_args => {
dbic_schema => $schema,
},
producer => 'SQL::Translator::Producer::YAML',
)->translate;
my $yaml = SQL::Translator->new(
parser => 'SQL::Translator::Parser::DBIx::Class',
producer => 'SQL::Translator::Producer::YAML',
)->translate(data => $schema);
add_fk_index
Create an index for each foreign key. Enabled by default, as having indexed foreign key columns is normally the sensible thing to do.
sources
Arguments: @class_names
Limit the amount of parsed sources by supplying an explicit list of source names.
SEE ALSO
SQL::Translator, DBIx::Class::Schema
AUTHORS
See "CONTRIBUTORS" in DBIx::Class.
LICENSE
You may distribute this code under the same terms as Perl itself.
perl v5.18.2 2014-01-22 SQL::Translator::Parser::DBIx::Class(3)