The ORM Foundation

Get the facts!


Page 1 of 40 (396 items) 1 2 3 4 5 Next > ... Last »
  • Re: RE: The specified invariant name is not supported

    Hi Karl, I've checked in the code provided in this thread by Jose Carlus (whom I owe a huge belated thank you). I have not tested this, and I think you're running a different driver version, but it is definitely worth a try. The database import assembly needs to be installed in the GAC or VS won't open it, ...
    Posted to Technical support (Forum) by Matthew Curland on 04-18-2014
  • Re: Syntax highlighting no longer working in ORM fact editor

    Hi Karl, Getting editor colors to work got significantly harder for the VS2012 release. It sounds like something is off in your color settings, but I don't verify the colors are properly registered because it is already flagged in the registry as being checked for this NORMA version, meaning that it won't recheck until you install a ...
    Posted to Technical support (Forum) by Matthew Curland on 04-18-2014
  • Re: Why extra tables in relational view if not declared independent?

    Hi Gordon, This is related to Other Features #6 in the Dec 2013 readme notes: Entity type subtypes with an auto counter data type can no longer be absorbed into the parent table. Similarly, no entity type identified by an autocounter can be created without its own table. The default data type for the .id reference mode is Autocounter, so ...
    Posted to Contributed Models (Forum) by Matthew Curland on 04-02-2014
  • Re: Generated constraint names

    Hi Maurice, There is no way to specify this in NORMA right now. This has to be done somewhat carefully as one value type can map to multiple columns, so (like value constraints) a distinction between a 'default value' on the role vs. one on the value type vs one on the data type would need to be made. At the XSL level, we currently go ...
    Posted to NORMA (Forum) by Matthew Curland on 03-31-2014
  • Re: Generated constraint names

    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 ...
    Posted to NORMA (Forum) by Matthew Curland on 03-31-2014
  • Re: Objectification in the latest NORMA update

    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 ...
    Posted to NORMA (Forum) by Matthew Curland on 03-22-2014
  • Re: What is a fact?

    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 ...
    Posted to Philosophy (Forum) by Matthew Curland on 03-20-2014
  • Re: Population validation on a join subset constraint

    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 ...
    Posted to NORMA (Forum) by Matthew Curland on 02-14-2014
  • Re: Value comparison constraint

    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 ...
    Posted to Technical support (Forum) by Matthew Curland on 02-11-2014
  • Re: Visual Studio Versions for NORMA

    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 ...
    Posted to NORMA (Forum) by Matthew Curland on 02-10-2014
Page 1 of 40 (396 items) 1 2 3 4 5 Next > ... Last »
© 2008-2014 The ORM Foundation: A UK not-for-profit organisation -------------- Terms of Service