QueryBuilder should support specialization by superclasses of indexed entities

Activity

Show:

Emmanuel BernardMay 30, 2013 at 5:00 PM

It is allowed in so far as for a given @Indexed class we look up the hierarchy to find @Field properties.

Gunnar MorlingMay 30, 2013 at 2:50 PM

Ah, so there can be an entity without @Indexed but with @Field? I assumed that wouldn't be allowed.

Emmanuel BernardMay 30, 2013 at 2:27 PM

No if Base is not marked as @Indexed, there will be no index binding for it.

Gunnar MorlingMay 30, 2013 at 2:13 PM

That means it's a partial fix right? If the superclass happens to host a @Field property we could have it work.

But wouldn't be there an entity index binding for the super class if it has such a property? The problem I came across when there was no index binding at all. So I would assume that this case already works, but I'll add a test case for this.

Emmanuel BernardMay 30, 2013 at 2:04 PM

That means it's a partial fix right? If the superclass happens to host a @Field property we could have it work.

If as I proposed, we look for a subclass of Base that is indexed, in this case Detail, we have the best of both worlds/.

Fixed

Details

Assignee

Reporter

Labels

Components

Fix versions

Priority

Created March 3, 2011 at 3:41 PM
Updated August 2, 2013 at 11:49 AM
Resolved June 7, 2013 at 12:56 PM