Skip to content

Non-inverse no-proxy one-to-one are eager loaded #1960

Open
@fredericDelaporte

Description

@fredericDelaporte

A non-inverse one-to-one mapped as lazy="no-proxy" is not actually lazy, it is eager loaded.

This is not the same than #1087, which is about the lazy="proxy" case, which is considered invalid on an non-inverse end. But the case here is supposed to be the valid way of having a non-inverse one-to-one lazy.

This trouble is see-able with LazyOneToOneTest.Lazy. The test does not fail to date due to a subsequent bug, but if checking the emitted SQL query, we can see that the one-to-one was eagerly loaded.

#1947 exposes this trouble more obviously by fixing the subsequent bug, see these comments.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions