Today I have been mainly playing with the SQL Fairy (aka SQL::Translator).
After watching it install about half of CPAN are prerequisites and finally being galvanised into going thru the pain of installing libgd and GD.pm I finally got to try it out. And it seems like a pretty useful piece of code. It translates SQL DDL between various storage formats. That might be actual DDL code (in various dialects) or perhaps XML or YAML. It'll even have a good stab at drawing a picture of your database (that's what it needs GD for).
I'll be adding it to my standard toolbox.
Re:common
dha on 2004-02-02T19:29:15
Wow. That's exactly what I was thinking.
I'm frightened.
[cowers in corner]
Well, we've tried hard not to recreate any
wheels unless we really have to.
Would you rather we wrote our own bitmap output
library?
Re:Half of CPAN
jhi on 2004-02-02T19:31:16
> Well, we've tried hard not to recreate any wheels unless we really have to
But if you end up pulling in the annual combined output of Goodyear and Michelin?
What I would like to see is better composability (and therefore decomposability) of modules, so that one pulls in only the parts one is really using.
Re:Half of CPAN
TeeJay on 2004-02-17T10:21:32
I manage to only require a handful of modules in Autodia and acheive much the same result.Of course I still need to munge the Makefile some more to make it interactively ask if it should install $module if the user wants / needs it for something.
Autodia has been doing Database Diagrams (from DDL/SQL or DBI and even Druid XML) for yonks. Hopefully I can add the new pureperl directed graph module as an alternative to GraphViz.
If you have databases in Dia you might want to check out tedia2sql which handles multiple databases rather nicely (in a handful of modules)
Schemamania is quite cool too.
I can't remember the links off hand but you can find them on the autodia site in the links page.
Not to knock SQL Fairy - it looks damned useful, and I hope to nick some ideas^W^W^Wfind some inspiration from it
:)
