Entity Framework未读取新增列值及LINQ to Entities异常问题

Hey there, let's work through this frustrating issue you're hitting. That error about isAdmin not being supported in LINQ to Entities usually boils down to a mismatch between your EF model and how the property is being used in queries. Here are the most common fixes to try:

• Check if isAdmin is a computed or non-mapped property
  LINQ to Entities translates your C# queries directly to SQL, so it can't handle properties that aren't directly mapped to a database column. If your isAdmin property is a custom computed one (like public bool isAdmin => RoleId == 1;) or has the [NotMapped] attribute, EF will ignore it as an entity member. Make sure the property in your model is a plain auto-implemented getter/setter tied directly to the database column:

  public bool isAdmin { get; set; }
  

• Verify full synchronization between your model and database
  Even if you re-added the ADO.NET model, sometimes the .edmx file's underlying mappings get stuck. Open your .edmx file in an XML editor and search for isAdmin to confirm it exists in three places:

  • The Conceptual Schema Definition Language (CSDL) section (your model class)
  • The Storage Schema Definition Language (SSDL) section (database table mapping)
  • The Mapping Specification Language (MSL) section (links CSDL to SSDL)
    If any of these are missing, use the "Update Model from Database" wizard again, make sure the table with isAdmin is checked, and force a full refresh.

• Clear all cached metadata and build artifacts
  EF and your project can hold onto old model metadata even after a machine restart. Try these steps:

  1. Delete the bin and obj folders in your project directory
  2. Clean and rebuild your solution in Visual Studio
  3. If you're running on IIS, recycle the application pool to clear any in-memory model cache

• Check for type mismatches between database column and model property
  A common gotcha is when the database column type doesn't align with your model's property type. For example, if your database uses tinyint for isAdmin but your model uses bool, EF might not map it correctly. Ensure the database column is a bit type (for SQL Server) and your model uses bool—this is the standard mapping for boolean values.

• Avoid using non-entity logic in LINQ queries
  If you're using isAdmin in a query with custom logic (like db.Users.Where(u => u.isAdmin && u.CreatedDate > DateTime.Now.AddDays(-7))), double-check that isAdmin isn't relying on other non-mapped properties. The entire query needs to be translatable to SQL, so any logic using isAdmin must only reference the mapped database column.

If none of these work, try creating a brand new small test project with just the affected table and model to isolate the issue—sometimes larger projects have hidden configuration conflicts that are easier to spot in a clean environment.

内容的提问来源于stack exchange，提问作者parfaire