setFetchMode() ignore incorect path

Description

In a criteria, call to setFetchMode() with an incorect path don't throw any exception. Hibernate just ignore it.

That mean that some optimisation we expect won't append, and because of lazy initialization, everything may look to work fine, except it will run much slower.

Adrien

Environment

None

Status

Assignee

Gail Badner

Reporter

Adrien

Fix versions

None

Labels

None

backPortable

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

Components

Affects versions

Priority

Major
Configure