Don't invoke parseQuery() prior to schema initializer has been run

Description

Something seems odd regarding the timing of named query validation and triggering the schema initializer which run in that order. This gives issues on Cassandra, which cannot validate queries without the schema in place.

Ties into the change we have in mind to piggy-back on ORM's HBM2DDL setting instead of providing our own one.

Environment

None

Activity

Show:
Gunnar Morling
January 20, 2016, 12:23 PM

It's caused by the fact that a session factory listener is used to invoke schema definers. That's tool late, as query validation will be run by then already. Instead we'd have to trigger schema definers through a custom SchemaManagementTool implementation which happens at the right time.

Assignee

Gunnar Morling

Reporter

Gunnar Morling

Labels

None

Feedback Requested

None

Feedback Requested By

None

backPortable

None

Suitable for new contributors

None

Pull Request

None

backportDecision

None

backportReEvaluate

None

Components

Fix versions

Priority

Major
Configure