Question

I want to build a WCF data service which should be used for CRUD operations on a database backend. In order to identify the related record of the object in the database I have to know it’s primary key. I use surrogate keys in my database schema.

Is it a good practice to pass the surrogate keys to the caller, so that it is possible to identify the records in the database in subsequent calls? (Caller retrieves object, caller modifies object, caller calls WCF update method) I know that surrogate keys should normally not be used outside the database. If that is not a good idea, what other options do I have?

Any advice is greatly apreciated.

Answer 1

Yes, your solution is totally adequate. It’s the simplest way to map CLR objects to persistent entities. Moreover, your services’ consumers may find this unqiue identifier useful when programming UI, for logging purposes etc.

I’d go this way without hesitation.