I spoke to one of the maintainers of SQL::Translator and after a suggestion from him I arrived at the following which avoids the problem above:
my $translator = SQL::Translator->new( from => 'DBI', to => 'GraphViz', parser_args => { dsn => "dbi:Oracle:xxx", db_user => 'xxx', db_password => 'xxx', producer_args => { output_type => 'png', out_file => 'out.png', natural_join => 1, width => 30.0, height => 30.0, #fontsize => 10 }, }, ); my $sql = $translator->translate( data => '');
unfortunately our schema is quite large and the above produces a png which although looks like it might be correct is unreadable - everything is too small. The png output is limited in size apparently. I tried generating a postscript file as well but I don't seem to be able to produce one of those - nothing is output. Maybe I don't have whatever GraphViz needs to generate postscript.
In reply to Re^4: Dancer + SQL::Translator
by mje
in thread Dancer + SQL::Translator
by jeffa
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |