-
Notifications
You must be signed in to change notification settings - Fork 182
Request: Initial SQL Read/Write Support #110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact it 8000 s 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 some initial SQL in it? (I'm marking this as an enhancement) |
Sure, I've attached a sample workbook in #109 that has both query bands and initial sql. As an example use case I'd like to be able to write something like following;
|
* 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 allow for initial sql to be passed. Being able to programmatically modify it would be extremely useful.
The text was updated successfully, but these errors were encountered: