Do we need Hibernate 5 to resolve those type system issues?
If so, is there an alternative solution which wouldn't necessarily
couple the OGM lifecycle with ORM ? (just for the time being)
On 4 December 2012 18:19, Emmanuel Bernard <emmanuel(a)hibernate.org> wrote:
Moving to dev mailing list.
On Tue 2012-12-04 12:09, Steve Ebersole wrote:
> Can we have such discussions on the dev list?
>
> Anyway, that's why I said about developing the parser separately but in
> tandem and synching later. That gives us that flexibility.
>
> Because it's not been decided that the parser change will even go into
> 5.0...
> On Dec 4, 2012 11:35 AM, "Emmanuel Bernard" <emmanuel(a)hibernate.org>
wrote:
>
> > Hey guys,
> >
> > Steve and I started a discussion on how to reuse Sanne's work around the
> > new JP-QL parser. The crux of the problem is to be able to reuse the type
> > of a given node in the parser even if Hibernate ORM and Hibernate OGM use a
> > different type system. This looks doable but then the problem of timing
> > arises.
> >
> > With Davide coming onboard, and even more after BV is behind us, I expect
> > OGM to speed up significantly which means we will need to do fast releases.
> > So the question is when are we targeting Hibernate ORM 5 final and does
> > that fit Hibernate OGM's time goals.
> >
> > We have been promising query for ever now and I would hate to have to
> > delay it more than necessary.
> >
> > Thoughts?
> >
> > Emmanuel
> >
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev