Details
-
Type:
Improvement
-
Status:
Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: 1.3.5
-
Fix Version/s: None
-
Component/s: Documentation
-
Labels:None
Description
given a case like this
Building.withCriteria {
jobs { tasks {} }
projections {
groupProperty "name"
groupProperty "id"
sum "tasks_alias2.cost"
sum "tasks_alias2.duration"
}
}
it comes very handy to know that
- grails criteria defaults to a left join on associations and
- creates the aliases with names like associationPropertyName + "_alias" + "aliasNumber" where aliasNumber is starting with 1 and is incremented in the order the HibernateCriteriaBuilder builds the criteria...
Issue Links
- is related to
-
GRAILS-7152
Document createAlias usage in GORM Criteria queries
-
Activity
Peter Ledbrook
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Peter Ledbrook [ pledbrook ] |
Contegix Support
made changes -
| Project Import | Thu Mar 24 21:22:24 CDT 2011 [ 1301019744151 ] |
Burt Beckwith
made changes -
| Workflow | jira [ 31984 ] | Grails [ 40287 ] |
Burt Beckwith
made changes -
| Workflow | Grails [ 40287 ] | Copy of Grails [ 47719 ] |
Burt Beckwith
made changes -
| Workflow | Copy of Grails [ 47719 ] | Grails [ 55129 ] |
Burt Beckwith
made changes -
| Workflow | Grails [ 55129 ] | Grails2 [ 62680 ] |
Peter Ledbrook
made changes -
| Link | This issue is related to GRAILS-7152 [ GRAILS-7152 ] |
Burt Beckwith
made changes -
| Workflow | Grails2 [ 62680 ] | jira [ 77684 ] |
Burt Beckwith
made changes -
| Workflow | jira [ 77684 ] | Grails2 [ 86037 ] |
Peter Ledbrook
made changes -
| Last Reviewed | 01/Jan/10 |
Peter Ledbrook
made changes -
| Workflow | Grails2 [ 86037 ] | jira [ 94418 ] |
Peter Ledbrook
made changes -
| Workflow | jira [ 94418 ] | Grails2 [ 102564 ] |
We definitely need a better way of doing this
The aliases are obviously not designed to be used directly by developers, but I guess that should be a separate issue.