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.

Sign up for GitHub

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

Jump to bottom

Allow specifying whse object name in bcdc_query_geodata #106

Closed
ateucher opened this issue Aug 23, 2019 · 1 comment
Closed

Allow specifying whse object name in bcdc_query_geodata #106

ateucher opened this issue Aug 23, 2019 · 1 comment
Labels
enhancement New feature or request
Milestone
v0.2.0

Comments

@ateucher
Copy link
Collaborator

It's often the case that users familiar with the BCGW will know the exact name of the database object they want to query, so we should allow that without forcing them to go through the catalogue record/resource id.

E.g., this should work: bcdc_query_geodata("WHSE_IMAGERY_AND_BASE_MAPS.GSR_AIRPORTS_SVW")
@ateucher ateucher added the enhancement New feature or request label Aug 23, 2019
@ateucher ateucher added this to the v0.2.0 milestone Aug 23, 2019
ateucher added a commit that referenced this issue Sep 11, 2019
@ateucher
Allow passing whse object name to bcdc_query_geodata (#106)
05afe0a
ateucher added a commit that referenced this issue Sep 11, 2019
@ateucher
Fix print method for bcdc_promise when whse object name is passed (no…
c5dc492 
… record to parse). #106
ateucher added a commit that referenced this issue Sep 11, 2019
@ateucher
Allow whse object name to be passed to bcdc_get_data. #106
e607ac4
@ateucher ateucher mentioned this issue Sep 11, 2019
Merged
3 tasks
@boshek
Copy link
Collaborator

boshek commented Oct 10, 2019

Closed via #110

@boshek boshek closed this as completed Oct 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
v0.2.0
Development

No branches or pull requests
2 participants
@ateucher @boshek