@Shashank Agrawal Yeah, we noticed this awhile ago and worked around it in a similar way. It would be nice if Grails handled the exceptions from the unique constraint in the mapping block better. The problem with using it this way is that you won't see it until the session is flushed, which can sometimes lose the context of the failure and make handling it harder.