Hi,

 In the [sprocCategoryInsertUpdateSingleItem] stored procedure there is a block of code:
IF (@id IS NULL) -- Insert a new item
BEGIN
  IF NOT EXISTS (SELECT Id FROM Category WHERE Description = @description AND ContentTypeId = @contentTypeId)
  BEGIN
    INSERT INTO Category(Description, ContentTypeId, SortOrder) VALUES(@description, @contentTypeId, @sortOrder)
    SET @returnValue = SCOPE_IDENTITY()
  END
  ELSE
  BEGIN
    SET @returnValue = -1 -- record already exists
  END
END

Why we don't use a unique constraint on the fields instead?

Hi there,

You could indeed use a unique constraint to have the database enforce uniqueness.

However, IMO, you would still need to do the check manually. Relying on the constraint results in exceptions being thrown when the item already exists. By manually checking the description you can avoid handling run-time exceptions when they aren't necessary....

Imar

---------------------------------------
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Everyone is unique, except for me.
Author of ASP.NET 2.0 Instant Results and Beginning Dreamweaver MX / MX 2004

ok :D