-
Notifications
You must be signed in to change notification settings - Fork 182
Request: Query Band Read/Write Support #109
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
Comments
@r-richmond Thank you for opening a request! Would it be possible to include a dummy-tds or twb that already has a query band in it? (I'm marking this as an enhancement) |
Sure, I've attached a dummy workbook that contains both sample query bands & sample initial sql. As far as an example use case. I would like to be able to write something like
note: in this case I'd like to be the special value that you can use in query bands now and not a hardcoded string of the current workbook name. |
* Fix #117 by only attempting files with the right extension inside the archive (#118) * Commenting and Docstring cleanup. A few very small code cleanups (#120) Add docstrings and remove clutter. I also made some very tiny tweaks to some code for clarity. * Small cleanups for various editors. Play nice with built in test-runners (#121) * Add Py36, update travis to use pycodestyle (#124) * Add `initial sql` and `query band` support (#123) Addresses #109 and #110 * Prep for release of 0.6 (#125) * Prep for release of 0.6 * wordsmithing the changelog
Marking this as closed with release 0.6 & the merging of #123 |
Certain Datasources have query bands and it would be extremely helpful to be able to modify these programatically.
The text was updated successfully, but these errors were encountered: