[hibernate-dev] Filter activation

[Steve Ebersole]

Let's keep this on-list, please.  Thanks!

The issue, to be clear, is not auto-enabling filters.. No, the
issues/concern is allowing enabled filters to be later disabled.

On Fri, Nov 13, 2015 at 8:34 AM Petar Tahchiev <paranoiabla at gmail.com>
wrote:

> Hello,
>
> I'm just chatting with the spring-boot guys now and they ask if hibernate
> allows you to specify the filters to activate in a property file. I guess
> they are interested in adding this functionality to spring-boot too.
>
> 2015-11-13 16:13 GMT+02:00 Steve Ebersole <steve at hibernate.org>:
>
>> Well not sure I said it is valid ;)  There are open questions such as the
>> one I brought up. For a proposal to be valid (as in possible) all such
>> questions need to have some answer.
>>
>> On Fri, Nov 13, 2015, 7:15 AM Petar Tahchiev <paranoiabla at gmail.com>
>> wrote:
>>
>>> Hi Steve,
>>>
>>> and thanks for your reply. I guess I have mis-understood what the real
>>> proposal was. Also, unfortunately I don't have enough knowledge of
>>> hibernate's internals and like you already mentioned this change will
>>> actually affect a lot of the code. My question was more to see what the
>>> hibernate team thinks about such a proposal, and if there was something
>>> totally against it. Now I know that it is a valid proposal and might be
>>> included one day in the pipeline.
>>>
>>> That's ok for me :)
>>>
>>>
>>>
>>> 2015-11-13 14:37 GMT+02:00 Steve Ebersole <steve at hibernate.org>:
>>>
>>> > Well I like this idea (additional flag on @Filter) better the actual
>>> > request (multi-valued config setting).  And what about for the
>>> > @FilterDef(inition)?
>>> >
>>> > One concern I have is, e.g., getting a collection with a filter
>>> enabled,
>>> > now disabling a filter and then initializing the collection.  That
>>> seems
>>> > like the outcome (the initialization will not be filtered) will not be
>>> what
>>> > was probably intended.  Filters were designed to be disabled by
>>> default and
>>> > only enable-able; so a change like this will challenge assumptions
>>> > throughout the code.
>>> >
>>> > Is this something you are volunteering to work on?
>>> >
>>> >
>>> > On Fri, Nov 13, 2015 at 5:25 AM Petar Tahchiev <paranoiabla at gmail.com>
>>> > wrote:
>>> >
>>> >> Hello,
>>> >>
>>> >> here's a 6-year old issue:
>>> >>
>>> >> https://hibernate.atlassian.net/browse/HHH-3815
>>> >>
>>> >> That suggests to add another attribute on the @Filter annotation
>>> >> (something
>>> >> like activeByDefault=true). Can we have your oppinion on it?
>>> >> --
>>> >> Regards, Petar!
>>> >> Karlovo, Bulgaria.
>>> >> ---
>>> >> Public PGP Key at:
>>> >> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x19658550C3110611
>>> >> Key Fingerprint: A369 A7EE 61BC 93A3 CDFF  55A5 1965 8550 C311 0611
>>> >> _______________________________________________
>>> >> hibernate-dev mailing list
>>> >> hibernate-dev at lists.jboss.org
>>> >> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>> >>
>>> >
>>>
>>>
>>> --
>>> Regards, Petar!
>>> Karlovo, Bulgaria.
>>> ---
>>> Public PGP Key at:
>>> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x19658550C3110611
>>> Key Fingerprint: A369 A7EE 61BC 93A3 CDFF  55A5 1965 8550 C311 0611
>>> _______________________________________________
>>> hibernate-dev mailing list
>>> hibernate-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>>
>>
>
>
> --
> Regards, Petar!
> Karlovo, Bulgaria.
> ---
> Public PGP Key at:
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x19658550C3110611
> Key Fingerprint: A369 A7EE 61BC 93A3 CDFF  55A5 1965 8550 C311 0611
>