#1672 closed enhancement (fixed)
Join annotation values into a main item query
Reported by: | Nicklas Nordborg | Owned by: | Nicklas Nordborg |
---|---|---|---|
Priority: | major | Milestone: | BASE 3.2 |
Component: | core | Version: | |
Keywords: | Cc: |
Description (last modified by )
By mapping a few extra associations in the data layer classes it should be possible to join the annotation value tables into the main item query. The main use case is that it would be possible to sort on single-valued annotation values in the web interface (see #1673).
Change History (5)
comment:1 by , 13 years ago
Description: | modified (diff) |
---|
comment:2 by , 13 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:3 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:4 by , 13 years ago
(In [6045]) References #1672: Define extension points for adding columns to table listings
Implemented for all list pages in the Administrate menu.
Version 0, edited 13 years ago by (next)
comment:5 by , 12 years ago
Note:
See TracTickets
for help on using tickets.
(In [6022]) Fixes #1672: Join annotation values into a main item query
There is now support for this in the Query API. The main entry point is the
Annotations.expression()
,Annotations.innerJoin()
andAnnotations.leftJoin()
methods. The implementation is in theAnnotationJoin
andAnnotationExpression
classes. The expression variant uses an auto-joiner to automatically create the correct join. Otherwise, an explict join can be use together with a regularHql.alias()
expression.In the data layer, the functionality is provided by the shortcut link defined by
AnnotatableData.getAnnotations()
. TheAnnotationLink
provides the mappings that are needed to reach the final***Values
table. To get XDoclet to create the mapping that we needed we have added support forproperty-ref
andmutable
.