Navigation Property Naming Convention

2 posts, 0 answers
  1. Matthew
    Matthew avatar
    13 posts
    Member since:
    Aug 2010

    Posted 21 Aug 2013 Link to this post

    Is there a way to set the naming convention for the Navigation Property for Source End and Target End?  For instance:

    Table Name: Transaction
    id_Transaction
    FK_Warehouse_From
    FK_Warehouse_To
    Quantity

    Table Name: Warehouse
    id_Warehouse
    Name

    So a transaction record has two foreign keys to warehouse entries, and the in the Association Editor you can see the "Source End (Navigation Property)" defaults to "warehouse" and "Target End (Navigation Property)" defaults to "transactions" for FK_Warehouse_To, and FK_Warehouse_From has "warehouse1" for its Source End and "transactions1" for its Target End.  Is there anyway to set a naming convention in the design wizard or programmatically setting the naming?  The Open Access ORM is building from a MySQL database, are the navigation property names somehow pulled from a setting from the database?

    Any help would be greatly appreciated.  Thanks.
  2. Boris Georgiev
    Admin
    Boris Georgiev avatar
    190 posts

    Posted 26 Aug 2013 Link to this post

    Hi Matthew,

    The navigation properties are generated by Telerik OpenAccess ORM and their names are based on the Domain Classes on the other side of the association in which they attend. At the moment the only way to change the navigation property names is to open the association in the Association Editor and to edit the navigation property name. 
     
    Additionally, there is a Feature Request, to enhance the Navigation Property name generator, in our Ideas and Feedback Portal. If you feel that you would like to add something to the description - post a comment to the item. 

    This feature is in our backlog list and we will implement it for the next official release of OpenAccess - Q3 2013, expected in the end of October. 

    If you have any further questions, do not hesitate to contact us again.

    Regards,
    Boris Georgiev
    Telerik
    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.
  3. DevCraft banner
Back to Top