To be clear, I do not mean moving the method from Session to Query. More as a user you would convert the call from Session#createFilter to Session#createQuery
The "intent" of this #createFilter call is better served design-wise as a stream/filter on the collection. On Mon, Sep 12, 2016 at 12:41 AM Vlad Mihalcea <mihalcea.v...@gmail.com> wrote: > I agree. The createFilter can be moved to the Query, so we don't require > this to be in the Session interface. > > I haven't seen many questions about this functionality, so I guess we > shouldn't worry to much about this change. > > Vlad > > On Mon, Sep 12, 2016 at 6:02 AM, Steve Ebersole <st...@hibernate.org> > wrote: > >> Another method I'd like to drop is Session#createFilter. This is method >> is >> easy enough to replace with a call to createQuery instead. Longer term I >> can also see Stream or DSL support from our persistent collections to >> provide the similar capabilities. But for now its just no real benefit >> for >> the cost of overly-complicating the grammars. >> > _______________________________________________ >> hibernate-dev mailing list >> hibernate-dev@lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hibernate-dev >> > > _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev