The ORM Foundation

Hi Maurice, NORMA current maps the table and column names, but not all of the constraints names. The issue that we basically have three kinds of elements: Items that are represented in the in-memory version of the relational model. These should use the naming conventions if they are specified. Items that are named in the ORM model ...

Hello Piotr, Starting with this release NORMA actually verifies that each expanded reading in your model correspond to exactly one fact type. By an expanded reading, I mean a reading with a normalized form (object type names are broken into pieces over camel casing, hyphens are removed, etc.). I called this expanded form a reading signature, and ...

Hello Niels, Thanks for a great example of why a lexical representation of a value is not the value itself. I've never liked the NIAM-era notion of LOT vs. NLOT (Lexical Object Type vs Non-Lexical Object Type), which evolved into Value Type and Entity Type in ORM. The problem is that the focus is on the wrong thing, namely a lexical ...

I'm not in a position to comment on any recent Doctool versions as it has been close to a decade since I touched a new version, but I am familiar with the approach. There is certainly a stronger emphasis on sample population as the whole system focuses on the lexical level. The system does not use ORM object types at all. The primary ...

Hi Karl, It isn't that the simpler case doesn't have a join path. NORMA just creates the join path automatically in the simple case. You'll see a join path for this constraint if you look at the .ORM file in an XML editor. The harder case actually has three possibilities. I'm assuming you want to join over both Person and ...

The only difference in functionality is an additional class generator supported in VS2008 (and later) versions. Windows added multi monitor support around 1998, and VS had full support by VB6 (before it was even called VS). I even remember fixing a multi-monitor Intellisense bug in that timeframe. [The original Intellisense implementation would ...

Hi Karl, I'll confirm this as a bug with populations across mandatory constraints on different subtypes. I fixed some related cases in the last round (mentioned in bug fix item 2 in the Dec 2013 readme), but apparently I have more work to do. This is an issue with incremental validation not recognizing that instances of the 'other' ...

Hi Karl, An exclusive or constraint is actually two constraints linked together for convenience in the object model and diagram. These are always handled separately in the logic engine. There is a context menu command to split the constraints (Split Exclusive Or Constraint) and another to recombine them. Constraint names are unique across a ...

Hi Karl, That's an interesting perspective. Glancing at the code, we do a TranslateTransform on the graphics object used to generate the image, but I don't see any graphics.ScaleTransform. If I can get a reasonable quality image with some tweaks to the graphics object then I can break Copy Image into three items (copy at default ...

Sorry,  José, I haven't done any work in this area. This comes down to writing a file for Oracle that is similar to http://sourceforge.net/p/orm/code/HEAD/tree/trunk/Tools/DatabaseImport/SqlServer2005DcilSchemaProvider.cs and plugging it into the GetDcilSchemaProvider method in DcilObjectModel.cs in the same directory. I ...