All the Perl that's Practical to Extract and Report

Navigation

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Without JavaScript enabled, you might want to
use the classic discussion system instead. If you login, you can remember this preference.

Please Log In to Continue

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

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 th

Multiple inheritance in Tangram works fine. What doesn't work is empty intermediate classes. I got burnt by the same "bug" you experienced, and found that it was simply due to the fact that I had an "organizational" superclass with no actual attributes. A little class rearrangement and everything was OK.