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

Conflicting table references #23

Closed
MrSwitch opened this issue Dec 17, 2017 · 1 comment
Closed

Conflicting table references #23

MrSwitch opened this issue Dec 17, 2017 · 1 comment

Comments

@MrSwitch
Copy link
Member

MrSwitch commented Dec 17, 2017

In the below example both are saying they reference the other, in reality the reference should be defined in the joining table, aka the one which is not holding the unique value/primary key, aka the second one.

{
    assets: {
         id: 'assetCollections.asset_id'
    },
    assetCollections: {
         asset_id: 'assets.id'
    }
}

This causes alot of conflicting results including broken responses

@MrSwitch
Copy link
Member Author

Not specified approach, closing

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

No branches or pull requests

2 participants