Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

TeeJay (2309)

  (email not shown publicly)

Working in Truro
Graduate with BSc (Hons) in Computer Systems and Networks
pm :,,
lug : Devon & Cornwall LUG
irc : TeeJay
skype : hashbangperl
livejournal : hashbangperl []
flickr :hashbangperl []

Journal of TeeJay (2309)

Thursday April 24, 2003
03:12 AM

Perl and SQL by numbers

[ #11819 ]
I have been talking to Tim Ellison of teDiaSQL fame, about integrating tediasql and autodia.

I don't think it would be that hard - the main changes would be..

  • Making the diagram object more generic so that it handles databases better (with more relevent method and attribute names too) and also can support the new Database Schema shapes being cooked up.
  • Adding Database objects representing relationships (one to many, etc), tables, etc.
  • Adding some configuration options.

That is probably going to take a while, especially if I want to add argouml output to autodia.

Another thing I really want to do is build a tool for generating perl skeleton code based on common patterns, idioms and good practice.

It would do things like generate SQL to create tables, build SQL phrase books, use common modules to provide Object Persistance and/or Database abstraction, and be run from either UML or some kind of interactive GUI.

I suppose it should also generate tests and maybe Package using PAR or something. Possibly even Apache config directives - I mean none of these things are hard in themselves but a tool that automates them all easily would be very useful for design and prototyping and seems the natural partner to autodia.

Simon Cozens article at gives some perspective on this, so I plan to read through that and hopefully find some modules that can do some of the legwork for me.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.