The ORM Foundation

Yeah, you're correct about the conceptual modeling of objectifying "VersionedThirdPartyItem". I'll give that a go separately. Appologies for getting it wrong in my original post, the issue appears to be creating the objectified primary reference modes in the sample population editor for simple value types attached ...

 I have a ternary predicate that I've objectified to model Open Source usages by our internal projects.  "Project uses ThirdPartyItem version number Version" where Project and ThirdPartyItem are objects and Version is a value type.  Both Project and ThirdPartyItem have .Id reference modes. (that I've ...

After thinking about this some more. I'm becoming more convinced that a SQL Server IDENTITY and an Oracle SEQUENCE type really are two different conceptual data types and ought to be treated differently in the conceptual model. The huge difference between the two is simple: An IDENTITY MUST exist inside of an Independent Entity, while a ...

[quote user="Matthew Curland"]Hi Paul, good to hear from you. So, for a fact type, you'd see a submenu to pick the uniqueness patterns, with menus below each uniqueness pattern to choose the mandatory patterns (possibly up to n=5). The issue here is that each glyph in the menus needs to be hand-drawn for each pattern, and VS ...

[quote user="Matthew Curland"]Bill, We are not currently checking for multiple identity columns in relational tables. In fact, we currently don't do any datatype checking in the relational model in the tool (the datatype properties on the columns are smoke-and-mirrors that directly edit the underlying value types). Basically, the ...

Person isSmoker currently transforms into (more or less): BOOLEAN isSmoker isNullable at the relational level. Wouldn't the saner translation to relational be: BOOLEAN isSmoker !isNullable? Distinguishing between NULL implying false and 1 implying true for users of the relational model seems odd to me. Thanks, Bill

I was doing some fiddling with the ORM diagram discussed at: http://www.ormfoundation.org/forums/t/589.aspx when I noticed that the generated SQL Server output contained TWO colorID IDENTITY columns. This was clearly due to me using .ID as the reference mode instead of .code as in the linked discussion. However, shouldn't a validation error ...

Ah yes... The Virtual Tree Grid control. Some of the TFS Version Control UI in VS2k8 used that control.  I used the control to modify an internal visual diff tool to support TFS. (no, not windiff... :) ) An WPF improved version would be pretty cool if you ever get around to it. Don't you hate it when you're "around to it" ...

The US online store has a VS standard => Pro upgrade for  $299 at http://store.microsoft.com/microsoft/Visual-Studio-2010-Professional-Upgrade-for-Visual-Studio-Standard-Users/product/BE303EE9. Additionally, would an isolated shell approach be cheaper for end users? (If DSL designers can be hosted in an isolated shell... I tried looking ...