New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JPA 2.1 capabilities #658

Closed
ldez opened this Issue Feb 9, 2014 · 11 comments

Comments

Projects
None yet
4 participants
@ldez

ldez commented Feb 9, 2014

Add support for Hibernate 4.3.x.
Add also support of new JPA 2.1 capabilities, ex : treat for .as(Class) when entities are joined.

@timowest

This comment has been minimized.

Show comment
Hide comment
@timowest

timowest Feb 10, 2014

Member

Which specific Hibernate 4.3 and JPA 2.1 features would you like to see supported?

Member

timowest commented Feb 10, 2014

Which specific Hibernate 4.3 and JPA 2.1 features would you like to see supported?

@ldez

This comment has been minimized.

Show comment
Hide comment
@ldez

ldez Feb 10, 2014

Thank you for your interest.
I speak of Hibernate 4.3.x support but actually it's only JPA 2.1 support that interest me.
Allow me a few days to define more precisely the elements.

At first, support TREAT in the case of inheritance between two entities associated with JOINED.
ex : root.book.as(QManga.class).drawer.eq("foobar")

ldez commented Feb 10, 2014

Thank you for your interest.
I speak of Hibernate 4.3.x support but actually it's only JPA 2.1 support that interest me.
Allow me a few days to define more precisely the elements.

At first, support TREAT in the case of inheritance between two entities associated with JOINED.
ex : root.book.as(QManga.class).drawer.eq("foobar")

@timowest

This comment has been minimized.

Show comment
Hide comment
@timowest

timowest Mar 20, 2014

Member

@ldez What is the (full) list of JPA 2.1 features that could/should be supported?

Member

timowest commented Mar 20, 2014

@ldez What is the (full) list of JPA 2.1 features that could/should be supported?

@timowest

This comment has been minimized.

Show comment
Hide comment
@timowest

timowest Apr 9, 2014

Member

@ldez I made TREAT support now available in this pull request #705

Could you take a look and maybe review?

Member

timowest commented Apr 9, 2014

@ldez I made TREAT support now available in this pull request #705

Could you take a look and maybe review?

@timowest timowest added this to the 3.3.4 milestone Apr 30, 2014

@timowest timowest added the fixed label May 4, 2014

@timowest timowest modified the milestone: 3.3.4 May 10, 2014

@timowest timowest changed the title from Hibernate 4.3.x and JPA 2.1 capabilities to JPA 2.1 capabilities May 10, 2014

@timowest

This comment has been minimized.

Show comment
Hide comment
@timowest

timowest May 10, 2014

Member

I updated the title to better reflect what has been done for it.

Member

timowest commented May 10, 2014

I updated the title to better reflect what has been done for it.

@timowest

This comment has been minimized.

Show comment
Hide comment
@timowest

timowest May 20, 2014

Member

Released in 3.3.4

Member

timowest commented May 20, 2014

Released in 3.3.4

@timowest timowest closed this May 20, 2014

@ldez

This comment has been minimized.

Show comment
Hide comment
@ldez

ldez May 22, 2014

Good work, sorry for not replying sooner but I had a lot of work.

ldez commented May 22, 2014

Good work, sorry for not replying sooner but I had a lot of work.

@virgo47

This comment has been minimized.

Show comment
Hide comment
@virgo47

virgo47 Feb 24, 2016

Sorry for asking in the closed issue, but Google search for "Querydsl JPA 2.1 FUNCTION" lead me here. I see that TREAT is in Querydsl, but I don't understand what the status of FUNCTION is, and if it is in, how it should be used (search through Reference did not help).

virgo47 commented Feb 24, 2016

Sorry for asking in the closed issue, but Google search for "Querydsl JPA 2.1 FUNCTION" lead me here. I see that TREAT is in Querydsl, but I don't understand what the status of FUNCTION is, and if it is in, how it should be used (search through Reference did not help).

@virgo47

This comment has been minimized.

Show comment
Hide comment
@virgo47

virgo47 Feb 24, 2016

Seems I needed to ask (after a long search, mind you :-)), after the question I got it in a minute, as it is not strictly tied to JPA 2.1, but more to Querydsl templates:
http://stackoverflow.com/questions/22984343/how-to-call-mysql-function-using-querydsl

So we should just use Expressions.xxxTemplate depending on the type and write function(real_function) template ourselves.

virgo47 commented Feb 24, 2016

Seems I needed to ask (after a long search, mind you :-)), after the question I got it in a minute, as it is not strictly tied to JPA 2.1, but more to Querydsl templates:
http://stackoverflow.com/questions/22984343/how-to-call-mysql-function-using-querydsl

So we should just use Expressions.xxxTemplate depending on the type and write function(real_function) template ourselves.

@Shredder121

This comment has been minimized.

Show comment
Hide comment
@Shredder121

Shredder121 Feb 24, 2016

Member

Yes, that would be right.
Don't forget to also make your functions known to the JPA provider.

Member

Shredder121 commented Feb 24, 2016

Yes, that would be right.
Don't forget to also make your functions known to the JPA provider.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment