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.

Sign up for GitHub

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

Jump to bottom

Implement proper one-to-one support #198

Closed
beikov opened this issue Mar 17, 2016 · 0 comments
Closed

Implement proper one-to-one support #198

beikov opened this issue Mar 17, 2016 · 0 comments
Assignees
@beikov
Labels
component: core kind: enhancement
Milestone
1.2.0

Comments

@beikov
Copy link
Member

beikov commented Mar 17, 2016

Currently we have some TODOs in the code for one-to-one mappings.

One example is the determination of the foreign key column location for to-one mappings to decide if a join is necessary to use the id of the relation. Knowing the location can make it possible to avoid a join.
@beikov beikov self-assigned this Mar 17, 2016
@beikov beikov added this to the 1.1.1 milestone Mar 17, 2016
@beikov beikov modified the milestones: 1.2.0, 1.1.1 Aug 1, 2016
beikov added a commit to beikov/blaze-persistence that referenced this issue Mar 15, 2017
@beikov
Fixed Blazebit#198 - Added detection of the join column source to be …
eddce8d 
…able to determine if single valued association ids should be rendered
beikov added a commit to beikov/blaze-persistence that referenced this issue Mar 15, 2017
@beikov
Fixed Blazebit#198 - Added detection of the join column source to be …
57f66b1 
…able to determine if single valued association ids should be rendered
@beikov beikov closed this as completed in 3e12fa1 Mar 16, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@beikov beikov

Labels
component: core kind: enhancement
Projects
None yet
Milestone
1.2.0
Development

No branches or pull requests
1 participant
@beikov