[Expand]General Information
[Expand]WinForms Controls
[Expand]ASP.NET Controls and MVC Extensions
[Expand]ASP.NET Bootstrap Controls
[Expand]ASP.NET Core Bootstrap Controls
[Expand]WPF Controls
[Expand]Xamarin Controls
[Expand]Windows 10 App Controls
[Expand]Office File API
[Expand]Reporting
[Expand]Report and Dashboard Server
[Expand]Dashboard
[Expand]eXpressApp Framework
[Collapse]eXpress Persistent Objects
 [Expand]Product Information
 [Expand]Getting Started
 [Expand]Fundamentals
 [Expand]Feature Center
 [Expand]Concepts
 [Expand]Design-Time Features
 [Collapse]Examples
   How to: Access Data in SQL Query Results
   How to: Bind an XPCollection to a LookUp
   How to: Bind an XPCollection to Standard Controls
   How to: Bind an XPCollection to the DataGrid
   How to: Bind an XPCollection to the Grid
   How to: Build Complex Criteria
   How to: Build Simple Criteria
   How to: Change Inheritance Mapping
   How to: Connect to a SQL Server
   How to: Connect to SQL Azure
   How to: Connect XPO to a Database Other than MS SQL or MS Access
   How to: Control Automatic Saving of Objects when Editing in a Grid
   How to: Create an Aggregated Object
   How to: Delay Property Loading
   How to: Filter By DateTime Values
   How to: Filter Persistent Objects by Type
   How to: Handle Persistent Object Initialization
   How to: Implement a Custom Criteria Language Function Operator
   How to: Implement a Full-Text Search
   How to: Implement Custom Functions and Criteria in LINQ to XPO
   How to: Implement Many-to-Many Relationships
   How to: Implement One-to-One Relationships
   How to: Link Classes Located in Different Assemblies
   How to: Make a Class or Property Non-Persistent
   How to: Make XPCollection Create Objects of Specific Type when They are Created via Bound Controls
   How to: Map to Custom Tables (Views) and Columns
   How to: Obtain a Collection of Persistent Objects by a Set of Their IDs
   How to: Obtain a Collection of Persistent Objects for Processing
   How to: Persist a BLOB Field
   How to: Prevent Changes in a Persistent Object from being Automatically Committed
   How to: Restore Deleted Objects
   How to: Use Pageable Collections
   How to: Use Read-Only Persistent Properties
   How to: Use the ContainsOperator for Objects in a Many-to-Many Relationship
   How to: Validate an Object
   How to: Work with Structures
 [Expand]Member Tables
 [Expand]API Reference
[Expand]CodeRush
[Expand]CodeRush Classic
[Expand]Cross-Platform Core Libraries
[Expand]Tools and Utilities
 End-User Documentation
View this topic on docs.devexpress.com (Learn more)

How to: Build Simple Criteria

Using criteria objects you can precisely specify the objects that you want to appear in a collection. Criteria is a tree of objects representing a logical expression. Generally, a simple logical expression is comprised of a relational operator and its operands.

This topic demonstrates how to represent simple logical expressions in code. Please refer to How to Build Complex Criteria which is to do with complex logical expressions.

Expanded Building Simple Criteria - Example

With XPO, you have multiple options for building simple filter criteria. For instance, the same criteria which represents a simple logical expression (City <> "Chicago") can be represented using two different notations as shown in code examples below.

  • You can pass the appropriate operands as parameters to the BinaryOperator's constructor.

The main drawback of this way of writing criteria is that you have to write a lot of code. It can also be quite difficult to come up with complete hierarchies of operators that are frequently needed for complex expressions.

 

  • You can represent criteria as a human-readable string and parse it using the static CriteriaOperator.Parse method.

The number of criteria operators available in XPO allow you to easily form logical expressions of considerable complexity.

The drawback here is that complex expressions basically stored in string variables in the code are not checked. If you are creating operator classes in code, it's possible to make mistakes in field names, or comparing things that naturally can't be compared. The whole string containing a query expression can't be checked, and therefore can easily bring up runtime errors.

Expanded See Also

Is this topic helpful?​​​​​​​