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 <paranoia...@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@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
