c# - Is there a kind of design pattern or a methodology to delete a record on Db from UI? -


is there commonly referred methodology or kind of design-pattern or model when comes delete record user interface exists in database?

basically following steps should taken , when (like validation, deleting main record, how handle when there a

conflict reference constraint

how handle exceptions or notifying user on failure (how transfer bl failure info ui; catching exceptions or report object etc.) , more or less common issues regarding deletion context.

  1. delete link in web ui should open "delete page".
  2. on "delete page" should validate preconditions existing of related records. not display form if validation fails.
  3. post "delete page" should validate preconditions again , delete database record in 1 database transaction
  4. if second validation fails or database exception raised display general error message.

Comments

Popular posts from this blog

php - What is the difference between $_SERVER['PATH_INFO'] and $_SERVER['ORIG_PATH_INFO']? -

fortran - Function return type mismatch -

queue - mq_receive: message too long -