On Tue, Aug 18, 2015 at 08:59:28AM +0200, Gunnar Morling wrote: > >> One possible workaround is to enforce the indexNullAs value to match the > >> underlying field type, at the > >> moment it is always a string. > > > > Interesting idea, but the user would need to provide which "value" > > he's ok to give up, as he would need to pick a number to be treated as > > NaN. > > Since the indexNullAs parameter requires a string, would we expect > > people to write a number in there? > > +1 for that idea.
+1 as well > Isn't that what's happening already atm.? If a value is null (and > indexNullAs() is *not* given), it will not be part of the index as per > my observations. But if it is null and indexNullAs() is given, that > token will be used. That seems like the right thing to do IMO. Esp. I > would not ignore indexNullAs() if given, apparently the user meant to > encode null in that case e.g. to use it in queries. Right, that the intended behavior. If it behaves differently right now a regression has sneaked in. --Hardy
pgpIal__eiIOv.pgp
Description: PGP signature
_______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
