[ROOT] / doc / DocFrag / ARCQuery.QueryProgress.OrderAndReconstructKeys
| Key | Value |
|---|---|
| Assembly | ARCQuery |
| DocFragType | ClassMember |
| IsInherited | -False- |
| IsInheritedDoc | -False- |
| Lines | -14- |
| Name | OrderAndReconstructKeys |
| Namespace | ARCQuery |
| Type | QueryProgress |
ClassMemberAttribute
| Key | Value |
|---|---|
| DeclaringType | QueryProgress |
| MethodName | OrderAndReconstructKeys |
| MethodSignature | System.Collections.Generic.List`1[ARCCore.IK] OrderAndReconstructKeys(System.Collections.Generic.List`1[ARCQuery.QueryExpression], System.String, System.Collections.Generic.List`1[ARCCore.IK]) |
Part 1:
Order keys either:
a) According to last QueryExpressionSelect, or (if no SELECT found)
b) Alphabetically.
Part 2:
Will also attempt to reconstruct keys to the more strongly typed PK- based on keys found for input parameter strCurrentType.
Because queries may be in multiple steps, the original strongly typed key may not be carried through the different QueryExpressions.
Example: For 'Customer/All', 'Customer/SELECT *', 'Customer/WHERE ...' we would have the original key already, because the query result will consist of the original (whole) Customer-objects.
But for a query like 'Customer/SELECT Name, Address' new temporary objects are created, usually with IKString as type.
The original PK is necessary in order for instance for PKHTMLAttribute to do its work.
WARNING: TimestampIsOld. Possible cause: API is currently initializing.
Generated 2025-10-30 04:05:16.417 UTC