ansaurus

Question

Answer 1

A:

You're trying to save a record with an id that already exists.

If id is auto-generated, don't set it manually
If id is not auto-generated, set it to something else, for example max(id) + 1

armandino 2010-04-20 04:39:15

No, id is not auto generated and column is a unique key. Its a text field to enter and when user enters existing integer, it will fail to save. This works correctly, but in console i was getting the errors mentioned .

Srinath 2010-04-20 06:00:36

Answer 2

A:

surely no Exception should be thrown for constraint violation, but rather object.save() should return null? i.e.

if(object.save() == null) {
    // save failed
} else {
    // save succeeded
}

Alison 2010-04-20 08:56:19

Answer 3

A:

If you defined the uniqueness through a Grails constraint, you have to look for a ValidationException. This is thrown when object.validate() fails; Validation is done before any object.save().

try {
  object.save(failOnError: true)
}
catch(ValidationException ve) {
  // Do something ...
}

Bu remember: Any constraint violation, for any member variable can cause a ValidationException ... so you have to distiguish yourself.

Edit:

This applies, if you use the Grails 1.2 failOnError feature ...

air_blob 2010-04-20 13:48:46

yeah, but i'm on grails-1.1.2

Srinath 2010-04-20 18:58:52

Ok, now there are two possibilities: either try the common Grails validation procedure like if(obj.validate()) { obj.save() } else { obj.errors.each { // doh, there are errors ... } } (like Ali G mentioned) or a simpler and cleaner 'grails upgrade' ;)

air_blob 2010-04-21 09:14:12

ansaurus

tags:

views:

answers:

Grails Duplicate Exception handling

related questions