gorm

I have two domain classes with 1:n relationship: import Action class Task { Action actionParent String taskName } and class Action { String actionName } I have the list of Tasks where I have the column "Action name", I would like to sort this column by Action.actionName. Now I'm using the createCriteria() method [I need to use it because I have more logic for filtering and sorting...], but I'm able to sort only by "Action.id". This method looks like: def criteria = Task.createCriteria(); taskList = criteria.list { if(parameters.max != null) maxResults(parameters.max) if(parameters.offset !=

In version 1.2, Grails introduced global constraints. I tried adding the following to Config.groovy grails.gorm.default = { constraints { notBlank(nullable:false, blank:false) } } Then using it in one of my domain classes static constraints = { email(email: true, unique: true, shared: 'notBlank') } But when I save a user with a null e-mail address, no errors are reported, why? Thanks, Don I've never tried to make global constraints, but I can tell you that if you want to mark a field as not blank and not nullable you don't need to create a new constraint at all, just add this to your domain

I have this domain : class Participation { ParticipationStatus status } class ParticipationStatus{ String name Date creationDate } I create a query : Participation.createCriteria().list{ createAlias("status","statusAlias") order "statusAlias.creationDate" projections{ groupProperty "id" } } But I received an error : Caused by: java.sql.SQLException: ORA-00979: N'est pas une expression GROUP BY I 'm working 2 days ago on this query grrrr ! ;-) Thanks a lot Every field you use in aggregate queries (the one using projections ) should be either a groupProperty , or only an aggregate function

Hibernate uses method calls to get the values of domain class properties by default. How can I configure direct field access with GORM? It's not directly supported but will be in 1.4. For now you can enable it with a custom Configuration subclass as described at http://grails.1312388.n4.nabble.com/GORM-setting-access-quot-field-quot-td1592837.html#a1594428 I did a small post about subclassing Configuration with links to specific examples at http://burtbeckwith.com/blog/?p=465 I suggest this is due to how groovy implements Beans convention therefore not something that can be configured for GORM

public class Address { static mapWith = "mongo" Region region; Zone zone; static mapping = { id generator: 'identity' region reference:true zone reference:true } } I'm interested in knowing what reference:true does. In my experience, leaving it off gives exactly the same result except there's no DBRef in the actual mongo document. It looks like reference controlls how documents are linked. When true , the related documents are referenced by db-refs , if false , GORM inserts simple id , aka Manual references in mongo This means that those properties will be stored on your Address record by

I have written a criteria query in a Grails service class where I expect an eager join to be performed, and to avoid lazy loading of child objects when displaying my results either as a JSON response or in my GSP. The query executed as expected (setting my hibernate.show_sql=true in my DataSource.groovy I can see the query), but when I crawl the association in my GSP, I can see that Hibernate is executing subsequent queries as if it were lazily loading the associations. I'm not convinced that the eager loading is actually working. I do not want to set lazy:false within my domain class for

How can I basically carry out a unique constraint on a string data-type field. class User{ String username String Email static hasMany = [roles:Roles] static constraints = { Email(email:true) username(unique:true) } } Is there any simple way to implement username(unique: true) Or must I manually check the database using methods like .findByNameLike ? The username should be unique, but the uniqueness is should be case-insensitive. So, if you want to have unique and case insensitive usernames, there are two possible approaches. The simple one: Store them upper or lower case and use the unique