Hi Steven,
I'm trying to integrate FlexyPool ( https://github.com/vladmihalcea/flexy-pool
) with Java EE Application servers, and the only work-around I found is to add
a new Hibernate ConnectionProvider that extends the
DataSourceConnectionProvider and exposes a DataSource proxy, instead of the
That comment is
in
org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl#applyJdbcConnectionProperties.
The more important calls are the ones right before those #put calls. The
ones to StandardServiceRegistryBuilder#applySetting. Those are the
settings that ultimately will get passed t
>
> I know personally, time/resources aside, the biggest reason I have not
> worked a lot on the bigger task (other than my initial work on the new
> query parser) is because I had hoped a solution would present itself to the
> Antlr 4 quandary. But it hasn't and likely wont and I think Gunnar and
>
> - since I'm currently exploring the 2nd level cache keys and the
> persistence context keys again, it's getting clear (again as we
> discussed this before) to potentially use a different data structure
> to hold the persistence context.
>
The persistence context holds a lot of data, a lot of
Here is a list of tasks, with dependent tasks nested under the tasks they
depend on...
1. rework SQL generation & HQL parser
1. change JDBC extraction to work by position, rather than alias
2. port Hibernate Criteria constructs to JPA criteria, begin
deprecation of Hibernate
Wow, the formatting on that came out awful. One more try
1. rework SQL generation & HQL parser
1. change JDBC extraction to work by position, rather than alias
2. port Hibernate Criteria constructs to JPA criteria, begin
deprecation of Hibernate Criteria
3. ability to over
