HQL Console uses Hibernate as persistence provider no matter what provider is set for persistence unit. It actually forces JPQL for all PUs with provider other than hibernate.
Awesome. Except we're using Eclipselink and not Hibernate. And as much as I'd like to believe the behavior is going to be identical across JPA implementations, I don't.
I understand your point. The generic JPA QL console is not available. For the time being you can try the `hibernate` one. Just add hibernate jars to the module class path. I'd like to know the results of this experiment on live project.
Gregory Shrago
On 01.04.2010 18:46, Tim McNerney wrote:
Awesome. Except we're using Eclipselink and not Hibernate. And as much as I'd like to believe the behavior is going to be identical across JPA implementations, I don't.
I did just that, but the console does not work for me because my object model is one that Hibernate does not understand. This is not unexpected as my attempts to transparently switch providers from EL to Hibernate failed for just this reason.
We are using JPA Query Tool, which seems to work fine. It would just be nice to have something integrated into Idea.
I did just that, but the console does not work for me because my object model is one that Hibernate does not understand. This is not unexpected as my attempts to transparently switch providers from EL to Hibernate failed for just this reason.
>
We are using https://jpaquerytool.dev.java.net/, which seems to work fine. It would just be nice to have something integrated into Idea.
HQL Console uses Hibernate as persistence provider no matter what
provider is set for persistence unit. It actually forces JPQL for all PUs with
provider other than hibernate.
This might be useful:
http://blogs.jetbrains.com/idea/2009/03/hql-console-with-pure-jpa-facets/
On 01.04.2010 1:16, Tim McNerney wrote:
>
>
Awesome. Except we're using Eclipselink and not Hibernate. And as much as I'd like to believe the behavior is going to be identical across JPA implementations, I don't.
--Tim
I understand your point. The generic JPA QL console is not available.
For the time being you can try the `hibernate` one.
Just add hibernate jars to the module class path.
I'd like to know the results of this experiment on live project.
Gregory Shrago
On 01.04.2010 18:46, Tim McNerney wrote:
>
>
I did just that, but the console does not work for me because my object model is one that Hibernate does not understand. This is not unexpected as my attempts to transparently switch providers from EL to Hibernate failed for just this reason.
We are using JPA Query Tool, which seems to work fine. It would just be nice to have something integrated into Idea.
Thanks for the info.
--Tim
http://youtrack.jetbrains.net/issue/IDEA-55361
On 06.04.2010 21:28, Tim McNerney wrote:
>
>
>
>
Awesome. Thanks. I'm assuming this will be for 9.0.3?
--Tim