Some conflicts with foreign key?

Thread is closed for posting
2 posts, 0 answers
  1. Jürgen
    Jürgen avatar
    11 posts
    Member since:
    Aug 2010

    Posted 03 Oct 2011 Link to this post

    Hello Telerik.
    I have such Entity structure:
    I have an Entity [Workstation] - it is a one PC.
    For each [Workstation] (PC) user can connect some devices - Entity [Device]
    The list of devices is Entity [DeviceConfiguration]
    Each [DeviceConfiguration] "knows" for what Workstation it was created.
    And each [Workstation] can contains many [DeviceConfiguration].
    And for [Workstation] it is possible to select  DefaultDeviceConfig
    public class Workstation 
      public string Name { get; set; } 
      // ... 
      public DeviceConfig DefaultDeviceConfig { get; set; } 
    public class DeviceConfig 
      public string Name { get; set; } 
      / ...
      public IList<Device> DeviceList
      public Workstation DeviceWorkstation { get; set; } 
    public class Device
      public string Name { get; set; }
      // ...
    but when I use mapping to create/update my DB - I can't see foreign keys in tables [Workstation] and [DeviceConfig]
    I expect that for properties DefaultDeviceConfig and DeviceWorkstation were created 2 foreign keys.
    But - not!
    Why? Is it some conflicts with crossreference?
    But in IBExpert I can create these constraints by manual. Why not by mapping?
  2. Ivailo
    Ivailo avatar
    318 posts

    Posted 06 Oct 2011 Link to this post

    Hi Jürgen,

    If you are using the official Q2 2011 release - assembly version 2011.2.713, then this is a known issue in our forward mapping. Can you update to our latest stable build (2011.2.908.1) and try again?

    Do not hesitate to get back to us if you have any issues.

    the Telerik team

    Thank you for being the most amazing .NET community! Your unfailing support is what helps us charge forward! We'd appreciate your vote for Telerik in this year's SQL Server Community Awards. We are competing in TWO categories and every vote counts! VOTE for Telerik NOW >>

Back to Top