On 23 February 2016 at 19:26, Guillaume Smet wrote:
> On Tue, Feb 23, 2016 at 7:21 PM, Sanne Grinovero
> wrote:
>>
>> I don't have a strong opinion on the usefulness on faceting on null;
>> would someone have a sensible example of faceting on a "null value" ?
>>
>> We can fix it but I have the im
On Tue, Feb 23, 2016 at 7:21 PM, Sanne Grinovero
wrote:
> I don't have a strong opinion on the usefulness on faceting on null;
> would someone have a sensible example of faceting on a "null value" ?
>
> We can fix it but I have the impression it's just about fixing a
> developer's itch because of
I don't have a strong opinion on the usefulness on faceting on null;
would someone have a sensible example of faceting on a "null value" ?
We can fix it but I have the impression it's just about fixing a
developer's itch because of it being inconsistent with other
components; if it helps with Elas
Hi,
While looking at HSEARCH-1917 which is an issue with faceting and null
values, I came up with the following observations:
1/ Faceting doesn't take into account indexNullAs
2/ Faceting doesn't take into account FieldBridges
1/
In HSEARCH-1917, Hardy talked about supporting indexNullAs.
Does
Well first I'd probably ask on user communication channels, not the
developer mailing list. That said, have you read the User Guide,
especially the revamped User Guide in 5.1?
On Tue, Feb 23, 2016 at 7:13 AM Adriano Santos
wrote:
> First all, where (exactly) can I get the correct way to mapping
First all, where (exactly) can I get the correct way to mapping all the
relations? We are always finding many differents mapping forms and this can
be terrible to beginners. I still dont know if we have some tutorial or
book like that, but I'd like... Anybody here knows?
Este e-mail foi enviado po
Well first, technically isn't that mapping incorrect? That should use
@CollectionTable rather than @JoinTable. I am not sure that makes a
difference, but in the interest of mapping things properly...
That being said... the whole premise of the legacy EJB3NamingStrategy was
to prefer the use of t
To be honest I cannot make up my mind to decide which behavior is more correct.
I can see both as valid.
> On 22 Feb 2016, at 18:07, Steve Ebersole wrote:
>
> It is also important to understand that lots of Hibernate code calling into
> NamingStrategy did so in quite inconsistent ways. We deci
