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

Add sql slicing and make sort use a CTE so that the semantics are similar to numpy #1125

Merged
merged 17 commits into from Jun 11, 2015
Merged

Add sql slicing and make sort use a CTE so that the semantics are similar to numpy #1125

merged 17 commits into from Jun 11, 2015

Conversation

cpcloud
Copy link
Member

@cpcloud cpcloud commented Jun 11, 2015

closes #1072

@Will-So

This PR has all of your commits as well as a few extras to fix the order of
operations for sort on the SQL backend.

@cpcloud cpcloud mentioned this pull request Jun 11, 2015
@cpcloud
Copy link
Member Author

cpcloud commented Jun 11, 2015

cc @llllllllll this fixes the stuff we talked about on gitter regarding sort

@cpcloud cpcloud self-assigned this Jun 11, 2015
@cpcloud cpcloud added this to the 0.8.1 milestone Jun 11, 2015
def test_sort_compose():
expr = t.name[:5].sort()
result = compute(expr, s)
expected = """with anon_1 as (select accounts.name as name from accounts limit :param_1 offset :param_2) select anon_1.name from anon_1 order by anon_1.name asc"""
Copy link
Member Author

Choose a reason for hiding this comment

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

note to self: format this

cpcloud added a commit that referenced this pull request Jun 11, 2015
Add sql slicing and make sort use a CTE so that the semantics are similar to numpy
@cpcloud cpcloud merged commit 3ca9071 into blaze:master Jun 11, 2015
@cpcloud cpcloud deleted the sort-compose branch June 11, 2015 13:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Slicing on Interactive Data with SQL does not work
3 participants