On Thu, 9 Aug 2018 at 16:00, Steve Ebersole wrote:
>
> "Maven repository" is any thing we want it to be, even a locally hosted repo
> manager into which we can install any dependencies we want - so it is not
> available in any "public" repo, but still referrable via normal Gradle means.
> Seem
"Maven repository" is any thing we want it to be, even a locally hosted
repo manager into which we can install any dependencies we want - so it is
not available in any "public" repo, but still referrable via normal Gradle
means. Seems by far easier solution...
On Thu, Aug 9, 2018 at 9:42 AM Sann
In 6.0 HQLQueryPlan is replaced by AggregatedSelectQueryPlanImpl[1]
(polymorphic queries) and ConcreteSqmSelectQueryPlan[2].
ConcreteSqmSelectQueryPlan holds a reference to the SQM AST;
AggregatedSelectQueryPlanImpl
hold 2+ ConcreteSqmSelectQueryPlans. AggregatedSelectQueryPlan operates
much like
I'm setting up some new Oracle integration tests on ci.hibernate.org,
and we're having again a similar issue to what we had with SAP HANA:
- some JDBC drivers can not be distributed freely
- we do not want to allow the Hibernate ORM build to load
dependencies from a local Maven repository
So I'
Hi,
>From what I can see, the HQLQueryPlan objects are rather big, mostly due to
the sqlAst element of the QueryTranslators.
They can consume a fair amount of memory when you have a lot of HQL queries.
We need at least some of the information collected by the AST but I'm
wondering if we really n
