 |
 |
 |
Modeling: User's Guide |  |
 |
|
| Prop. | Type | Default | Comment |
|---|---|---|---|
name |
string |
no default | The name is the first
mandatory argument when instanciating a BaseRelationship. Once set, it
should not be changed |
destination |
string |
no default | The destination
entity's name is the second mandatory argument when instanciating a
BaseRelationship. Once set, it should not be changed |
delete |
string |
'nullify' |
|
isClassProperty |
int |
1 | |
multiplicity |
sequence | [0,1] |
|
joinSemantic |
int |
0 | see below |
src |
string |
'' |
source attr.'s name |
dst |
string |
'' |
destination attr.'s names |
displayLabel |
string |
'' |
|
doc |
string |
'' |
|
inverse |
string |
'' |
a valid relationship's name in the destination entity -see 2.4.7, ''Inverse relationships'' for a full discussion. |
You'll never need to use a BaseRelationship; in fact, it's not even legal in a PyModel. Instead, you'll declare RToOne (2.4.7) and RToMany (2.4.7) objects; or even better, you'll use Association (2.4.8) objects to create both a relationship and its inverse in a single declaration.
We presented it here because all three element RToOne, RToMany and Association use the BaseRelationship's defaults for their own defaults (and override some of them).
The possible values for the attribute joinSemantic, and their respective
meaning are:
0: Inner join
1: Full outer join
2: Left outer join
3: Right outer join
|
|
|
Modeling: User's Guide | |
|
|