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.

Tangram Inheritance problems 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • You're problem is just that Tangram takes over the database for you. It keeps a table that maps class names to table names so you never have to look that far down. It does cause an inheritance problem but I suspect that could be overcome, perhaps a 1-to-many relationship for class name aliases. I suspect it wouldn't be too horrible.

    Beware, though, creating your own mapper will drive you insane if you aren't careful. I don't use Tangram because I'm not willing to give up that much control. On the other end
    --
    Casey West
    • Tangram is just not ready for production use.

      The documentation is sparse, once you leave the trivial parts and it is hugely limiting.

      I wouldn't mind it hiding the complexity and details, if it let me choose to be able to at least see what was problematic and why it crashed.

      More error checking wouldn't go amiss either - failing to check that all the table aliases it refers to in a query are in there is a stupid loophole and the sql is generated so far from the query that its impossible to find where the problem occured - there ought to be some sanity checking in the sql generation.

      If there is another problem - like 2 or more deep inheritance it should complain rather than silently break.

      Bah!

      --

      @JAPH = qw(Hacker Perl Another Just);
      print reverse @JAPH;
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.