Marcin Swierczynski's blog

If you’ve used Grails, you’re probably familiar with a domain class and its “constraints” block. There you can define conditions which have to be met by class’s fields. For example, you can enforce that a field have to be not-empty using “blank: false” condition. It’d be intuitive not to define conditions for the field you don’t care of. Unfortunately, there is a small trap here. Let’s use an example to explain it.

Let’s define an Invoice class with a few fields: number, draw date and payment date. The number and draw data are obligatory while the payment date isn’t, because you’re able to pay for an invoice by cash.

class Invoice {
	String number;
	Date drawDate;
	Date paymentDate;
	static constraints = {
		number(blank: false);
		drawDate(blank: false);
	}
}

It looks good, doesn’t it? You can generate controller and views for that class and test it in a browser. Try to leave a payment date field empty and save an invoice. Success – it works! OK, so let’s create a BootStrap entry for our new class. Again, try to omit its optional field – paymentDate.

def invoice = new Invoice(number: “1/2010”, drawDate: new Date()).save();

What value does invoice variable have? Null! What’s wrong? Why does it work in a browser and not directly in a code?

The answer is quite straight, but I haven’t found it in a documentation. The default, implicit value of a field’s constraint is “nullable: false”. When you fills in a form in your browser, you really sends a blank value – empty string. This string isn’t null so it meets “nullable: false” criteria. On the other hand, if you creates a new object in your code and you omits a field, you pass a null value and hence the validator doesn’t allow to create an object! Unfortunately, Grails doesn’t provide any descriptive message on what’s really going under the hood.

What can you do? You can set an explicit constraint for such a field: “nullable: true”. The complete class would be:

class Invoice {
	String number;
	Date drawDate;
	Date paymentDate;
	static constraints = {
		number(blank: false);
		drawDate(blank: false);
		paymentDate(nullable: true);
	}
}

Personally, I suggest to set “nullable: true” constraint for every field which is optional and “blank: false” for every obligatory field.

This article was previously posted at Groovy Zone.

I’ve recently came across a small issue in my Grails application. I had to set an initial value of auto-generated identifiers of my objects. Moreover, I had to use two different values in two classes. For example, identifiers in one table in database should start from 50, while in another table – from 1000. How to get this in Grails domain classes?

You have to use SequenceStyleGenerator with its parameter – initial_value. You can do this with generator phrase in mapping clousure:

class FirstClass {
  static mapping = {
    id(generator: 'org.hibernate.id.enhanced.SequenceStyleGenerator',
       params: [initial_value: 50])
  }
  ...
}

class SecondClass {
  static mapping = {
    id(generator: 'org.hibernate.id.enhanced.SequenceStyleGenerator',
       params: [initial_value: 1000])
  }
  ...
}

Unfortunately, in this case you’ll finish with the same sequence generator in both classes. That means that you’ll get one sequence shared between two tables. How to avoid this? Just specify sequence name using next parameter – sequence_name:

class FirstClass {
  static mapping = {
    id(generator: 'org.hibernate.id.enhanced.SequenceStyleGenerator',
       params: [sequence_name: 'first_seq', initial_value: 50])
  }
  ...
}

class SecondClass {
  static mapping = {
    id(generator: 'org.hibernate.id.enhanced.SequenceStyleGenerator',
       params: [sequence_name: 'second_seq', initial_value: 1000])
  }
  ...
}

What do you think about my solution? Do you know another one?

This article was previously posted at Groovy Zone.