Neil O'Toole
Neil O'Toole
In keeping with `sq`'s general goal of terseness, `sq` should prefer short driver names. As in: ``` # Prefer this: $sq add 'pg://user:pass@localhost/sakila` # Over existing mechanism: $ sq add...
It would be useful to have an `--opts` flag for more control over output formats and what not. For example ``` # separate CSV with pipe | > sq --csv...
Currently one must do `sq add DS` and then reference the data source in a later command. It should be possible to refer to data sources in-line, e.g. ``` sq...
Given #29, `sq` could include pre-declared drivers for common APIs. Examples could include AWS, GitHub, Azure, etc. Usage could be something like: ``` sq add https://api.github.com @gh --auth="prompt" sq '@gh...
As it stands, `sq` currently always uses the embedded SQLite DB for scratch purposes. It should be possible to specify an alternative database to use. For example: ``` > sq...
With document formats such as XML and JSON, there are many sub-schema out there for which it's impractical or impossible for `sq` to generate an ideal database schema. RSS is...
Currently, if there's a non-zero number of data sources, you need to do ``` > sq add https://feed.acme.com/rss.xml @rss_acme > sq src @rss_acme # make @rss_acme the active data source...
Currently `sq` writes a downloaded remote data source to a temporary file. There should be an option to keep this file around.
Currently a remote data source (e.g. `http://neilotoole.io/sq/test/test1.xlsx`) is always re-downloaded when a command is executed against it. `sq` should be smart enough to check the remote modification (e.g. via HTTP...
It should be possible to alias tables and columns, e.g.: ``` > sq '.user | .uid:user_id, .username, .email:mail' # rename "uid" to "user_id", and "email" to "mail" ```