Hi,
Still trying to get one of our applications starting with ORM 5. With
Search 5.4.0.Beta1 and Spring 4.2.0.RC1, I'm now at the database schema
validation phase.
I think there's something fishy with the way a table is looked for when
we're using specific schemas in our database.
Some backgroun
FWIW, if I change the return ""; to return null;, I get my application to
start \o/.
I'll start testing the application more in depth.
FWIW, I don't know if it's something normal but
AvailableSettings.DEFAULT_SCHEMA is not used in the constructor of
JdbcEnvironmentImpl used when JDBC is available
Steve,
I missed you ping yesterday about HHH-9857. I reworked based on the
EntityEntry needing to be threadsafe to be shared across sessions. With
the current impl a new EntityEntry is created for each
PeristenceContext. If we share it between sessions, there is a race
condition on the compres
Hi Guillaume.
The trouble with the way it used to work is that we are essentially looking
at tables from all catalogs/schemas. That is the difference between "" and
null in those DBMD params. This causes problems in a few different
situations. First is the case of simply having more than one ta
As for the "multi-select" case you mention, JPA actually does not mention
support for TREAT in select clauses. In fact it explicitly lists support
for TREAT in the from and where clause. So because it explicitly mentions
those, I'd say it implicitly excludes support for them in select clause.
T
Test from new Nabble gateway
--
View this message in context:
http://hibernate-development.74578.x6.nabble.com/Test-from-Nabble-tp3.html
Sent from the Hibernate Development mailing list archive at Nabble.com.
___
hibernate-dev mailing list
hibernate-d
I am not so sure that manually building a tree that would work with
listeners/visitors generated from a second grammar is going to be an
option. I have asked on SO and on the Antlr discussion group and basically
got no responses as to how that might be possible. See
https://groups.google.com/foru
See below:
- Original Message -
> From: "Steve Ebersole"
> To: "Gail Badner" , "Hibernate Dev"
>
> Sent: Tuesday, June 16, 2015 11:00:49 AM
> Subject: Re: [hibernate-dev] TREAT operator and joined inheritance (HHH-9862)
>
> As for the "multi-select" case you mention, JPA actually does
