Home/ Questions/Q 825515
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T03:16:09+00:00

If I have a Domain Model that has an ID that maps to a

  • 0

If I have a Domain Model that has an ID that maps to a SQL Server identity column, what does the POCO look like that contains that field?

Candidate 1: Allows anyone to set and get the ID. I don’t think we want anyone setting the ID except the Repository, from the SQL table.

public class Thing {
    public int ID {get;set;}
}

Candidate 2: Allows someone to set the ID upon creation, but we won’t know the ID until after we create the object (factory creates a blank Thing object where ID = 0 until we persist it). How would we set the ID after persisting?

public class Thing {
    public Thing () : This (ID: 0) {}
    public Thing (int ID) {
        this.ID = ID
    }
    private int _ID;
    public int ID {
        get { return this.ID;};
    }

Candidate 3: Methods to set ID?

Somehow we would need to allow the Repository to set the ID without allowing the consumer to change it. Any ideas? Is this barking up the wrong tree? Do we send the object to the Repository, save it, throw it away, then create a new object from the loaded version and return that as a new object?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    How about a public get accessor and an internal set accessor that throws InvalidOperationException if the underlying value is already non-zero?

    Obviously you already have some way of materializing the field so that you can even load the record. Why not just use the same mechanism? After all it’s not just identity values that you need to consider. It’s basically any value that can change in the database after an insert/update such as computed columns, columns affected by triggers, etc.

    • 0