[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
 [Collapse]Feature Center
  [Expand]Data Representation
  [Expand]Object Relational Mapping
  [Collapse]Connecting to a Data Store
    Data Access Layer
    Object Access Layer
    Session
    Unit of Work
    Cached Data Store
    Transferring Data via WCF Services
  [Expand]Data Exchange and Manipulation
  [Expand]Querying a Data Store
  [Expand]Using XPO in Web Applications
 [Expand]Concepts
 [Expand]Design-Time Features
 [Expand]Examples
 [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)

Object Access Layer

An object access layer (OAL for short) is a mediator between a Session (or Unit of Work) and a Data Access Layer. An OAL translates object queries and storage schema updates to corresponding statements, and passes them to a data access layer for execution. With OALs, sessions and units of work abstract data access at the object level, while leaving data store specifics to data access layers.

XPO provides the following object layer implementations.

Expanded Concepts

Expanded Task-Based Help

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