You searched for the word(s): 5
Well, "fate", which smiled upon you, has indeed played some funny games with version 18: I just discovered that the final version of the unary f.t. shape did not find its way into version 18, somehow. This has now precipitated version 20.
BugsSure no problem. I've attached two images showing the difference. Upon a bit of further testing I noticed that when I first open the ConstraintValidationReport.html page in IE, the gold underline (border-bottom property) for .topHeader is not visible, the header for the page is not visible and "Fact Type" is not visible either. ...
The checkboxes are directed more toward a validated printout than online. This is a static html page at this point after all, so there is no tracking of the checks.
As for the bugs:
Could you be a little more specific? They look the same to me.
This is a problem with the .topHeader style, which needs an overflow:hidden
I’ve been attempting to reverse engineer object role models into Visio UML diagrams by using Visual Studio 2010 Ultimate.
I have been successful in reverse engineering a very simple object role model based around the proposition “Person buys Car”, which I have attached to this post. However when I attempt to repeat the procedure for more ...
Hi Matt, I have a few queries/bug reports regarding the NORMA generated HTML report.
In the ConstraintValidationReport, why is there a checkbox for each constraint? I assume this may be something to do with showing the report to a client so that they can agree or disagree with the propositions made by checking or unchecking a checkbox. If ...
This is a bug in the relational display code. For the raw data types, length is not supported for Picture or Ole Object raw data types, but the relational display code was not ignoring the value for these two types.
This will be fixed in the next NORMA release.
Thanks for the bug,
Interesting scenario. Unary fact types are currently stored in a binarized form which is revalidated on load. If the form doesn't match (including the required boolean data type) then the unary-ness of the fact type is abandoned and you get a binary fact type with a missing role player, as you see.
Relational columns do not have ...
When mapping a unary fact type to a relational view, a column is created with a logical True/False data type. When this model is exported to Oracle a column with NCHAR(1) is created.
I prefer to use numeric data types in Oracle for boolean values, 0 for false and 1 for true, so in the relational view I tried to assign a numeric data type to ...
Believe it or not, I was not the first one to down load it. I have been working on other projects and have not yet taken the time to install it--but it looks like fate smiled upon me :)
If you were the first to download version 18, would you please re-download? Since that download, I found and fixed a bug in the code that re-glues connections made to the (nested) entity types. My apologies for this, I thought it would be better to go ahead and fix this and re-upload as version 18, rather than make a new ...