-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
Using astropy's PyVO to make URL calls. #129
Conversation
Co-authored-by: Nabil Freij <[email protected]>
sunpy_soar/client.py
Outdated
return qrt | ||
|
||
def add_join_to_query(query: list[str], data_table: str, instrument_table: str): | ||
""" | ||
Construct the WHERE, FROM, and SELECT parts of the ADQL query. | ||
Construct the WHERE, FROM, and SELECT parts of the SQL query. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't understand, before it was URL-encoded ADQL, now it is just ADQL. Transforming the +s to spaces don't make this SQL.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alrighty, makes sense!
Following this comment on the parent issue #32, TapPlus now recommends to use PyVO instead. Most of line changes in this PR were to make the ADQL queries non-URL-escaped. The transition to PyVO should then not be too difficult as a next step. Shall we do this? (and then change the title of the PR) |
Yes we should do that. |
Yep sounds good, also I wanted to ask about one thing, by using these external call methods we restrict the "REQUESTS" to be strictly |
If we need to add support for other queries, we should check upstream with pyvo and then implement it there. That is my immediate thought. |
Alright, l'll migrate this PR to using PyVo for now. |
I don't know, so I've asked in this comment on the solar distance issue #134. Going back to requests seems to be a step backwards (although the non-URL encoded ADQL query can still be passed to requests, by using the request payload instead of building the full URL by hand). |
OK, so we have discussed this on our weekly calls. And I think the decision was just to punt this for the moment? Am I recalling this correctly? |
Yes that is correct. |
Ok great. I think maybe we should close this PR for the moment, but link it to the original issue. Is that ok with you @NucleonGodX ? |
Yep, thats perfectly fine. |
This PR is a part of GSoC-2024, this PR is tackling the issue(#32 ) that is using astroquery's tap plus to do URL calls.
Fixes #32