Skip to content

Validate that a ManyToOne is not used as single field in an id. #12427

@stof

Description

@stof

Feature Request

What

when using a ManyToOne relation as the id of the entity without making it part of a composite key, this effectively turns the relation into a OneToOne.

Why

This got reported on Slack by someone forgetting to put the Id attribute on the other field expected to be part of their composite key.

How

The schema validator should report an error in this case to make debugging easier.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions