/ doc / tocInheritance / QueryExpression

QueryExpression

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 = Represents part of a query (or actually a transformation) against a given collection and the data storage from which it was taken.0x000D0x000A0x000D0x000AA series of queries are usually chained together in a fluent fashion0x000D0x000Afor instance as an API call like:0x000D0x000A  'api/RQ/Order/WHERE Value 0x003E 1000 NOK/REL Customer/ORDER BY LastName, FirstName/TAKE 50/'0x000D0x000Aor as a C# expression like:0x000D0x000A  'new QueryProgress(DataStorage, Orders).Where("Value 0x003E 100").Rel(typeof(Customer)).OrderBy("LastName,FirstName").Take(50)'0x000D0x000A(but in the latter case the standard LINQ extension in .NET will of course usually provide the same or better functionality (expect for AgoRapide unique queries like -QueryExpressionRel-)).0x000D0x000A0x000D0x000ASee also -CompoundKey- which expands the concept of keys.0x000D0x000A0x000D0x000AThe main purpose of the -QueryExpression- concept is to empower API users to create their own simple ad-hoc reports, without needing assistance from the API developers (that is, without any C# code having to be written or new API endpoints to be created).0x000D0x000A0x000D0x000AThe -QueryExpression- concept is not meant to be exhaustive with relation to relational modelling, nor is it proven formally.0x000D0x000AThis concept just takes away some (or actually rather quite a lot) of the need for 'hand-crafted' code in order to cover what are quite often very common scenarios.0x000D0x000A0x000D0x000AMore complex needs can be covered by -ApplicationSpecificCode- implementations of this class (see below).0x000D0x000A0x000D0x000ANote that queries can also be embedded in a -Subscription- (but this only gives meaning when querying against a hierarchical object storage, see -AdHocQuery-).0x000D0x000A0x000D0x000AThe most important implementing classes in -StandardAgoRapideCode- are:0x000D0x000A-QueryExpressionAll-0x000D0x000A-QueryExpressionSelect-0x000D0x000A-QueryExpressionWhere-0x000D0x000A-QueryExpressionOrderBy-0x000D0x000A-QueryExpressionSkip-0x000D0x000A-QueryExpressionTake-0x000D0x000ASome classes useful for aggregation queries are:0x000D0x000A-QueryExpressionPivot-0x000D0x000A-QueryExpressionAggregate-0x000D0x000A-QueryExpressionRel-0x000D0x000AOther implementing classes:0x000D0x000A-QueryExpressionShuffle-0x000D0x000A-QueryExpressionLimit-0x000D0x000A-QueryExpressionHint-0x000D0x000A-QueryExpressionStrict-0x000D0x000A-QueryExpressionCache-0x000D0x000A0x000D0x000ATODO: Potential sub-classes to be added:0x000D0x000A-QueryExpressionUnion- (for instance like /UNION 0x007BsubQuery0x007D)0x000D0x000A0x000D0x000ANote that the concept is inherently expandable, you can create your own sub-classes and integrate them with -StandardAgoRapideCode-.0x000D0x000ANote how any -ApplicationSpecificCode- implementations must be added to -Parsers- at application startup in order for them to be recognized by -TryParse-.0x000D0x000A0x000D0x000AOne practical application for -ApplicationSpecificCode- implementations of -QueryExpression- is hand-crafted reports, for instance a 'QueryExpressionReport042', available as for instance 'api/RQ/Report042'.0x000D0x000AAnother application could be hand-crafted HTML-representations of result sets.0x000D0x000A0x000D0x000ASee also -CompoundKey- (like -ForeignKey-, -EntityMethodKey- and -NewKey-),0x000D0x000A-FunctionKey-,0x000D0x000A-QuantileKey- and0x000D0x000A-ValueComparer-.0x000D0x000A0x000D0x000AThe implementations of -QueryExpression- (together with the classes mentioned above) constitute building blocks which for instance an API end-user can fit together to construct reports as needed.0x000D0x000AThis compares well to monolithic report creation where elements can not be reused easily.0x000D0x000A(it is similar to the UNIX philosophy of small utilities each performing a well defined easy-to-understand function).0x000D0x000A0x000D0x000ASome online applications demonstrating -QueryExpression- are:0x000D0x000Ahttp://ARNorthwind.AgoRapide.com and0x000D0x000Ahttp://ARAdventureWorksOLAP.AgoRapide.com 0x000D0x000A
__TOCDet/DocFragType = Class
__TOCDet/Name = QueryExpression
__TOCDet/Namespace = ARCQuery
__TOCDet/Type = QueryExpression
__TOCDet/Attribute/AssemblyName = ARCQuery
__TOCDet/Attribute/ClassNamespace = ARCQuery
__TOCDet/Attribute/ClassType = QueryExpression
__TOCDet/Attribute/Description = Represents part of a query (or actually a transformation) against a given collection and the data storage from which it was taken.0x000D0x000A0x000D0x000AA series of queries are usually chained together in a fluent fashion0x000D0x000Afor instance as an API call like:0x000D0x000A  'api/RQ/Order/WHERE Value 0x003E 1000 NOK/REL Customer/ORDER BY LastName, FirstName/TAKE 50/'0x000D0x000Aor as a C# expression like:0x000D0x000A  'new QueryProgress(DataStorage, Orders).Where("Value 0x003E 100").Rel(typeof(Customer)).OrderBy("LastName,FirstName").Take(50)'0x000D0x000A(but in the latter case the standard LINQ extension in .NET will of course usually provide the same or better functionality (expect for AgoRapide unique queries like -QueryExpressionRel-)).0x000D0x000A0x000D0x000ASee also -CompoundKey- which expands the concept of keys.0x000D0x000A0x000D0x000AThe main purpose of the -QueryExpression- concept is to empower API users to create their own simple ad-hoc reports, without needing assistance from the API developers (that is, without any C# code having to be written or new API endpoints to be created).0x000D0x000A0x000D0x000AThe -QueryExpression- concept is not meant to be exhaustive with relation to relational modelling, nor is it proven formally.0x000D0x000AThis concept just takes away some (or actually rather quite a lot) of the need for 'hand-crafted' code in order to cover what are quite often very common scenarios.0x000D0x000A0x000D0x000AMore complex needs can be covered by -ApplicationSpecificCode- implementations of this class (see below).0x000D0x000A0x000D0x000ANote that queries can also be embedded in a -Subscription- (but this only gives meaning when querying against a hierarchical object storage, see -AdHocQuery-).0x000D0x000A0x000D0x000AThe most important implementing classes in -StandardAgoRapideCode- are:0x000D0x000A-QueryExpressionAll-0x000D0x000A-QueryExpressionSelect-0x000D0x000A-QueryExpressionWhere-0x000D0x000A-QueryExpressionOrderBy-0x000D0x000A-QueryExpressionSkip-0x000D0x000A-QueryExpressionTake-0x000D0x000ASome classes useful for aggregation queries are:0x000D0x000A-QueryExpressionPivot-0x000D0x000A-QueryExpressionAggregate-0x000D0x000A-QueryExpressionRel-0x000D0x000AOther implementing classes:0x000D0x000A-QueryExpressionShuffle-0x000D0x000A-QueryExpressionLimit-0x000D0x000A-QueryExpressionHint-0x000D0x000A-QueryExpressionStrict-0x000D0x000A-QueryExpressionCache-0x000D0x000A0x000D0x000ATODO: Potential sub-classes to be added:0x000D0x000A-QueryExpressionUnion- (for instance like /UNION 0x007BsubQuery0x007D)0x000D0x000A0x000D0x000ANote that the concept is inherently expandable, you can create your own sub-classes and integrate them with -StandardAgoRapideCode-.0x000D0x000ANote how any -ApplicationSpecificCode- implementations must be added to -Parsers- at application startup in order for them to be recognized by -TryParse-.0x000D0x000A0x000D0x000AOne practical application for -ApplicationSpecificCode- implementations of -QueryExpression- is hand-crafted reports, for instance a 'QueryExpressionReport042', available as for instance 'api/RQ/Report042'.0x000D0x000AAnother application could be hand-crafted HTML-representations of result sets.0x000D0x000A0x000D0x000ASee also -CompoundKey- (like -ForeignKey-, -EntityMethodKey- and -NewKey-),0x000D0x000A-FunctionKey-,0x000D0x000A-QuantileKey- and0x000D0x000A-ValueComparer-.0x000D0x000A0x000D0x000AThe implementations of -QueryExpression- (together with the classes mentioned above) constitute building blocks which for instance an API end-user can fit together to construct reports as needed.0x000D0x000AThis compares well to monolithic report creation where elements can not be reused easily.0x000D0x000A(it is similar to the UNIX philosophy of small utilities each performing a well defined easy-to-understand function).0x000D0x000A0x000D0x000ASome online applications demonstrating -QueryExpression- are:0x000D0x000Ahttp://ARNorthwind.AgoRapide.com and0x000D0x000Ahttp://ARAdventureWorksOLAP.AgoRapide.com 0x000D0x000A
__TOCDet/Attribute/Interfaces = ITypeDescriber0x003BIEquatable0xoooo003CQueryExpression0xoooo003E
__TOCDet/Attribute/InterfacesDirectlyImplemented = ITypeDescriber0x003BIEquatable0xoooo003CQueryExpression0xoooo003E
__TOCDet/Attribute/SubTypes = QueryExpressionAggregate0x003BQueryExpressionAll0x003BQueryExpressionCache0x003BQueryExpressionHint0x003BQueryExpressionLimit0x003BQueryExpressionLog0x003BQueryExpressionOrderBy0x003BQueryExpressionPivot0x003BQueryExpressionRel0x003BQueryExpressionSelect0x003BQueryExpressionShuffle0x003BQueryExpressionSkip0x003BQueryExpressionStrict0x003BQueryExpressionTake0x003BQueryExpressionWhere
QueryExpressionAggregate/__TOCDet/Assembly = ARCQuery
QueryExpressionAggregate/__TOCDet/Description = Aggregates over the given key.0x000D0x000A0x000D0x000AExamples:0x000D0x000A  'AGGREGATE Product'.0x000D0x000Aor0x000D0x000A  'AGGREGATE Product BY Year SUM Amount'.0x000D0x000A0x000D0x000ASee -SyntaxHelp-.0x000D0x000A0x000D0x000ASee also:0x000D0x000A-QueryExpressionPivot- which aggregates over two keys (row key and column key).0x000D0x000Aand0x000D0x000A-FunctionKeyAggregate- which operates over a collection of properties.0x000D0x000A0x000D0x000ATODO: As of Nov 2020 there is lot of similar code in -QueryExpressionPivot- and -QueryExpressionAggregate.0x000D0x000A
QueryExpressionAggregate/__TOCDet/DocFragType = Class
QueryExpressionAggregate/__TOCDet/Name = QueryExpressionAggregate
QueryExpressionAggregate/__TOCDet/Namespace = ARCQuery
QueryExpressionAggregate/__TOCDet/Type = QueryExpressionAggregate
QueryExpressionAggregate/__TOCDet/Attribute/AssemblyName = ARCQuery
QueryExpressionAggregate/__TOCDet/Attribute/BaseTypes = QueryExpression
QueryExpressionAggregate/__TOCDet/Attribute/ClassNamespace = ARCQuery
QueryExpressionAggregate/__TOCDet/Attribute/ClassType = QueryExpressionAggregate
QueryExpressionAggregate/__TOCDet/Attribute/Description = Aggregates over the given key.0x000D0x000A0x000D0x000AExamples:0x000D0x000A  'AGGREGATE Product'.0x000D0x000Aor0x000D0x000A  'AGGREGATE Product BY Year SUM Amount'.0x000D0x000A0x000D0x000ASee -SyntaxHelp-.0x000D0x000A0x000D0x000ASee also:0x000D0x000A-QueryExpressionPivot- which aggregates over two keys (row key and column key).0x000D0x000Aand0x000D0x000A-FunctionKeyAggregate- which operates over a collection of properties.0x000D0x000A0x000D0x000ATODO: As of Nov 2020 there is lot of similar code in -QueryExpressionPivot- and -QueryExpressionAggregate.0x000D0x000A
QueryExpressionAggregate/__TOCDet/Attribute/Interfaces = ITypeDescriber0x003BIEquatable0xoooo003CQueryExpression0xoooo003E
QueryExpressionAll/__TOCDet/Assembly = ARCQuery
QueryExpressionAll/__TOCDet/Description = Represents all entities for a given collection.0x000D0x000A0x000D0x000A(-Execute- just returns the input collection, without making any changes).0x000D0x000A0x000D0x000AUseful in order to get result set presented by -ToHTMLSimpleSingle- (from -QueryProgress-) instead of -ToHTMLSimpleSingle- (from -ARCDoc-.-Extensions-).0x000D0x000A0x000D0x000AExample:0x000D0x000AFor a query like 'Customer' presentation will be done by -ARCDoc-.-Extensions-.-ToHTMLSimpleSingle- as default.0x000D0x000AFor a query like 'Customer/All' presentation will be done by -QueryProgress-.-ToHTMLSimpleSingle- as default.0x000D0x000A0x000D0x000ANote: -QueryExpressionAll- differs from -QueryExpressionSelect- 'SELECT *' regarding use of -EntityMethodKey-s.0x000D0x000AThe query 'Customer/All' will not include -EntityMethodKey-s, while 'Customer/SELECT *' would.0x000D0x000A0x000D0x000ASee -SyntaxHelp-.
QueryExpressionAll/__TOCDet/DocFragType = Class
QueryExpressionAll/__TOCDet/Name = QueryExpressionAll
QueryExpressionAll/__TOCDet/Namespace = ARCQuery
QueryExpressionAll/__TOCDet/Type = QueryExpressionAll
QueryExpressionAll/__TOCDet/Attribute/AssemblyName = ARCQuery
QueryExpressionAll/__TOCDet/Attribute/BaseTypes = QueryExpression
QueryExpressionAll/__TOCDet/Attribute/ClassNamespace = ARCQuery
QueryExpressionAll/__TOCDet/Attribute/ClassType = QueryExpressionAll
QueryExpressionAll/__TOCDet/Attribute/Description = Represents all entities for a given collection.0x000D0x000A0x000D0x000A(-Execute- just returns the input collection, without making any changes).0x000D0x000A0x000D0x000AUseful in order to get result set presented by -ToHTMLSimpleSingle- (from -QueryProgress-) instead of -ToHTMLSimpleSingle- (from -ARCDoc-.-Extensions-).0x000D0x000A0x000D0x000AExample:0x000D0x000AFor a query like 'Customer' presentation will be done by -ARCDoc-.-Extensions-.-ToHTMLSimpleSingle- as default.0x000D0x000AFor a query like 'Customer/All' presentation will be done by -QueryProgress-.-ToHTMLSimpleSingle- as default.0x000D0x000A0x000D0x000ANote: -QueryExpressionAll- differs from -QueryExpressionSelect- 'SELECT *' regarding use of -EntityMethodKey-s.0x000D0x000AThe query 'Customer/All' will not include -EntityMethodKey-s, while 'Customer/SELECT *' would.0x000D0x000A0x000D0x000ASee -SyntaxHelp-.
QueryExpressionAll/__TOCDet/Attribute/Interfaces = ITypeDescriber0x003BIEquatable0xoooo003CQueryExpression0xoooo003E
QueryExpressionCache/__TOCDet/Assembly = ARCQuery
QueryExpressionCache/__TOCDet/Description = Describes if cache is to be used or not.0x000D0x000A0x000D0x000AThis is relevant for generated values (as generated by -FunctionKey-, -NewKey- and similar). 0x000D0x000ASpecified through -QueryExpressionCache- and stored in -UseCache-.0x000D0x000AUsed by -TryGetP-.0x000D0x000ATODO: NOT IMPLEMENTED AS OF JUN 20200x000D0x000ATODO: Some issues are:0x000D0x000ATODO: 1) Impossible to store cached values back to IP sub-classes like -PExact-.0x000D0x000ATODO: 2) Introducing IP.CanAcceptAnyValue  would still defeat purpose, since 1) still holds0x000D0x000ATODO: 3) Having a global cache would be difficult, because no key available (not possible to use object itself as key).0x000D0x000ATODO: 4) Cache would 'poison' later queries (could introduce PCacheValue though, with DateTime created and similar metadata).0x000D0x000A0x000D0x000ADoes not affect query result (other than that data may be from cache and therefore stale).0x000D0x000A0x000D0x000ASet to ON if caches are to be used.0x000D0x000A0x000D0x000ASee -QueryExpressionWithSuggestions-.0x000D0x000A0x000D0x000ASee -SyntaxHelp-.
QueryExpressionCache/__TOCDet/DocFragType = Class
QueryExpressionCache/__TOCDet/Name = QueryExpressionCache
QueryExpressionCache/__TOCDet/Namespace = ARCQuery
QueryExpressionCache/__TOCDet/Type = QueryExpressionCache
QueryExpressionCache/__TOCDet/Attribute/AssemblyName = ARCQuery
QueryExpressionCache/__TOCDet/Attribute/BaseTypes = QueryExpression
QueryExpressionCache/__TOCDet/Attribute/ClassNamespace = ARCQuery
QueryExpressionCache/__TOCDet/Attribute/ClassType = QueryExpressionCache
QueryExpressionCache/__TOCDet/Attribute/Description = Describes if cache is to be used or not.0x000D0x000A0x000D0x000AThis is relevant for generated values (as generated by -FunctionKey-, -NewKey- and similar). 0x000D0x000ASpecified through -QueryExpressionCache- and stored in -UseCache-.0x000D0x000AUsed by -TryGetP-.0x000D0x000ATODO: NOT IMPLEMENTED AS OF JUN 20200x000D0x000ATODO: Some issues are:0x000D0x000ATODO: 1) Impossible to store cached values back to IP sub-classes like -PExact-.0x000D0x000ATODO: 2) Introducing IP.CanAcceptAnyValue  would still defeat purpose, since 1) still holds0x000D0x000ATODO: 3) Having a global cache would be difficult, because no key available (not possible to use object itself as key).0x000D0x000ATODO: 4) Cache would 'poison' later queries (could introduce PCacheValue though, with DateTime created and similar metadata).0x000D0x000A0x000D0x000ADoes not affect query result (other than that data may be from cache and therefore stale).0x000D0x000A0x000D0x000ASet to ON if caches are to be used.0x000D0x000A0x000D0x000ASee -QueryExpressionWithSuggestions-.0x000D0x000A0x000D0x000ASee -SyntaxHelp-.
QueryExpressionCache/__TOCDet/Attribute/Interfaces = ITypeDescriber0x003BIEquatable0xoooo003CQueryExpression0xoooo003E
QueryExpressionHint/__TOCDet/Assembly = ARCQuery
QueryExpressionHint/__TOCDet/Description = Describes if hints are to be generated (as query progresses) for potential new queries.0x000D0x000A0x000D0x000ASpecified through -QueryExpressionHint- and stored in -CreateHints-.0x000D0x000ADoes not affect query result.0x000D0x000A0x000D0x000ASet to OFF if hints are not needed (for instance if consumer of query is not a human). This will slightly improve performance.0x000D0x000A0x000D0x000ASee -QueryExpressionWithSuggestions-.0x000D0x000A0x000D0x000ASee -SyntaxHelp-.
QueryExpressionHint/__TOCDet/DocFragType = Class
QueryExpressionHint/__TOCDet/Name = QueryExpressionHint
QueryExpressionHint/__TOCDet/Namespace = ARCQuery
QueryExpressionHint/__TOCDet/Type = QueryExpressionHint
QueryExpressionHint/__TOCDet/Attribute/AssemblyName = ARCQuery
QueryExpressionHint/__TOCDet/Attribute/BaseTypes = QueryExpression
QueryExpressionHint/__TOCDet/Attribute/ClassNamespace = ARCQuery
QueryExpressionHint/__TOCDet/Attribute/ClassType = QueryExpressionHint
QueryExpressionHint/__TOCDet/Attribute/Description = Describes if hints are to be generated (as query progresses) for potential new queries.0x000D0x000A0x000D0x000ASpecified through -QueryExpressionHint- and stored in -CreateHints-.0x000D0x000ADoes not affect query result.0x000D0x000A0x000D0x000ASet to OFF if hints are not needed (for instance if consumer of query is not a human). This will slightly improve performance.0x000D0x000A0x000D0x000ASee -QueryExpressionWithSuggestions-.0x000D0x000A0x000D0x000ASee -SyntaxHelp-.
QueryExpressionHint/__TOCDet/Attribute/Interfaces = ITypeDescriber0x003BIEquatable0xoooo003CQueryExpression0xoooo003E
QueryExpressionLimit/__TOCDet/Assembly = ARCQuery
QueryExpressionLimit/__TOCDet/Description = Limits the final HTML presentation of results (limits the number of elements being presented). 0x000D0x000ADoes not affect the query in itself. Used in order to avoid building huge HTML pages which will not be consumed anyway.0x000D0x000ASpecified through -QueryExpressionLimit- and stored in -Limit-.0x000D0x000ASee also -QueryExpressionTake- which takes a specific number of elements from the current query result.0x000D0x000A0x000D0x000ASee -SyntaxHelp-.
QueryExpressionLimit/__TOCDet/DocFragType = Class
QueryExpressionLimit/__TOCDet/Name = QueryExpressionLimit
QueryExpressionLimit/__TOCDet/Namespace = ARCQuery
QueryExpressionLimit/__TOCDet/Type = QueryExpressionLimit
QueryExpressionLimit/__TOCDet/Attribute/AssemblyName = ARCQuery
QueryExpressionLimit/__TOCDet/Attribute/BaseTypes = QueryExpression
QueryExpressionLimit/__TOCDet/Attribute/ClassNamespace = ARCQuery
QueryExpressionLimit/__TOCDet/Attribute/ClassType = QueryExpressionLimit
QueryExpressionLimit/__TOCDet/Attribute/Description = Limits the final HTML presentation of results (limits the number of elements being presented). 0x000D0x000ADoes not affect the query in itself. Used in order to avoid building huge HTML pages which will not be consumed anyway.0x000D0x000ASpecified through -QueryExpressionLimit- and stored in -Limit-.0x000D0x000ASee also -QueryExpressionTake- which takes a specific number of elements from the current query result.0x000D0x000A0x000D0x000ASee -SyntaxHelp-.
QueryExpressionLimit/__TOCDet/Attribute/Interfaces = ITypeDescriber0x003BIEquatable0xoooo003CQueryExpression0xoooo003E
QueryExpressionLog/__TOCDet/Assembly = ARCQuery
QueryExpressionLog/__TOCDet/Description = A debugging tool used to extract detailed log information about the execution of the query.0x000D0x000A0x000D0x000AGives as result the content of -AllLogEntriesForThisQuery-.0x000D0x000A0x000D0x000AUseful in circumstances where the query is considered successful from the view of -ARCQuery- but the user need to debug how the result was achieved.0x000D0x000A(Note that if a query fails then -ToHTMLSimpleSingle- will show the log result anyway).0x000D0x000A0x000D0x000ASee -SyntaxHelp-.
QueryExpressionLog/__TOCDet/DocFragType = Class
QueryExpressionLog/__TOCDet/Name = QueryExpressionLog
QueryExpressionLog/__TOCDet/Namespace = ARCQuery
QueryExpressionLog/__TOCDet/Type = QueryExpressionLog
QueryExpressionLog/__TOCDet/Attribute/AssemblyName = ARCQuery
QueryExpressionLog/__TOCDet/Attribute/BaseTypes = QueryExpression
QueryExpressionLog/__TOCDet/Attribute/ClassNamespace = ARCQuery
QueryExpressionLog/__TOCDet/Attribute/ClassType = QueryExpressionLog
QueryExpressionLog/__TOCDet/Attribute/Description = A debugging tool used to extract detailed log information about the execution of the query.0x000D0x000A0x000D0x000AGives as result the content of -AllLogEntriesForThisQuery-.0x000D0x000A0x000D0x000AUseful in circumstances where the query is considered successful from the view of -ARCQuery- but the user need to debug how the result was achieved.0x000D0x000A(Note that if a query fails then -ToHTMLSimpleSingle- will show the log result anyway).0x000D0x000A0x000D0x000ASee -SyntaxHelp-.
QueryExpressionLog/__TOCDet/Attribute/Interfaces = ITypeDescriber0x003BIEquatable0xoooo003CQueryExpression0xoooo003E
QueryExpressionOrderBy/__TOCDet/Assembly = ARCQuery
QueryExpressionOrderBy/__TOCDet/Description = Orders collection.0x000D0x000A0x000D0x000ASee -SyntaxHelp-.0x000D0x000A0x000D0x000ATODO: Implement also QueryThenBy and QueryThenByDescending as in ThenBy0x000D0x000ATOOD: Syntax 'THEN BY 0x007Bkey0x007D 0x005BDESC0x005D / 0x005BASC0x005D'0x000D0x000ATODO: Should probably work through casting of Progress to IOrderedEnumerable.0x000D0x000ATODO: OR, just improve parser her (multiple fields with ASC / DESC), and utilize ThenBy from within this class.
QueryExpressionOrderBy/__TOCDet/DocFragType = Class
QueryExpressionOrderBy/__TOCDet/Name = QueryExpressionOrderBy
QueryExpressionOrderBy/__TOCDet/Namespace = ARCQuery
QueryExpressionOrderBy/__TOCDet/Type = QueryExpressionOrderBy
QueryExpressionOrderBy/__TOCDet/Attribute/AssemblyName = ARCQuery
QueryExpressionOrderBy/__TOCDet/Attribute/BaseTypes = QueryExpression
QueryExpressionOrderBy/__TOCDet/Attribute/ClassNamespace = ARCQuery
QueryExpressionOrderBy/__TOCDet/Attribute/ClassType = QueryExpressionOrderBy
QueryExpressionOrderBy/__TOCDet/Attribute/Description = Orders collection.0x000D0x000A0x000D0x000ASee -SyntaxHelp-.0x000D0x000A0x000D0x000ATODO: Implement also QueryThenBy and QueryThenByDescending as in ThenBy0x000D0x000ATOOD: Syntax 'THEN BY 0x007Bkey0x007D 0x005BDESC0x005D / 0x005BASC0x005D'0x000D0x000ATODO: Should probably work through casting of Progress to IOrderedEnumerable.0x000D0x000ATODO: OR, just improve parser her (multiple fields with ASC / DESC), and utilize ThenBy from within this class.
QueryExpressionOrderBy/__TOCDet/Attribute/Interfaces = ITypeDescriber0x003BIEquatable0xoooo003CQueryExpression0xoooo003E
QueryExpressionPivot/__TOCDet/Assembly = ARCQuery
QueryExpressionPivot/__TOCDet/Description = Creates a table by querying over two keys like0x000D0x000A  For 'Order', 'PIVOT Product BY Year'.0x000D0x000Aor0x000D0x000A  'PIVOT Product BY Year SUM Amount'.0x000D0x000A0x000D0x000ASee -SyntaxHelp-.0x000D0x000A0x000D0x000ASee also:0x000D0x000A-QueryExpressionAggregate- which aggregates over only one key0x000D0x000Aand0x000D0x000A-FunctionKeyAggregate- which operates over a collection of properties.0x000D0x000A0x000D0x000ATODO: Nov 2020: There is lot of similar code in -QueryExpressionPivot- and -QueryExpressionAggregate.0x000D0x000A
QueryExpressionPivot/__TOCDet/DocFragType = Class
QueryExpressionPivot/__TOCDet/Name = QueryExpressionPivot
QueryExpressionPivot/__TOCDet/Namespace = ARCQuery
QueryExpressionPivot/__TOCDet/Type = QueryExpressionPivot
QueryExpressionPivot/__TOCDet/Attribute/AssemblyName = ARCQuery
QueryExpressionPivot/__TOCDet/Attribute/BaseTypes = QueryExpression
QueryExpressionPivot/__TOCDet/Attribute/ClassNamespace = ARCQuery
QueryExpressionPivot/__TOCDet/Attribute/ClassType = QueryExpressionPivot
QueryExpressionPivot/__TOCDet/Attribute/Description = Creates a table by querying over two keys like0x000D0x000A  For 'Order', 'PIVOT Product BY Year'.0x000D0x000Aor0x000D0x000A  'PIVOT Product BY Year SUM Amount'.0x000D0x000A0x000D0x000ASee -SyntaxHelp-.0x000D0x000A0x000D0x000ASee also:0x000D0x000A-QueryExpressionAggregate- which aggregates over only one key0x000D0x000Aand0x000D0x000A-FunctionKeyAggregate- which operates over a collection of properties.0x000D0x000A0x000D0x000ATODO: Nov 2020: There is lot of similar code in -QueryExpressionPivot- and -QueryExpressionAggregate.0x000D0x000A
QueryExpressionPivot/__TOCDet/Attribute/Interfaces = ITypeDescriber0x003BIEquatable0xoooo003CQueryExpression0xoooo003E
QueryExpressionRel/__TOCDet/Assembly = ARCQuery
QueryExpressionRel/__TOCDet/Description = Enables 'jumping' or 'travelling' from a collection of one entity type to another (related) entity type.0x000D0x000A0x000D0x000AEnables queries like0x000D0x000A'Order/WHERE Amount 0x003E 10000 EUR/REL Customer/REL SupportTicket'0x000D0x000Awhich will show support tickets for all customer who at some time have ordered something for at least 10 000 EUR.0x000D0x000A0x000D0x000ACorresponds (very) coarsely to the JOIN concept in SQL0x000D0x000A0x000D0x000AThere are two ways for this to happen:0x000D0x000A0x000D0x000A1) -ToMany-:0x000D0x000AIf -IPRelationsKeysPointingTo- has a link for the current entity type, like 'Customer' having a link to 'Order' then a jump from a collection of Customers can be made to for instance an Order collection by iterating through all Orders with CustomerId present in the collection of Customers.0x000D0x000A0x000D0x000A2) -ToOne-:0x000D0x000AA jump from a collection of 'OrderLine' to 'Order', or 'Order' to 'Customer' can be made by iterating through the whole collection looking for respectively 'OrderId = xxx' and 'CustomerId = xxx' properties.0x000D0x000A0x000D0x000AVariant 1) (-ToMany-) will be the default attempted. Note how this depends on a more strongly typed schema (existence of entity classes, and -PK-s).0x000D0x000AIf 1) is not found, then variant 2) (-ToOne-) will be attempted.0x000D0x000A0x000D0x000ANOTE: The relevant keys for 'jumping' must exist. If you for instance do like this (admittedly meaningless query, but it explains the point though):0x000D0x000ANOTE:   'Order/WHERE Amount 0x003E 10000 EUR/SELECT Amount, Created/REL Customer'0x000D0x000ANOTE: then the key CustomerId is not available, and the jumping breaks down.0x000D0x000ANOTE:   'Order/WHERE Amount 0x003E 10000 EUR/SELECT CustomerId, Amount, Created/REL Customer'0x000D0x000ANOTE: on the other hand would work (but use of SELECT is meaningless anyway of course).0x000D0x000A0x000D0x000ASee -SyntaxHelp-.
QueryExpressionRel/__TOCDet/DocFragType = Class
QueryExpressionRel/__TOCDet/Name = QueryExpressionRel
QueryExpressionRel/__TOCDet/Namespace = ARCQuery
QueryExpressionRel/__TOCDet/Type = QueryExpressionRel
QueryExpressionRel/__TOCDet/Attribute/AssemblyName = ARCQuery
QueryExpressionRel/__TOCDet/Attribute/BaseTypes = QueryExpression
QueryExpressionRel/__TOCDet/Attribute/ClassNamespace = ARCQuery
QueryExpressionRel/__TOCDet/Attribute/ClassType = QueryExpressionRel
QueryExpressionRel/__TOCDet/Attribute/Description = Enables 'jumping' or 'travelling' from a collection of one entity type to another (related) entity type.0x000D0x000A0x000D0x000AEnables queries like0x000D0x000A'Order/WHERE Amount 0x003E 10000 EUR/REL Customer/REL SupportTicket'0x000D0x000Awhich will show support tickets for all customer who at some time have ordered something for at least 10 000 EUR.0x000D0x000A0x000D0x000ACorresponds (very) coarsely to the JOIN concept in SQL0x000D0x000A0x000D0x000AThere are two ways for this to happen:0x000D0x000A0x000D0x000A1) -ToMany-:0x000D0x000AIf -IPRelationsKeysPointingTo- has a link for the current entity type, like 'Customer' having a link to 'Order' then a jump from a collection of Customers can be made to for instance an Order collection by iterating through all Orders with CustomerId present in the collection of Customers.0x000D0x000A0x000D0x000A2) -ToOne-:0x000D0x000AA jump from a collection of 'OrderLine' to 'Order', or 'Order' to 'Customer' can be made by iterating through the whole collection looking for respectively 'OrderId = xxx' and 'CustomerId = xxx' properties.0x000D0x000A0x000D0x000AVariant 1) (-ToMany-) will be the default attempted. Note how this depends on a more strongly typed schema (existence of entity classes, and -PK-s).0x000D0x000AIf 1) is not found, then variant 2) (-ToOne-) will be attempted.0x000D0x000A0x000D0x000ANOTE: The relevant keys for 'jumping' must exist. If you for instance do like this (admittedly meaningless query, but it explains the point though):0x000D0x000ANOTE:   'Order/WHERE Amount 0x003E 10000 EUR/SELECT Amount, Created/REL Customer'0x000D0x000ANOTE: then the key CustomerId is not available, and the jumping breaks down.0x000D0x000ANOTE:   'Order/WHERE Amount 0x003E 10000 EUR/SELECT CustomerId, Amount, Created/REL Customer'0x000D0x000ANOTE: on the other hand would work (but use of SELECT is meaningless anyway of course).0x000D0x000A0x000D0x000ASee -SyntaxHelp-.
QueryExpressionRel/__TOCDet/Attribute/Interfaces = ITypeDescriber0x003BIEquatable0xoooo003CQueryExpression0xoooo003E
QueryExpressionSelect/__TOCDet/Assembly = ARCQuery
QueryExpressionSelect/__TOCDet/Description = Selects which fields to include.0x000D0x000A0x000D0x000ANote: -QueryExpressionAll- differs from -QueryExpressionSelect- 'SELECT *' regarding use of -EntityMethodKey-s.0x000D0x000AThe query 'Customer/All' will not include -EntityMethodKey-s, while 'Customer/SELECT *' would.0x000D0x000A0x000D0x000A'SELECT *' can be used in connection with -CompoundKey-, like for instance0x000D0x000A'Customer/SELECT *, CountP()' which will select all fields in addition to a new field calculated by -NewKeyCountP-.0x000D0x000ASee -CompoundKey- for the quite rich functionality offered (like traversion of entity relations for instance).0x000D0x000A0x000D0x000AHINT: It is recommended to use 'AS' when using -CompoundKey- if subsequent -QueryExpression-s follows.0x000D0x000AHINT: This will reduce parsing complexities because a complex field name may be unnecessary attempted evaluated as a -CompoundKey-.0x000D0x000AHINT: Example: For 'Customer/SELECT Name, Order.OrderLine.Sum.Sum()/ORDER BY Order.OrderLine.Sum.Sum()', HINT: if the key 'Order.OrderLine.Sum.Sum()' does not exist for some Customer, it will be attempted reevaluated by the following -QueryExpressionOrderBy-0x000D0x000AHINT: and may be misunderstood.0x000D0x000AHINT: Doing instead 'Customer/SELECT Name, Order.OrderLine.Sum.Sum() AS OrderSum/ORDER BY OrderSum' will remove this possibility0x000D0x000AHINT: (and be more readable also).0x000D0x000A0x000D0x000ANote: The original key type is not necessarily preserved.0x000D0x000ASee hack in -OrderAndReconstructKeys- (called from -ToHTMLSimpleSingle- for details.0x000D0x000A0x000D0x000ATODO: Add some functionality recognizing -PriorityOrder-, like0x000D0x000ATODO: 'SELECT' which could select only from -Important- or lesser value.0x000D0x000ATODO: Or 'SELECT WHERE PriorityOrder LEQ Important' (Using negative values for PriorityOrder is not very intuitive here).0x000D0x000ATODO: or any other query against the property keys for the relevant entity class.0x000D0x000A0x000D0x000ASee -SyntaxHelp-.
QueryExpressionSelect/__TOCDet/DocFragType = Class
QueryExpressionSelect/__TOCDet/Name = QueryExpressionSelect
QueryExpressionSelect/__TOCDet/Namespace = ARCQuery
QueryExpressionSelect/__TOCDet/Type = QueryExpressionSelect
QueryExpressionSelect/__TOCDet/Attribute/AssemblyName = ARCQuery
QueryExpressionSelect/__TOCDet/Attribute/BaseTypes = QueryExpression
QueryExpressionSelect/__TOCDet/Attribute/ClassNamespace = ARCQuery
QueryExpressionSelect/__TOCDet/Attribute/ClassType = QueryExpressionSelect
QueryExpressionSelect/__TOCDet/Attribute/Description = Selects which fields to include.0x000D0x000A0x000D0x000ANote: -QueryExpressionAll- differs from -QueryExpressionSelect- 'SELECT *' regarding use of -EntityMethodKey-s.0x000D0x000AThe query 'Customer/All' will not include -EntityMethodKey-s, while 'Customer/SELECT *' would.0x000D0x000A0x000D0x000A'SELECT *' can be used in connection with -CompoundKey-, like for instance0x000D0x000A'Customer/SELECT *, CountP()' which will select all fields in addition to a new field calculated by -NewKeyCountP-.0x000D0x000ASee -CompoundKey- for the quite rich functionality offered (like traversion of entity relations for instance).0x000D0x000A0x000D0x000AHINT: It is recommended to use 'AS' when using -CompoundKey- if subsequent -QueryExpression-s follows.0x000D0x000AHINT: This will reduce parsing complexities because a complex field name may be unnecessary attempted evaluated as a -CompoundKey-.0x000D0x000AHINT: Example: For 'Customer/SELECT Name, Order.OrderLine.Sum.Sum()/ORDER BY Order.OrderLine.Sum.Sum()', HINT: if the key 'Order.OrderLine.Sum.Sum()' does not exist for some Customer, it will be attempted reevaluated by the following -QueryExpressionOrderBy-0x000D0x000AHINT: and may be misunderstood.0x000D0x000AHINT: Doing instead 'Customer/SELECT Name, Order.OrderLine.Sum.Sum() AS OrderSum/ORDER BY OrderSum' will remove this possibility0x000D0x000AHINT: (and be more readable also).0x000D0x000A0x000D0x000ANote: The original key type is not necessarily preserved.0x000D0x000ASee hack in -OrderAndReconstructKeys- (called from -ToHTMLSimpleSingle- for details.0x000D0x000A0x000D0x000ATODO: Add some functionality recognizing -PriorityOrder-, like0x000D0x000ATODO: 'SELECT' which could select only from -Important- or lesser value.0x000D0x000ATODO: Or 'SELECT WHERE PriorityOrder LEQ Important' (Using negative values for PriorityOrder is not very intuitive here).0x000D0x000ATODO: or any other query against the property keys for the relevant entity class.0x000D0x000A0x000D0x000ASee -SyntaxHelp-.
QueryExpressionSelect/__TOCDet/Attribute/Interfaces = ITypeDescriber0x003BIEquatable0xoooo003CQueryExpression0xoooo003E
QueryExpressionShuffle/__TOCDet/Assembly = ARCQuery
QueryExpressionShuffle/__TOCDet/Description = Shuffles collection in random order.0x000D0x000A0x000D0x000AUseful when you want to see a limited but still 'representative' sample of result set.0x000D0x000A0x000D0x000AUseful in collection with -QueryExpressionTake-.0x000D0x000A0x000D0x000ANote extension method -Shuffle- which can be used in C# directly.0x000D0x000ASee -SyntaxHelp-.
QueryExpressionShuffle/__TOCDet/DocFragType = Class
QueryExpressionShuffle/__TOCDet/Name = QueryExpressionShuffle
QueryExpressionShuffle/__TOCDet/Namespace = ARCQuery
QueryExpressionShuffle/__TOCDet/Type = QueryExpressionShuffle
QueryExpressionShuffle/__TOCDet/Attribute/AssemblyName = ARCQuery
QueryExpressionShuffle/__TOCDet/Attribute/BaseTypes = QueryExpression
QueryExpressionShuffle/__TOCDet/Attribute/ClassNamespace = ARCQuery
QueryExpressionShuffle/__TOCDet/Attribute/ClassType = QueryExpressionShuffle
QueryExpressionShuffle/__TOCDet/Attribute/Description = Shuffles collection in random order.0x000D0x000A0x000D0x000AUseful when you want to see a limited but still 'representative' sample of result set.0x000D0x000A0x000D0x000AUseful in collection with -QueryExpressionTake-.0x000D0x000A0x000D0x000ANote extension method -Shuffle- which can be used in C# directly.0x000D0x000ASee -SyntaxHelp-.
QueryExpressionShuffle/__TOCDet/Attribute/Interfaces = ITypeDescriber0x003BIEquatable0xoooo003CQueryExpression0xoooo003E
QueryExpressionSkip/__TOCDet/Assembly = ARCQuery
QueryExpressionSkip/__TOCDet/Description = Skips the specified number of elements from the current query result.0x000D0x000A0x000D0x000AUseful in combination with -QueryExpressionTake-.0x000D0x000A0x000D0x000ASee -SyntaxHelp-.
QueryExpressionSkip/__TOCDet/DocFragType = Class
QueryExpressionSkip/__TOCDet/Name = QueryExpressionSkip
QueryExpressionSkip/__TOCDet/Namespace = ARCQuery
QueryExpressionSkip/__TOCDet/Type = QueryExpressionSkip
QueryExpressionSkip/__TOCDet/Attribute/AssemblyName = ARCQuery
QueryExpressionSkip/__TOCDet/Attribute/BaseTypes = QueryExpression
QueryExpressionSkip/__TOCDet/Attribute/ClassNamespace = ARCQuery
QueryExpressionSkip/__TOCDet/Attribute/ClassType = QueryExpressionSkip
QueryExpressionSkip/__TOCDet/Attribute/Description = Skips the specified number of elements from the current query result.0x000D0x000A0x000D0x000AUseful in combination with -QueryExpressionTake-.0x000D0x000A0x000D0x000ASee -SyntaxHelp-.
QueryExpressionSkip/__TOCDet/Attribute/Interfaces = ITypeDescriber0x003BIEquatable0xoooo003CQueryExpression0xoooo003E
QueryExpressionStrict/__TOCDet/Assembly = ARCQuery
QueryExpressionStrict/__TOCDet/Description = Describes -Strictness- ON / OFF when executing query. 0x000D0x000ASpecified through -QueryExpressionStrict- and stored in -CurrentStrictness-.0x000D0x000ADoes not affect query result, only whether query will terminate or not due to perceived inconsistencies in the data.0x000D0x000A0x000D0x000AA typical example where you may want to set 'STRICT OFF' is when you have queries results where sometimes a specific field is not set, and that field is used in a subsequent query expression, for instance 'WHERE' or 'ORDER BY'.0x000D0x000AThis is because -QueryExpression does not have any concept of schema / 'supposed to exist' fields, it only sees the actual data.0x000D0x000AExample: If you have this:0x000D0x000A  Customer/42/FirstName = John0x000D0x000A  Customer/42/LastName = Smith0x000D0x000A  Customer/43/FirstName = Ann0x000D0x000AThen the query   "Customer/WHERE FirstName = 'Ann'/ORDER BY LastName'"0x000D0x000Awill fail because -QueryExpressionOrderBy- will not see any field 'LastName'.0x000D0x000AThis query0x000D0x000A  "Customer/WHERE FirstName = 'Ann'/STRICT OFF/ORDER BY LastName'"0x000D0x000Aon the other hand will succeed.0x000D0x000A0x000D0x000ASee -SyntaxHelp-.
QueryExpressionStrict/__TOCDet/DocFragType = Class
QueryExpressionStrict/__TOCDet/Name = QueryExpressionStrict
QueryExpressionStrict/__TOCDet/Namespace = ARCQuery
QueryExpressionStrict/__TOCDet/Type = QueryExpressionStrict
QueryExpressionStrict/__TOCDet/Attribute/AssemblyName = ARCQuery
QueryExpressionStrict/__TOCDet/Attribute/BaseTypes = QueryExpression
QueryExpressionStrict/__TOCDet/Attribute/ClassNamespace = ARCQuery
QueryExpressionStrict/__TOCDet/Attribute/ClassType = QueryExpressionStrict
QueryExpressionStrict/__TOCDet/Attribute/Description = Describes -Strictness- ON / OFF when executing query. 0x000D0x000ASpecified through -QueryExpressionStrict- and stored in -CurrentStrictness-.0x000D0x000ADoes not affect query result, only whether query will terminate or not due to perceived inconsistencies in the data.0x000D0x000A0x000D0x000AA typical example where you may want to set 'STRICT OFF' is when you have queries results where sometimes a specific field is not set, and that field is used in a subsequent query expression, for instance 'WHERE' or 'ORDER BY'.0x000D0x000AThis is because -QueryExpression does not have any concept of schema / 'supposed to exist' fields, it only sees the actual data.0x000D0x000AExample: If you have this:0x000D0x000A  Customer/42/FirstName = John0x000D0x000A  Customer/42/LastName = Smith0x000D0x000A  Customer/43/FirstName = Ann0x000D0x000AThen the query   "Customer/WHERE FirstName = 'Ann'/ORDER BY LastName'"0x000D0x000Awill fail because -QueryExpressionOrderBy- will not see any field 'LastName'.0x000D0x000AThis query0x000D0x000A  "Customer/WHERE FirstName = 'Ann'/STRICT OFF/ORDER BY LastName'"0x000D0x000Aon the other hand will succeed.0x000D0x000A0x000D0x000ASee -SyntaxHelp-.
QueryExpressionStrict/__TOCDet/Attribute/Interfaces = ITypeDescriber0x003BIEquatable0xoooo003CQueryExpression0xoooo003E
QueryExpressionTake/__TOCDet/Assembly = ARCQuery
QueryExpressionTake/__TOCDet/Description = Takes a specific number of elements from the current query result.0x000D0x000A0x000D0x000ASee also -QueryExpressionLimit- which limits the final HTML presentation of results.0x000D0x000A0x000D0x000AUseful in combination with either -QueryExpressionSkip- or -QueryExpressionShuffle-.0x000D0x000A0x000D0x000ASee -SyntaxHelp-.
QueryExpressionTake/__TOCDet/DocFragType = Class
QueryExpressionTake/__TOCDet/Name = QueryExpressionTake
QueryExpressionTake/__TOCDet/Namespace = ARCQuery
QueryExpressionTake/__TOCDet/Type = QueryExpressionTake
QueryExpressionTake/__TOCDet/Attribute/AssemblyName = ARCQuery
QueryExpressionTake/__TOCDet/Attribute/BaseTypes = QueryExpression
QueryExpressionTake/__TOCDet/Attribute/ClassNamespace = ARCQuery
QueryExpressionTake/__TOCDet/Attribute/ClassType = QueryExpressionTake
QueryExpressionTake/__TOCDet/Attribute/Description = Takes a specific number of elements from the current query result.0x000D0x000A0x000D0x000ASee also -QueryExpressionLimit- which limits the final HTML presentation of results.0x000D0x000A0x000D0x000AUseful in combination with either -QueryExpressionSkip- or -QueryExpressionShuffle-.0x000D0x000A0x000D0x000ASee -SyntaxHelp-.
QueryExpressionTake/__TOCDet/Attribute/Interfaces = ITypeDescriber0x003BIEquatable0xoooo003CQueryExpression0xoooo003E
QueryExpressionWhere/__TOCDet/Assembly = ARCQuery
QueryExpressionWhere/__TOCDet/Description = Executes a 'WHERE 0x007Bkey0x007D 0x007Boperator0x007D 0x007Bvalue0x007D' against the given collection.0x000D0x000A0x000D0x000AThis class offers extensive functionality.0x000D0x000ATODO: Document functionality better.0x000D0x000A0x000D0x000ASee -FunctionKey- for possible functions that can be applied to properties.0x000D0x000A0x000D0x000ASee -RelationalOperator- for list of possible operators.0x000D0x000A0x000D0x000AUnderstands use of -ValueComparer- like -ValueComparerDateTime-0x000D0x000A0x000D0x000ATODO: Expand syntax, in order to support 'AND' and 'OR'. TODO: Currently 'AND' can be simulated by chaining multiple -QueryExpressionWhere-, but not 'OR'.0x000D0x000A0x000D0x000ATODO: Allow 'IS NULL' and 'IS NOT NULL' in addition to 'EQ NULL' and 'NEQ NULL'0x000D0x000A0x000D0x000ASee -SyntaxHelp-.
QueryExpressionWhere/__TOCDet/DocFragType = Class
QueryExpressionWhere/__TOCDet/Name = QueryExpressionWhere
QueryExpressionWhere/__TOCDet/Namespace = ARCQuery
QueryExpressionWhere/__TOCDet/Type = QueryExpressionWhere
QueryExpressionWhere/__TOCDet/Attribute/AssemblyName = ARCQuery
QueryExpressionWhere/__TOCDet/Attribute/BaseTypes = QueryExpression
QueryExpressionWhere/__TOCDet/Attribute/ClassNamespace = ARCQuery
QueryExpressionWhere/__TOCDet/Attribute/ClassType = QueryExpressionWhere
QueryExpressionWhere/__TOCDet/Attribute/Description = Executes a 'WHERE 0x007Bkey0x007D 0x007Boperator0x007D 0x007Bvalue0x007D' against the given collection.0x000D0x000A0x000D0x000AThis class offers extensive functionality.0x000D0x000ATODO: Document functionality better.0x000D0x000A0x000D0x000ASee -FunctionKey- for possible functions that can be applied to properties.0x000D0x000A0x000D0x000ASee -RelationalOperator- for list of possible operators.0x000D0x000A0x000D0x000AUnderstands use of -ValueComparer- like -ValueComparerDateTime-0x000D0x000A0x000D0x000ATODO: Expand syntax, in order to support 'AND' and 'OR'. TODO: Currently 'AND' can be simulated by chaining multiple -QueryExpressionWhere-, but not 'OR'.0x000D0x000A0x000D0x000ATODO: Allow 'IS NULL' and 'IS NOT NULL' in addition to 'EQ NULL' and 'NEQ NULL'0x000D0x000A0x000D0x000ASee -SyntaxHelp-.
QueryExpressionWhere/__TOCDet/Attribute/Interfaces = ITypeDescriber0x003BIEquatable0xoooo003CQueryExpression0xoooo003E

Edit single sub keys only: __TOCDet / QueryExpressionAggregate / QueryExpressionAll / QueryExpressionCache / QueryExpressionHint / QueryExpressionLimit / QueryExpressionLog / QueryExpressionOrderBy / QueryExpressionPivot / QueryExpressionRel / QueryExpressionSelect / QueryExpressionShuffle / QueryExpressionSkip / QueryExpressionStrict / QueryExpressionTake / QueryExpressionWhere

Generated 2025-11-04 02:20:57.538 UTC