Thank you for your feedback.
Generally, the outcome you describe with the workflow from your last message is the expected one - OpenAccess ORM will not generate a script that sets the nullability of a primary key
database column to False
. Moreover, a validation error regarding this setup will appear in Error List
(more about our Validation Framework
is available here
). Additionally, in the context of generating a script that changes the nullability in the database, the states of the logging
and the Allow table removal
properties are not relevant.
In fact, the domain models generated with OpenAccess ORM
are logically split in two parts: a conceptual model
and a storage model
. The conceptual model is the abstract specification for the persistent classes, the complex types and the associations - the schema you see in Visual Designer
. The storage model defines the underlying tables, columns, stored procedures, foreign keys and indexes - you can see it when you open the model in Visual Designer
and select Model Schema Explorer
In other words, in order to change the nullability you need to set Nullable
in Visual Designer
for the property and to check the Allow nulls
check-boxt in Table Editor
is an article that demonstrates the process. After applying the necessary modifications you can save the domain model and run the Update Database From Model
I hope you find this feasible. If you need further assistence, do not hesitate to get back to us.
OpenAccess ORM Q3 2013 simplifies your model operations even further providing you with greater flexibility. Check out the list of new features
shipped with our latest release!