Skip to content

query-usage.md

Latest commit

 

History

History
318 lines (234 loc) · 7.75 KB

query-usage.md

File metadata and controls

318 lines (234 loc) · 7.75 KB

Query Usage

Arguments

The arguments supported are ids, where, orderBy , skip, and take.

Arguments are executed in that order.

Ids

Queries entities by id. Currently the only supported identity member (property or field) name is Id.

Supported Types

String, Guid, Double, Boolean, Float, Byte, DateTime, DateTimeOffset, Decimal, Int16, Int32, Int64, UInt16, UInt32, and UInt64.

Single

{
  entities (ids: "1")
  {
    property
  }
}

Multiple

{
  entities (ids: ["1", "2"])
  {
    property
  }
}

Where

Where statements are and'ed together and executed in order.

Property Path

All where statements require a path. This is a full path to a, possible nested, property. Eg a property at the root level could be Address, while a nested property could be Address.Street. No null checking of nested values is done.

Supported Types

String, Guid, Double, Boolean, Float, Byte, DateTime, DateTimeOffset, Decimal, Int16, Int32, Int64, UInt16, UInt32, UInt64, and Enum.

Supported Comparisons

  • equal: (the default value if comparison is omitted)
  • greaterThan
  • greaterThanOrEqual
  • lessThan
  • lessThanOrEqual:
  • contains: Only works with string
  • startsWith: Only works with string
  • endsWith: Only works with string
  • in: Check if a member existing in a given collection of values
  • notIn: Negation of in operator (Deprecated, use negate property with in operator instead)
  • like: Performs a SQL Like by using EF.Functions.Like

Case of comparison names are ignored. So, for example, EndsWith, endsWith, and endswith are allowed.

Single

Single where statements can be expressed:

{
  entities
  (where: {
    path: "Property",
    comparison: "equal",
    value: "the value"})
  {
    property
  }
}

Where In

{
  testEntities
  (where: {
    path: "Property",
    comparison: "in",
    value: ["Value1", "Value2"]})
  {
    property
  }
}

Multiple Expressions and Expression Grouping

Expressions in the same logical grouping can be expressed together with a connector, on the preceeding where expression:

  • and: (default if no comparison provided)
  • or

When trying to logically group expressions, provide a Where expression with only the groupedExpressions property.

Multiple where statements with a logical grouping can be expressed:

{
  entities
  (where:
    [
      {path: "Property", comparison: "startsWith", value: "Valu"},
      {
        "groupedExpressions": [
          {path: "Property", comparison: "endsWith", value: "ue", comparison: "or"},
          {path: "Property", comparison: "endsWith", value: "id"}
        ]
      }
    ]
  )
  {
    property
  }
}

The above expression written as a logical statement would be:

Property.startsWith("value") && (Property.endsWith("ue") || Property.endsWith("id"))

Query Negation

If you need to negate any expression, including groupedExpressions, provide the negate property with true (Default is false).

Example:

{
  entities
  (where:
    [
      {path: "Property", comparison: "startsWith", value: "Valu", negate: true},
      {
        negate: true,
        "groupedExpressions": [
          {path: "Property", comparison: "endsWith", value: "ue", comparison: "or"},
          {path: "Property", comparison: "endsWith", value: "id"}
        ]
      }
    ]
  )
  {
    property
  }
}

Querying List Members

A common query function is constraining a master set by some property of the detail list. For example you want to filter all orders by line items for a specific product.

Note: This only constrains the master list and doesn't affect the detail list, you must re-query the detail list with the same query to achieve this effect.

To query a list member graph property, use parenthesis ([]) to wrap the property. Example:

{
  entities
  (where:
    [
      {
        path: "ListProperty[Property]",
        comparison: "startsWith",
        value: "Valu"
      }
    ]
  )
  {
    property
  }
}

Or:

{
  entities
  (where:
    [
      {
        path: "ListProperty[Property.AnotherProperty]",
        comparison: "startsWith",
        value: "Valu"
      }
    ]
  )
  {
    property
  }
}

Case Sensitivity

All string comparisons are, by default, done using no StringComparison. A custom StringComparison can be used via the case attribute.

{
  entities
  (where: {
    path: "Property",
    comparison: "endsWith",
    value: "the value",
    case: "Ordinal"})
  {
    property
  }
}

Null

Null can be expressed by omitting the value:

{
  entities
  (where: {path: "Property", comparison: "equal"})
  {
    property
  }
}

OrderBy

Ascending

{
  entities (orderBy: {path: "Property"})
  {
    property
  }
}

Descending

{
  entities (orderBy: {path: "Property", descending: true})
  {
    property
  }
}

Take

Queryable.Take or Enumerable.Take can be used as follows:

{
  entities (take: 1)
  {
    property
  }
}

Skip

Queryable.Skip or Enumerable.Skip can be used as follows:

{
  entities (skip: 1)
  {
    property
  }
}