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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix SQL query where oneWay relationship is null #2687

Merged
merged 4 commits into from Jan 24, 2019
Merged

Conversation

Aurelsicoko
Copy link
Member

My PR is a:

  • 馃挜 Breaking change
  • 馃悰 Bug fix #issueNumber
  • 馃拝 Enhancement
  • 馃殌 New feature

Main update on the:

  • Admin
  • Documentation
  • Framework
  • Plugin

Manual testing done on the follow databases:

  • Not applicable
  • MongoDB
  • MySQL
  • Postgres

Description:

I fixed the SQL query that allows retrieving multiple entries through GraphQL, there was a bug when a oneWay relationship was null.

@lauriejim lauriejim self-requested a review January 24, 2019 10:21
@lauriejim lauriejim self-assigned this Jan 24, 2019
@lauriejim lauriejim added pr: 馃悰 Bug fix source: core:content-manager Source is core/content-manager package labels Jan 24, 2019
@lauriejim lauriejim added this to the 3.0.0-alpha.22 milestone Jan 24, 2019
@lauriejim lauriejim added this to 馃暟Waiting for classification in 馃Cooking via automation Jan 24, 2019
@lauriejim lauriejim moved this from 馃暟Waiting for classification to 馃惪For next release in 馃Cooking Jan 24, 2019
Copy link
Contributor

@lauriejim lauriejim left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@derrickmehaffy
Copy link
Member

#2396

@greatwitenorth
Copy link
Contributor

I'm still seeing NULL on deep nested relations:

screenshot 2019-01-28 16 08 36

@lauriejim
Copy link
Contributor

@greatwitenorth What is the version of strapi you use to test it ?
alpha.21 or the mono repo ?

@greatwitenorth
Copy link
Contributor

greatwitenorth commented Jan 30, 2019

This is alpha 20 with the specific changes done from this pull request. I can try updating to 21 today to see if that fixes anything.

@lauriejim
Copy link
Contributor

Yes please. And make sur you apply update of this PR.

@greatwitenorth
Copy link
Contributor

After updating to Alpha 21 and applying the patches in this update I'm now seeing empty result sets for ALL nested relations when I know for certain there's related data:

Deeply nested data:
screenshot 2019-01-31 15 13 54

Nested data:
screenshot 2019-01-31 15 16 46

@lauriejim
Copy link
Contributor

Can you give us models you use (to have the relation type and test it on our side)

@greatwitenorth
Copy link
Contributor

You can ignore my issue, after updating to alpha 22 everything seems to be working correctly now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
source: core:content-manager Source is core/content-manager package
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants