Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Maypole 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Did you say you've got a web app that generates Maypole applcations??? Please, tell all.

    Bill

    --
    Bill
    # I had a sig when sigs were cool
    use Sig;
    • Well, I'm on the way to having that. It's certainly what I'm aiming for.

      Once it's finished I'll be very happy to share as much of it as a) is generally useful and b) the Powers That Be here allow me to share.

      But it's actually not that complex. You have an application where the objects in the database are applications, entities (that belong to an application), attributes (that belong to entities) and relationships (between entities).

      You then write a script that queries this database and finds all of the entities, attributes and relationships for a given application. You can then use this data to create database tables and Maypole classes that support the app. Of course, that's where all the magic is and that's what I'm currently trying to get working. It's tantalisingly close right now.

      It's all a bit of a trip back in time for me. My first job when I got my degree was working on a CASE tool (anyone else old enough to remember case tools?) I was working on the data modelling part of the system so we had a database that modelled entity-relationship diagrams and a program that used that data to generate SQL DDL. I'm dredging out all of that old knowledge for this project.
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.