How to handle constraint violations in session per request pattern?
1 view
Skip to first unread message
che
unread,
Jan 16, 2009, 2:19:54 AM1/16/09
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to nhusers
In session per request pattern, session is flushed and transaction
committed at the end of the request? How do I handle unique or check
constraint violations during the request? In my old applications, I
would simply catch constraint violation exceptions and then show
appropriate error message to the user.