-
Notifications
You must be signed in to change notification settings - Fork 21.6k
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
Make sure that JSON arrays as columns working #14685
Conversation
Would you mind squashing your commits down to single commit? @senny would you mind reviewing this patch? |
Oh right, sorry, I hadn't commented here... this is still in progress. |
@scuxiayiqian : If you want, you can run the following outside of your rails clone:
The rebase process is available on the contributing guide. Also this can be hard to rebase against the |
@scuxiayiqian did you get time to fix this big list of commits? And fix this PR? Can we close this one if you are going to do another PR for the same? |
Yes. I made some mistakes while doing something push thing. Please close this one and I'll do another PR. |
@scuxiayiqian please do not open a new PR, we only loose the discussion that's here already. You can clean up this PR without creating a new one. The only thing that can't be fixed, is changing the target branch. However that one looks good, so let's stick to this PR. Simply arrange the commits locally as you want them to be in the PR. Then you need to force-push them to your fork like so:
Just replace |
@scuxiayiqian : ATM, you just need to run |
This behavior is covered by the test #28295. |
scuxiayiqian@a0453b8 fixed the bug #14484