Supported Operators¶

This page is the authoritative reference for which LINQ operators translate to PartiQL server-side, which are evaluated client-side, and which are unsupported.

Filtering Operators¶

Projection Operators¶

Ordering Operators¶

Terminal Operators¶

Terminal operators execute the query and return results. The provider supports the following terminals:

Primary-Key Lookup¶

Use FindAsync when you have the full DynamoDB table key and want one entity by primary key. It checks the EF Core change tracker first. If the entity is not already tracked, the provider executes a base-table key-equality PartiQL query with ExecuteStatementRequest.Limit = 1.

// Partition-key-only table
var customer = await context.Customers.FindAsync(["CUSTOMER#123"], ct);

// Composite partition + sort key table; pass values in PK, SK order
var order = await context.Orders.FindAsync(["CUSTOMER#123", "ORDER#456"], ct);

FindAsync returns null when no item exists. It targets the base table and does not use secondary indexes or automatic index selection; use normal LINQ with .WithIndex(...) or automatic selection for secondary-index lookups. Synchronous Find can return an already-tracked entity, but throws if it needs to query DynamoDB.

DynamoDB-Specific Extensions¶

The following extension methods are unique to this provider and have no standard LINQ equivalent. They compose with the query before a terminal operator is called.

Unsupported Operators¶

The following operators are not supported and throw InvalidOperationException at translation time. The provider does not silently fall back to in-process evaluation.

Scalar Type Support¶

All scalar entity properties must map to a DynamoDB attribute type. Types without a native wire representation use built-in EF Core value converters.

Nullable variants of all types above are supported. Numeric comparisons use DynamoDB's single N wire type, so promotions to int, such as short to int, still bind as DynamoDB numbers. Custom types can be mapped using EF Core value converters; query parameters and constants use the property mapping so converters apply consistently.

Value-converted enums compare using the converter provider type. For example, an enum mapped with .HasConversion<string>() binds parameters as DynamoDB strings. Numeric casts of value-converted enums, such as (int)entity.Status == value, are not translated for parameter comparisons because the DynamoDB attribute stores the converted provider value. Compare enum values directly, or map the enum numerically if numeric comparisons are required.

See also¶

• How Queries Execute
• Filtering
• Limitations