Question

I develop winforms app. One of my forms accepts user input and calls a web service to add the input into the DB. The input must be unique, however I have no way of knowing if it is unique in the client side. I send the input to the WS and it is responsible of either adding it to the DB or informing the client that the input already exists.

What is the correct way to implement that?

Should I make two calls to the WS, one to know if it is unique and one to insert into the DB? I sense synchronization issues + two round trips across boundary.

Should I return an enum, ValueNotUnique and ValueInsertedSuccessfully?

Or perhaps throw an exception? That sounds not performance wise, plus I don’t like using exceptions for things I already know that might not work.

Is there a nice design to this mess? Help appreciated, thanks in advance!

Answer 1

I would probably do something like this:

• define an enumeration of result values; ValueAlreadyExists, ValueInserted etc.
• define a return object type that would include
  • the result of the operation, as that enum type
  • if the value already existed – possibly something like an ID or even some of the data
  • if the value was inserted successfully, the new ID

So you’d have:

public enum OpResult
{
   ValueInserted,
   ValueAlreadyExists
}

and a result type:

public class ResponseType
{
    public OpResult Result { get; set; }
    public int UniqueID { get; set; }
}

With this approach, you can easily

• extend the enumeration and add more possible outcomes for your operation
• extend the response type and add more information if you need it