ATK Relations: Difference between revisions

Latest revision as of 10:44, 8 March 2010

A relation defines a relation between two tables. One or more records in the first table belong to one or more records in the second table. A one to many relation would be '1 library has N books'. Below is a list of the relations that are currently available in ATK.

Relation	Description	Screenshot
atkOneToOneRelation	'A person has one address'
atkOneToManyRelation	'A department has many employees'
atkManyToOneRelation	'A project has a projectleader (that can lead multiple projects)'
atkManyToManyRelation	'A shopper buys multiple products, a product can be bought by multiple shoppers'
atkManyToManySelectRelation	'A shopper buys multiple products, a product can be bought by multiple shoppers'
atkManyBoolRelation	'An article has several categories, indicated with checkboxes'
atkManyToOneTreeRelation	'A category has a parent category'
atkMatrixRelation	'In a project, phases x and y depend on phases a and b'
atkSecureRelation	'A patient has personal information, that must be secured'
atkShuttleRelation	'An operator operates in several countries, selected from a list'
atkExtendableShuttleRelation	'An operator operates in several countries, selected from a list which can be filtered'

Relations behave similar to Attributes (in fact, relationships are nothing more then special attributes).

@@ Line 1: / Line 1: @@
 A relation defines a relation between two tables. One or more records in the first table belong to one or more records in the second table. A one to many relation would be '1 library has N books'. Below is a list of the relations that are currently available in ATK.
-* [[atkOneToOneRelation]] - 'A person has one address'
+{| border=1 cellpadding=5
-* [[atkOneToManyRelation]] - 'A department has many employees'
+ |- style="background-color: #FFFACD;"
-* [[atkManyToOneRelation]] - 'A project has a projectleader (that can lead multiple projects)'
+ ! Relation || Description || Screenshot
-* [[atkManyToManyRelation]] - 'A shopper buys multiple products, a product can be bought by multiple shoppers'
+ |-
+ | [[atkOneToOneRelation]] || 'A person has one address' ||
+ |-
+ | [[atkOneToManyRelation]] || 'A department has many employees' || [[Image:atkOneToManyRelation.png]]
+ |-
+ | [[atkManyToOneRelation]] || 'A project has a projectleader (that can lead multiple projects)' || [[Image:atkManyToOneRelation.png]]
+ |-
+ | [[atkManyToManyRelation]] || 'A shopper buys multiple products, a product can be bought by multiple shoppers' ||
+ |-
+ | [[atkManyToManySelectRelation]] || 'A shopper buys multiple products, a product can be bought by multiple shoppers' ||
+ |-
+ | [[atkManyBoolRelation]] || 'An article has several categories, indicated with checkboxes' || [[Image:atkManyBoolRelation.png]]
+ |-
+ | [[atkManyToOneTreeRelation]] || 'A category has a parent category' || [[Image:atkManyToOneTreeRelation.png]]
+ |-
+ | [[atkMatrixRelation]] || 'In a project, phases x and y depend on phases a and b' ||
+ |-
+ | [[atkSecureRelation]] || 'A patient has personal information, that must be secured' ||
+ |-
+ | [[atkShuttleRelation]] || 'An operator operates in several countries, selected from a list' || [[Image:atkShuttleRelation.png]]
+ |-
+ | [[atkExtendableShuttleRelation]] || 'An operator operates in several countries, selected from a list which can be filtered' ||
+ |}
-==atkManyBoolRelation==
+Relations behave similar to [[Attributes]] (in fact, relationships are nothing more then special attributes).
-Document me!
-==atkManyToOneTreeRelation==
-The atkManyToOneTree relation will build a dropdown that looks like:
- Record A
-   Record B
-   Record C
-      Record D
-      Record E
- Record F
-It could be used together with [[atkTreeNode]] with [[ATK_Attribute_Flags|AF_PARENT]].
-==atkMatrixRelation==
-The atkMatrixRelation is no longer maintained and probably does not work. Over the years that ATK has existed, there haven't been many uses for the atkMatrixRelation.
-==atkSecureRelation==
-Document me!
-==atkShuttleRelation==
-Document me!