Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue/2906 #2914

Merged
merged 6 commits into from
Jun 25, 2024
Merged

Issue/2906 #2914

merged 6 commits into from
Jun 25, 2024

Conversation

michael-simons
Copy link
Collaborator

No description provided.

michael-simons and others added 6 commits June 19, 2024 20:39
This will allow for the mapper to have only *one* physical relationship plus the original behaviour staying intact (creating two independent).

Required mapping is shown in the test.

Basic idea is to check if a relationship in the opposite direction with the actual *same* source and target entities has already been seen. If so, no batch update on the imperative path is scheduled.
Thus however will leave generated ids on the mapping classes unpopulated.
Those will be retrieved after the fact.

Also this won’t work for dynamic relationships with properties.
@michael-simons michael-simons merged commit 2e3edb8 into main Jun 25, 2024
1 check passed
michael-simons added a commit that referenced this pull request Jun 25, 2024
…2914)

This will allow for the mapper to have only *one* physical relationship plus the original behaviour staying intact (creating two independent).

Required mapping is shown in the test.

Basic idea is to check if a relationship in the opposite direction with the actual *same* source and target entities has already been seen. If so, no batch update on the imperative path is scheduled.
Thus however will leave generated ids on the mapping classes unpopulated.
Those will be retrieved after the fact.

---------
Co-authored-by: Gerrit Meier <[email protected]>
michael-simons added a commit that referenced this pull request Jun 25, 2024
…2914)

This will allow for the mapper to have only *one* physical relationship plus the original behaviour staying intact (creating two independent).

Required mapping is shown in the test.

Basic idea is to check if a relationship in the opposite direction with the actual *same* source and target entities has already been seen. If so, no batch update on the imperative path is scheduled.
Thus however will leave generated ids on the mapping classes unpopulated.
Those will be retrieved after the fact.

---------
Co-authored-by: Gerrit Meier <[email protected]>
@michael-simons michael-simons deleted the issue/2906 branch February 10, 2025 09:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants