Skip to main content

Grails - cross-field Date validation - Method using controllers

In continuation of my earlier post on the cross-field date validation , I'm going to discuss another method using grails controller.

The following code in "save" and "update" method of the controller validates the date fileds used in the student domain object that is discussed in the previous post

def save = {
def studentInstance = new Student (params)

if (studentInstance.endDate.before(studentInstance.startDate))
{

studentInstance.errors.rejectValue('endDate', 'student.endDate.shouldbegreater')
}

...
..
}

Note that the code highlighted as bold is the addition to the boiler-plate code generated by using the grails command "grails generate-all" on the domain class "Student"

Following message is to be added to the "messages.properties" file

vendor.contractEndDate.shouldbegreater= End Date should be greater than the start date.

The method used in controllers gives more control on validation rather than the method used in the domain class.

In scenarios where we need to validate "endDate" field referring to more than one domain object, having the validation in contoller is the right place.

Eg: If we have another domain class, "Course" with fields "courseStartDate" and "courseEndDate", we can apply a validation in rule saying Student.enddate <= Course.courseEndDate.
Labels:

Comments

Post a Comment

Popular posts from this blog

Grails - cross-field Date validation

Often we run into domain classes with date fields. If the domain class has two datefields, startDate and endDate, and the rule for a valid combination is "endDate to be greater than startDate", how do we handle? I listed below two of the options, either using domain level constraints or using the domain classes. Option 1: Using domain constraints. Let us take a sample Grails Domain class class Student{ String name String school Date startDate Date endDate } Add the following constraints to enforce validation rules where name, school, startDate cannot be blank and endDate if present should be greater than startDate.
5 comments
Read more

Grails - Querying complex associations

Criteria class allows performing complex searches on grails objects. There are number of shortcut methods for performing queries but these methods have limitations in terms of number of conditions used in "where clauses". Traditional sql "joins" are not possible as shown in some of the Grails "Finder" methods shown below. Sample 1: def list = AccountTransaction.findAllByCompanyCodeAndVoucherDateBetween(branch, fromDate, toDate, params) Sample 2: def list = AccountTransaction.findAllByCompanyCodeAndVoucherDateGreaterThanEquals(branch, fromDate, params) Sample 3: def list = AccountTransaction.findAllByCompanyCodeAndTransGroup(branch, group, params) "params" contains attributes related to sorting, paging etc. It is very easy to use finder methods but when you want to filter objects by more conditions we need to look for alternatives. For understanding the relationships used in this sample, I listed the grails domain classes. class TransactionTyp
4 comments
Read more

Implementing advanced sort in Grails

The "list" pages generated by inbuilt scaffolding/template features of grails have pagination and sorting features. However, if the domain object displayed in the list is a nested object having another domain object as a property, you may notice that sort is not enabled for that field. Boiler plate code for the header of the list is shown below. As you would have noticed few columns have sortable columns automatically generated by Grails command, generate-all or generate-views. The properties 'partyAccount' and 'bankAccount' in this sample are domain classes nested in the domain class 'partyTransaction'. We could convert them to sortable columns by using the tag g:sortableColum
2 comments
Read more