Docs Menu
Docs Home
/ / /
Entity Framework

Limitations

On this page

  • Overview
  • Unsupported Entity Framework Core Features
  • Select Projections
  • Type Discriminators
  • Scalar Aggregations
  • Transactions
  • Migrations
  • Database-First Development
  • Foreign Keys
  • Alternate Keys
  • Table Splitting
  • Temporal Tables
  • Spatial Data
  • Unsupported MongoDB Features
  • Time Series
  • Atlas Search
  • Vector Search

On this page, you can find a list of Entity Framework and MongoDB features that the MongoDB Entity Framework Core Provider does not support. Because the provider is in active development, some features listed on this page might be considered for future releases based on customer demand.

The following sections describe Entity Framework Core features that the Entity Framework Core Provider does not support.

Select projections use the Select() method in a LINQ query to change the structure of the created object. The projection changes the object by performing groupings, or selecting fields into anonymous types or alternative types not recognized by Entity Framework.

This version of the Entity Framework Core Provider does not support Select Projections.

A type discriminator is an element in a document that the Entity Framework Core Provider uses to decide which C# type to create for the document during deserialization.

This version of the Entity Framework Core Provider does not support type discriminators.

Top-level scalar aggregations are operations you can perform on a query, such as Count(), Min(), and Max(). This version of the Entity Framework Core Provider supports only the following scalar aggregation operations:

  • Count()

  • LongCount()

  • Any(), with or without predicates

This version of the Entity Framework Core Provider does not support other scalar aggregation operations.

Transactions ensure that all updates in a set of changes either succeed, or fail together so the database is not left in an inconsistent state.

This version of the Entity Framework Core Provider does not support the Entity Framework Core transaction model.

Migrations in Entity Framework Core are designed for relational databases. Because MongoDB is a document database, migrations are not supported by the MongoDB Entity Framework Core Provider.

MongoDB is designed to be flexible and does not require a database schema. Because of MongoDB's schemaless design, database-first development is not supported in the Entity Framework Core Provider.

Because MongoDB is a document database, the Entity Framework Core Provider does not support foreign keys.

Because MongoDB is a document database, the Entity Framework Core Provider does not support alternate keys.

MongoDB is a document database and does not have normalized tables. Because of this, table splitting is not supported by the Entity Framework Core Provider.

The Entity Framework Core Provider does not support temporal tables.

The Entity Framework Core Provider does not support spatial data.

The following sections describe MongoDB features that the Entity Framework Core Provider does not support.

The Entity Framework Core Provider does not support time series data or time series collections. These are MongoDB-exclusive features that are not available in Entity Framework Core.

The Entity Framework Core Provider does not support MongoDB Atlas search. Atlas Search is a MongoDB-exclusive feature with no similar feature available in Entity Framework Core.

The Entity Framework Core Provider does not support MongoDB Atlas Vector search. Atlas Vector Search is a MongoDB-exclusive feature with no similar feature available in Entity Framework Core.

← Write Data to MongoDB