Invalid column name in Entity Framework Core

Question

I'm working on a project using .NET 8, Entity Framework Core and SQL Server. I have created a table called Accounts in my database using the following SQL script:

CREATE TABLE [dbo].[Accounts] 
(
    [Id] INT IDENTITY (1, 1) NOT NULL,
    [AccountEmail] NVARCHAR (100) NOT NULL UNIQUE,
    [HashedPassword] NVARCHAR (200) NOT NULL,
    [DateOfBirth] DATETIMEOFFSET NOT NULL,
    [RegisterDate] DATETIMEOFFSET NOT NULL,

    CONSTRAINT [PK_Accounts] PRIMARY KEY CLUSTERED ([Id] ASC)
);
GO

I have also created an entity class in C# to represent this table, as shown below:

public class Account : BaseModel
{
    public required string AccountEmail { get; set; }
    public required string HashedPassword { get; set; }
    public DateTimeOffset DateOfBirth { get; set; }
    public DateTimeOffset RegisterDate { get; set; }
    public User? User { get; set; }
}

Despite these configurations, when I try to add a new account, I get the following error:

Invalid column name 'AccountEmail'

Here is code for account creation:

public async Task<AccountResponse> Register(RegisterRequest request)
{
    if (await _dbContext.Accounts.AnyAsync(x => x.AccountEmail == request.Email.ToLower()))
        // error appears here
        throw new Exception("This e-mail address is already taken!"); 

    var user = new User
                   {
                       Username = request.Username
                   };

    var account = new Account
                      {
                          AccountEmail = request.Email,
                          HashedPassword = _passwordManager.HashPassword(request.Password),
                          DateOfBirth = request.DateOfBirth,
                          RegisterDate = DateTime.UtcNow,
                          User = user
                      };

    user.Account = account;

    _dbContext.Accounts.Add(account);
    await _dbContext.SaveChangesAsync();

    return new AccountResponse
               {
                   Email = account.AccountEmail,
                   Username = user.Username,
                   Token = _tokenService.GenerateAccountToken(account.Id)
               };
}

I have ensured that the column name AccountEmail is correctly spelled and matches in both the database schema and the entity class. I have also updated the database.

What could be causing this error, and how can I fix it?

Possible duplicate of stackoverflow.com/questions/55438857/… — Sebastian Van Rooyen
– Sebastian Van Rooyen, Commented May 21, 2024 at 20:48
You can also check that at runtime the DbContext is talking to the database you expect it to, and not an older schema that might be missing the column. Temporarily add the following line prior to attempting to read, with a breakpoint and check that the connection string is going to the expected database: `var connectionString = _dbContext.Database.GetDbConnection().ConnectionString;' — Steve Py
– Steve Py, Commented May 21, 2024 at 21:29
@StevePy you were right, I was connected to the wrong base via connectionString — changedevelopersoftware
– changedevelopersoftware, Commented May 21, 2024 at 22:20

Rahul Timbaliya · Accepted Answer · 2024-12-13 07:03:43Z

1

Once try Code First Approach
Create Migration And Apply into the database and check once

Also Update the Entity Model as follow

 namespace Test
 {
     [Table("Account")]
     public class Account : BaseModel
     {
         [Required]
         public string AccountEmail { get; set; }
         [Required]
         public string HashedPassword { get; set; }
         public DateTimeOffset DateOfBirth { get; set; }
         public DateTimeOffset RegisterDate { get; set; }
         public User? User { get; set; }
     }

 }

answered Dec 13, 2024 at 7:03

Rahul Timbaliya

365 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Invalid column name in Entity Framework Core

1 Answer 1

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related