This question is locked. New answers and comments are not allowed.
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
but when I use mapping to create/update my DB - I can't see foreign keys in tables [
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?
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
[Persistent]
public
class
Workstation
{
public
string
Name {
get
;
set
; }
// ...
public
DeviceConfig DefaultDeviceConfig {
get
;
set
; }
}
[Persistent]
public
class
DeviceConfig
{
public
string
Name {
get
;
set
; }
/ ...
public
IList<Device> DeviceList
public
Workstation DeviceWorkstation {
get
;
set
; }
}
[Persistent]
public
class
Device
{
public
string
Name {
get
;
set
; }
// ...
}
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?