You searched for the word(s): 5
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 ...
Please note that version 18 of ORM2_Draw2 is up and available:
Here is an example of an equality constraint that I have taken from page 225 of Terry's book.
I would have thought that this constraint would generate some additional DDL but my tests show that the DDL is the same with and without the constraint. I have asked Matt to comment.
I'd like to know if an equality constraint in an ORM model has any effect over its relational view or if it only has an informational role.
I have a model which I've attached to this post. In the Asset_Movement table I'm getting two columns:
but these columns ...
Regarding " What might be helpful"?
It seems to me that it would be useful to add a "default value" field in the property sheet of each column of the relational model.
That way, you could set the default values during the modeling phase, rather than waiting until the physical DB had been generated.
Of course the ...
You made me laugh. I wasn't trying to overdo it, but I think I failed.
I think the fundamental issue is that on the conceptual side--which is just a first-order logic representation of the domain--there are only notions of true or false. The default value question issue is a question for the logical schema, not the conceptual ...