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

Security names returned by lookupSecurity #261

Open
joshuaulrich opened this issue Feb 18, 2018 · 2 comments
Open

Security names returned by lookupSecurity #261

joshuaulrich opened this issue Feb 18, 2018 · 2 comments

Comments

@joshuaulrich
Copy link

I was surprised that the security names returned by lookupSecurity() could not be passed directly to another Rblpapi function, like bdh(). I haven't looked at the code to understand where those values come from, though I suspect they're simply passed-through from whatever the API function returns.

So I'm soliciting feedback for the best way to achieve what I want. The options I can think of off the top of my head:

  1. Modify lookupSecurity() to return security names that can be used in other functions
  2. Add a translator function

I was also surprised that the yellowkey values were not consistent with what needs to be used when specifying a security name. Support for that could be added without changing the current defaults.

@eddelbuettel
Copy link
Member

All of those would strike me as API issues we cannot do much about given the famously opaque documentation. But if you can come up with workarounds, let us know.

@joel23888
Copy link
Contributor

@joshuaulrich you could try an approach like the regex referred to in #215 (comment). You may need to modify to your exact requirements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants