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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Hiding the database details from you is the major feature of Tangram. If you want closer access to the database, you should look at Class::DBI or SPOPS.

    Beware of hubris about Tangram -- it does a lot of tricky perl magic in order to provide almost invisible persistence. It is not easy to build something like that.

    • I'm not after hiding stuff - I am after automating stuff - there is an important difference. When something is automated I can still see what is going on - critical in any system AFAIK.

      The schema and other bits of database behind tangram aren't anything special.

      --

      @JAPH = qw(Hacker Perl Another Just);
      print reverse @JAPH;
      • If you're not after hiding stuff, then Tangram is the wrong tool for you. Hiding stuff is most of the point of Tangram.

        The schema that Tangram generates is simple, but handling the query language and doing all the TIE and proxying in order to make things like arrays work is quite complex.