/ doc / toc / ARCQuery / Class / ForeignKey / IPRelationsKeysPointingTo

IPRelationsKeysPointingTo

Edit keys at this level only

Edit keys at all sub levels.
NOTE: Edits are always additive. Use 'Invalid' in order to delete keys.

__TOCDet/Assembly = ARCQuery
__TOCDet/Description = Contains, for each (entity type) key, a list of entity types with foreign keys pointing to that entity type.0x000D0x000A0x000D0x000AShows how all the -IP- classes relate to each other.0x000D0x000A0x000D0x000AUsed to automatically create links to related objects in a dynamic context.0x000D0x000A(see for instance -LinkInsertionInDocumentation- and -QueryExpressionRel-.)0x000D0x000A0x000D0x000ADepends on -AllIPDerivedTypes- (the static defined schema), that is does not attempt to dynamically discover any structures.0x000D0x000A0x000D0x000AKey is the very short string representations of the type (as generated from -ToStringVeryShort-)0x000D0x000AValue is List0x003C-EntityTypeAndKey-0x003E with corresponding types that refer to that type.0x000D0x000A0x000D0x000ASee also -EntityTypeAndKey-, -IPRelationsKeysPointingFrom- and -ForeignKeyDirection-.
__TOCDet/DocFragType = ClassMember
__TOCDet/IsInherited = False
__TOCDet/IsInheritedDoc = False
__TOCDet/Lines = 26
__TOCDet/LongDescription = Example:0x000D0x000A0x000D0x000AIf we have classes Customer, Order and SupportTicket and property keys OrderP.CustomerId and SupportTicketP.CustomerId then the entry for the key 'Customer' would be like   new List0x003CEntityTypeAndKey0x003E 0x007B "Order CustomerId", 'SupportTicket CustomerId' 0x007D.0x000D0x000A0x000D0x000AThis may be used to dynamically and automatically create links to related objects. For instance for context   'Customer/42' it will (with the help of this information) be possible to create corresponding links   'Order/WHERE CustomerId = 42' and   'SupportTicket/WHERE CustomerId = 42'.0x000D0x000A0x000D0x000ARelations defined with -PKRelAttribute- (-ForeignEntity-) is also taken into account.0x000D0x000AFor instance for Employee there might be a key EmployeeP.SupervisorId pointing to another Employee.0x000D0x000ATODO: Document use of -OppositeTerm- in such cases.0x000D0x000A0x000D0x000ANote that as of Jun 2020 this concept relies on predefined property keys (-PropertyKeyEnum-).0x000D0x000AThere is however in principle nothing wrong with dynamically finding the same information, as long as 'standardized' names are used for foreign keys, like 'Order/1968/CustomerId = Customer/42' for instance.0x000D0x000ATODO: Consider implementation of such a dynamic discovery.
__TOCDet/Name = IPRelationsKeysPointingTo
__TOCDet/Namespace = ARCQuery
__TOCDet/Type = ForeignKey
__TOCDet/Attribute/DeclaringType = ForeignKey
__TOCDet/Attribute/Description = Contains, for each (entity type) key, a list of entity types with foreign keys pointing to that entity type.0x000D0x000A0x000D0x000AShows how all the -IP- classes relate to each other.0x000D0x000A0x000D0x000AUsed to automatically create links to related objects in a dynamic context.0x000D0x000A(see for instance -LinkInsertionInDocumentation- and -QueryExpressionRel-.)0x000D0x000A0x000D0x000ADepends on -AllIPDerivedTypes- (the static defined schema), that is does not attempt to dynamically discover any structures.0x000D0x000A0x000D0x000AKey is the very short string representations of the type (as generated from -ToStringVeryShort-)0x000D0x000AValue is List0x003C-EntityTypeAndKey-0x003E with corresponding types that refer to that type.0x000D0x000A0x000D0x000ASee also -EntityTypeAndKey-, -IPRelationsKeysPointingFrom- and -ForeignKeyDirection-.
__TOCDet/Attribute/LongDescription = Example:0x000D0x000A0x000D0x000AIf we have classes Customer, Order and SupportTicket and property keys OrderP.CustomerId and SupportTicketP.CustomerId then the entry for the key 'Customer' would be like   new List0x003CEntityTypeAndKey0x003E 0x007B "Order CustomerId", 'SupportTicket CustomerId' 0x007D.0x000D0x000A0x000D0x000AThis may be used to dynamically and automatically create links to related objects. For instance for context   'Customer/42' it will (with the help of this information) be possible to create corresponding links   'Order/WHERE CustomerId = 42' and   'SupportTicket/WHERE CustomerId = 42'.0x000D0x000A0x000D0x000ARelations defined with -PKRelAttribute- (-ForeignEntity-) is also taken into account.0x000D0x000AFor instance for Employee there might be a key EmployeeP.SupervisorId pointing to another Employee.0x000D0x000ATODO: Document use of -OppositeTerm- in such cases.0x000D0x000A0x000D0x000ANote that as of Jun 2020 this concept relies on predefined property keys (-PropertyKeyEnum-).0x000D0x000AThere is however in principle nothing wrong with dynamically finding the same information, as long as 'standardized' names are used for foreign keys, like 'Order/1968/CustomerId = Customer/42' for instance.0x000D0x000ATODO: Consider implementation of such a dynamic discovery.
__TOCDet/Attribute/MethodName = IPRelationsKeysPointingTo
__TOCDet/Attribute/MethodSignature = ARCCore.IP IPRelationsKeysPointingTo

Edit single sub keys only: __TOCDet

Generated 2025-06-29 08:23:03.143 UTC