Well not being this very urgent I'm going to create two JIRAs, on it,
one for the norms, and one for possibly changing the storage of the
optional field.
just wanted to mention it as while debugging I found it surprising behaviour.
*But* your last sentence got me a weird idea.
Nowadays if you hav
2011/3/15 Emmanuel Bernard :
>
> On 15 mars 2011, at 16:43, Sanne Grinovero wrote:
>
>> I guess we should prevent the indexing of ids in secondary elements?
>
> If the associated element is an entity, it's perfectly valid to index its id
> and query by it
>
> //return all books when the author's i
On 15 mars 2011, at 18:24, Emmanuel Bernard wrote:
>
> On 15 mars 2011, at 16:43, Sanne Grinovero wrote:
>
>> I guess we should prevent the indexing of ids in secondary elements?
>
> If the associated element is an entity, it's perfectly valid to index its id
> and query by it
>
> //return a
On 15 mars 2011, at 16:43, Sanne Grinovero wrote:
> I guess we should prevent the indexing of ids in secondary elements?
If the associated element is an entity, it's perfectly valid to index its id
and query by it
//return all books when the author's id is 2
"author.id:2"
_
2011/3/15 Emmanuel Bernard :
> Are you talking about JPA entities (with @Entity and @Id or mere mortal POJOs?
I got a bit confused for the reasons of your question, so I made some tests.
The index state reported in the previous email was about annotation
mapped entities, I repeated
the same test o
Are you talking about JPA entities (with @Entity and @Id or mere mortal POJOs?
On 14 mars 2011, at 21:26, Sanne Grinovero wrote:
> Hello,
> while debugging I just noticed that having a two entities scenario like
>
> @Indexed class Book {
> Long id;
> @IndexedEmbedded Nation bublishedFirstIn;
> }
Hello,
while debugging I just noticed that having a two entities scenario like
@Indexed class Book {
Long id;
@IndexedEmbedded Nation bublishedFirstIn;
}
Nation { //NOT indexed
Long id;
@Field name
}
the index for Book will contain these fields:
_hibernate_class - NOT_ANALYZED_NO_NO
