Vitaly Shukela
Vitaly Shukela
> I didn't want select to be case sensitive, which would have been the case if the command itself would have been called "SELECT". When I see `select`, I first...
> What do you think about the popularity of such a feature? Maybe the presence of such feature can be taken for granted, but absence seen as an disappointing moment......
Can `q` recognize that things after `AS` are not to be interpreted as filenames and just left as is?
``` $ python bin/q.py 'with eee as ( select 9 ) select 4' 4 $ python3 bin/q.py 'with eee as ( select 9 ) select * from eee' No files...
Maybe special table names like `nofile_eee` can be used to signal `q` not to try to read any files? ```diff diff --git a/bin/q.py b/bin/q.py index b41451f..de773bf 100755 --- a/bin/q.py +++...
With the diff above some my use cases which required saving temporary CSV files start working without temporary files.
@EdMUK Will this lead to less user-friendly error messages in case of misspelled filenames?
Is the filename escaping implement in some form?
Another approach: decouple table name and file name, makeing the former only a default for the latter. Example syntax: ``` q -O 'SELECT * FROM a LEFT JOIN b ON...
I think the main advantage of `q` is ability to use it as a one-liner, without any "environment". I don't want new features (this issue, the caching) to be API-only...