Thank you for the detailed information.
Generally, the described representation is the expected one for OpenAccess ORM. According to our design, if the database model contains a table which consists of foreign keys only
, it will be mapped as a join table in the domain model and the association between the domain classes connected through it will be visualized
as a many-to-many association.
In the given case, you can achieve a more accurate representation of the domain model using the following steps:
1. Open the .rlinq file in Visual Designer
and go to Model Schema Explorer
2. In the Tables
node, select the RecordFile
table and press F4
to open its details in the Property window
3. Set IsJoinTable
and save the model
the RecordFile table on the surface of the designer to create a domain class for it
the initial many-to-many association and save the domain model
With that workflow you will make only visual changes in the model that will not lead to eventual changes in the storage model. You can verify that by starting the Update Database from Model
wizard and selecting Migrate Database
I hope you find that feasible. If you have additional questions or experience difficulties, do not hesitate to get back to us.
OpenAccess ORM Q2 2013 brings you a more powerful code generation and a unique Bulk Operations support with LINQ syntax. Check out the list of new functionality and improvements shipped with this release.