-
Notifications
You must be signed in to change notification settings - Fork 11
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
Table manager #101
Table manager #101
Conversation
As happened before, I started to write documentation for how to do queries and the complexity of "oh, but this is a reference table so it's all different" seemed too much to try to communicate (or remember). I wanted to bump this commit to get it into testing and use. I added a warning to querying through this, similar to the live_live_query warning. |
As a reminder, the general format is something like:
Where the function named after the table name has query filters for both the table and any reference tables (these can be seen in the docstring) and the arguments for query (or live_query, which is live_live_query) are things like timestamp, split_positions, desired_resolution and other higher level parameters. A similar interface applies to |
Building on #100, add an optional table manager class to lower barriers to entry for querying tables.