From a performance perspective, I'm glad we'll be able to
override the EAGER fetching on a query-basis. We could have an UNFETCH directive to do the
opposite of the current FETCH one.
The bytecode enhancement dirty-checking is also a plus.
Vlad
On Friday, May 29, 2015 11:09 AM, Emmanuel Bernard <emmanuel(a)hibernate.org>
wrote:
Also (thinking outloud).
Maybe planning 5.1 5.2 5.x as a savant dosage of:
- a focused and useful new feature that users tend to like (discriminator-based
multi-tenancy, fluent criteria API, …)
- a performance focused feature (position rather than alias usage in JDBC)
- a longer term work plan which might span several minors to be achieved (SQL generation
& hQL parser, …)
One of each per 5.x might be interesting to explore.
On 29 May 2015, at 09:58, Emmanuel Bernard
<emmanuel(a)hibernate.org> wrote:
My favs are
* discriminator-based multi-tenancy
* extend JPA criteria API with fluent support (does that mean embracing something like
http://www.querydsl.com ? Os is that something different?
* rework SQL generation & HQL parser
> On 28 May 2015, at 18:33, Steve Ebersole <steve(a)hibernate.org> wrote:
>
> Anyone have any input here? Or should I just start scheduling them how I
> want?
>
> On Tue, May 19, 2015 at 8:47 PM, Steve Ebersole <steve(a)hibernate.org> wrote:
>
>> Now that 5.0 is settling down I wanted to start planning where we go from
>> here in terms of feature development and schedule/releases.
>>
>> Here is my high-level list of features/work:
>> * rework SQL generation & HQL parser
>> * change JDBC extraction to work by position, rather than alias (reworking
>> SQL generation is a prerequisite)
>> * rework annotation binding (Jandex, etc)
>> * extended orm.xml, deprecate hbm.xml
>> * discriminator-based multi-tenancy
>> * port Hibernate Criteria constructs to JPA criteria, begin deprecation of
>> Hibernate Criteria
>> * extend JPA criteria API with fluent support
>> * ability to override EAGER fetching with LAZY (fetch profiles, HQL, etc)
>> * merging hibernate-entitymanager into hibernate-core
>> * continue to fill out bytecode enhancement capabilities
>>
>> Some of these are more involved than others. The task for re-writing SQL
>> generation is a HUGE undertaking, but also has many huge benefits.
>> Re-writing annotation binding is another huge undertaking, but again with
>> many benefits.
>>
>> Any others we should add to the list here?
>>
>> And then we can work on scheduling them.
>>
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/hibernate-dev
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev