MetaForeignKeyAssociation: Target member is not an identity member...

Thread is closed for posting
7 posts, 1 answers
  1. Scott
    Scott avatar
    68 posts
    Member since:
    Nov 2011

    Posted 21 Dec 2011 Link to this post

    When will this be supported? See attached screenshot of error...
  2. Answer
    Zoran avatar
    534 posts

    Posted 23 Dec 2011 Link to this post

    Hello Scott,

     We have added this to our TODO list for our future versions. Since it requires major development in some core parts of our product, we have scheduled it for Q2 2012 together with some other major refactorings for the runtime handling of associations. This however is not absolute and final time-frame for the delivery of this feature as depending on the development cycle by then it could be implemented sooner or later than expected. It is a time-frame that you can have as orientation about when the feature will be released.

    All the best,
    the Telerik team

    Q3’11 of Telerik OpenAccess ORM is available for download. Register for the What's New in Data Tools webinar to see what's new and get a chance to WIN A FREE LICENSE!

  3. Scott
    Scott avatar
    68 posts
    Member since:
    Nov 2011

    Posted 10 Mar 2012 Link to this post

  4. Christopher
    Christopher avatar
    1 posts
    Member since:
    Dec 2012

    Posted 03 Jan 2013 Link to this post

    What is the status of this? A typical schema in my database is a one to many with foreign keys in the many table.

    e.g. Customers have many addresses hence the CustomerId is in the Address table.

    Without this feature I can't use OpenAccess.
  5. Ivailo
    Ivailo avatar
    318 posts

    Posted 07 Jan 2013 Link to this post

    Hi Christopher,

    Thank you for your interest in Telerik OpenAccess ORM.

    In your scenario, if the CustomerId that is located in the Address table is pointing to a column in Customers table that is a primary key, you should not have any problems using Telerik OpenAccess ORM. 

    The limitation that was discussed in this thread, and still remains in the product, is about a foreign key that is pointing to a unique constraint column that is not a primary key. For example a CustomerId that is linked with an Id column in the Customer table, but that Id column is not a primary key for the Customers table. In all other cases you will be able to create an association easily.

    For more information about associations in OpenAccess ORM, you can check this documentation section.

    I would also recommend you to download and use the OpenAccess SDK application, which includes a lot of useful sample projects using OpenAccess ORM - that is the fastest way to get an idea about how the product is used and what are the main benefits. Also you can see some of the introductory videos on Telerik TV.

    Let us know if you have any other questions.

    the Telerik team
    Q3'12 SP1 of OpenAccess ORM packs Multi-Table Entities mapping support. Check it out.
  6. Jason
    Jason avatar
    1 posts
    Member since:
    Apr 2014

    Posted 17 Jul 2014 in reply to Ivailo Link to this post

    This exception is still being encountered in Q3 2014. Has this at all been or scheduled to be addressed since the last post in Q1 2013? This would be a big help when dealing with third party databases where you have no control over the schema.
  7. Kristian Nikolov
    Kristian Nikolov avatar
    206 posts

    Posted 21 Jul 2014 Link to this post

    Hi Jason,

    Indeed, Telerik Data Access does not currently support scenarios where a relation is defined between a Foreign Key and a Unique column. Adding support for such scenarios would be a completely new feature of the product. Therefore we have an existing feature request about this functionality. We would like to invite you to vote for it at our Feedback Portal. Doing so will help us prioritize its eventual implementation.

    I hope this helps. Should you have additional questions, feel free to post at our forums again.

    Kristian Nikolov
    OpenAccess ORM is now Telerik Data Access. For more information on the new names, please, check out the Telerik Product Map.
Back to Top