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.
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
