Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris

Re: Dancer + SQL::Translator

by mje (Curate)
on Mar 27, 2012 at 14:03 UTC ( #961935=note: print w/replies, xml ) Need Help??

in reply to Dancer + SQL::Translator

Thanks for the reminder about SQL::Translator. I added a call to "dance;" at the end to run it from the command line directly, changed the DSN etc to point at our Oracle db and I changed those "MySQL"s to "Oracle". Unfortunately, although the SQL is generated the png generation failed for me immediately with xxx:

ERROR (line 9): Invalid statement: Was expecting remark, or run, or pr +ompt, or create, or table comment, or comment on table, or comment on + column, or alter, or drop

and leaving MySQL in with:

ERROR (line 789): Invalid constraint: Was expecting primary key def, o +r unique key def, or foreign key def

The generated SQL in both cases looks ok as far as I can tell but the line number reported seems to bear no relationship to the SQL at that line number. :-(

Obviously the same happens with sqlt-graph.

BTW, I thought GraphViz was deprecated in favour of Graphviz2.

Replies are listed 'Best First'.
Re^2: Dancer + SQL::Translator
by jeffa (Bishop) on Mar 27, 2012 at 15:31 UTC

    I saw that error creep up many times when i was trying to put this together. Looks like more will be necessary than simply replacing the name of the database vendor/driver. Take a look at the value for $sql and see what part(s) are invalid for Oracle. As for GraphViz2, normally i would jump up to upgrade but in this case i just need something quick and dirty to help me visualize my problem that needs to be solved. Thanks for your time. :)


    (the triplet paradiddle with high-hat)

      It is the double bracketed values in the timestamp definition.

      CREATE TABLE "ACCOUNT" ( "ACCOUNT_ID" number(38) NOT NULL, "DATE_TIME_UTC" timestamp(6)(11), "CURRENCY_ID" number(38) NOT NULL, "NAME" varchar2(128) NOT NULL, "BALANCE" number(14) NOT NULL, "ACCOUNT_TYPE_ID" number(38) NOT NULL, "CREATED_BY_USER" varchar2(128), "CREATED_DATE_TIME_UTC" timestamp(6)(11), "MODIFIED_BY_USER" varchar2(128), "MODIFIED_DATE_TIME_UTC" timestamp(6)(11) );

      When the table was originally created those columns were only timestamps with no precision.

        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.

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://961935]
and the shadows deepen...

How do I use this? | Other CB clients
Other Users?
Others perusing the Monastery: (8)
As of 2018-06-22 22:00 GMT
Find Nodes?
    Voting Booth?
    Should cpanminus be part of the standard Perl release?

    Results (124 votes). Check out past polls.