The ORM Foundation

  I love modelling stuff with ORM. I often find myself visiting these forums, looking for something I can hone my modelling skills on, posting a diagram of what I think the poster described.  The forums aren't all that lively, currently. It seems a good portion of the posts tend to follow the pattern of "I see This, ...

 This sounds exciting!  One of the greatest troubles I've had in getting ORM some greater traction is the barrier of needing to have Visual Studio to really browse the diagrams.  The HTML report feature outputs the info, true, but not quite as well as actually poking around in th diagram. A web-based diagram tool, even a ...

Quite often, this kind of information is specific to a given table, and not directly related to any Entity. Indirectly related, yes, since often an entity maps into a table. If it is the case that you'd want one of these logging records on any table, regardless of why the table is there, then it wouldn't make much sense to have it at a ...

 Ah, that's right! "Entry has Pennant that is of Colour" probably is not an elementary fact type!  When building that diagram, I made the assumption that a pennant might be reused in the next cat show. The constraint over the Pennant and Colour roles was meant to keep the pennants colour from changing from one show to the ...

 Peter,   An interesting scenario! Yes, the verbalization on join constraints is not yet implemented. Perhaps there is another way to model it?  In this diagram, I've introduced the notion of an 'Entry'  - not sure if that would make sense in your universe of discourse. Hopefully, this still covers what is ...

Hi Evorobey. Perhaps I might chime in with something useful here. If I'm understanding you correctly, you're wanting to show the objectified fact type in a new diagram, and don't want it to just be a set of boxes in a circle.   All you need do is to also add the entities involved in the objectified fact type in the new diagram ...

 Recently, I added a one to one relationship between two entities, non-mandatory on both sides.  Fortunately for me, it maps out the way I want it to - absorbing the role with a rolename. But if it had not, and I wanted to change it, is there anything I could do? (beyond deleting the fact type and adding it again, hoping that things land ...

 That's an interesting way of going about it. I think an important factor in this would be the subtype definition - how do you determine what makes a SalaryAdjustment an InitialSalaryAdjustment, and what makes it a SubsequentSalaryAdjustment? Would you want to add a constraint showing that it must be one or the other, and not ...

Currently, I'm using ORM to model the vast structure used for the US medicaid system. The number of diagram tabs I have is rather large. This model represents data that will be stored using about two dozen different physical database models It would be helpful if there were some way to select only a subset of the diagrams, and create a new ...