Well it does when you consider that there might be no getter for a
field. With createFilter you could still filter the result list without
exposing direct access to the field via a getter.
Am 02.01.2017 um 08:52 schrieb Steve Ebersole:
Field-access would have zero bearing on this
On Mon, Jan 2, 2017 at 1:30 AM Christian Beikov
<christian.beikov(a)gmail.com <mailto:christian.beikov@gmail.com>> wrote:
Sounds good to me, but maybe we could do a poll to see if people are
using this? I don't know if the filter also works for field based
access
strategy, but that could be a reason for keeping it around.
Regards,
Christian
Am 31.12.2016 um 21:00 schrieb Steve Ebersole:
> As I have not been hearing hardly any feedback on these 6.0 design
> questions I have been trying to start, I'll be doing something
different in
> this and any additional emails.. I'll state what I propose to do
and if
> anyone has issue with it they can make a counter proposal.
Otherwise I
> plan on following through with my proposal.
>
> I plan on removing Session#createFilter. There are numerous
reasons why
> which I can discuss if anyone is interested in exploring this.
>
> Ultimately I think it makes sense to handle this via Java 8
streams[1]
> although I am not sure that needs to happen in 6.0
>
> [1]
https://hibernate.atlassian.net/browse/HHH-10962
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org <mailto:hibernate-dev@lists.jboss.org>
>
https://lists.jboss.org/mailman/listinfo/hibernate-dev
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org <mailto:hibernate-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/hibernate-dev