-
Notifications
You must be signed in to change notification settings - Fork 13
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
Merge BETYdb table queries into a single generic function #26
Comments
@dlebauer okay, thanks |
@sckott no, I made this issue at the same time as #27 as a place-holder for re-implementing the broken functions that I removed in that pull request. The test file in PR #29 has the following function that doesn't work, which is where I got stuck trying to put the URL together ... I'd appreciate help on that ... (here is the API documentation) debugonce(betydb_http)
betydb_traits(genus = "Miscanthus", author = "Arundale", trait = "yield") |
@dlebauer can this be closed, been a while, not sure about the details |
Close
…On Tue, Mar 21, 2017 at 3:35 PM Scott Chamberlain ***@***.***> wrote:
@dlebauer <https://github.com/dlebauer> can this be closed, been a while,
not sure about the details
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#26 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAcX5zSNw9PeL8n301Zews6h_W7Ht6jGks5roCZlgaJpZM4EINmI>
.
|
Create a single function to query tables in BETYdb.
waiting / depends on #77
Features to implement:
betydb_<tablename>
functions with one function that takes tablename as an argumentbetydb_query(table = 'citations', key = '', baseurl = 'https://www.betydb.org', apiversion = 'beta', ...)
...
will accept one or more arguments of the form<field> = 'searchstring'
wherefield
is a valid API endpoint / field in the tableTests
The following queries should work:
References
The BETYdb table queries
betydb_traits
,betydb_yields
,betydb_citations
, etc were removed (PR Revisions to support BETYdb 4.0 API #27)feedback
@sckott @gsrhode @robkooper @max-zilla.
The text was updated successfully, but these errors were encountered: