Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects versions: 3.2.0.ga, 3.5.5, 3.6.0.Beta3
    • Fix versions: None
    • Labels:
      None
    • Last commented by a user?:
      true
    • Sprint:

      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

        Attachments

          Issue links

            Activity

              People

              • Votes:
                3 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated: