3 ms·
> Have you ever stared at a text file on the screen, hoping it would have been a database so you could ask anything you want about it? Not really. I could see
by iblaine 8y ago
> Have you ever stared at a text file on the screen, hoping it would have been a database so you could ask anything you want about it?
Not really. I could see this being helpful for debugging, but at that point you can get by with some simple bash string operations. Doing that same operation w/SQL seems like overkill.
- mjirv 8y agoMaybe my bash just isn't good enough anymore, but I do this all the time. In fact, I was just doing some work this morning where I needed to load a CSV into SQLite for analysis. Since I still had the file, I ran some queries on the same file via Q to test it out. And it works great! (With some handholding to get quoting and delimiters right). The major downside was it's pretty slow, presumably because it reloads the file into a SQLite database each time you run a command. So, I'll probably stick with loading CSVs into SQLite myself, but I could see this being a useful tool for running one-off analysis on data from stdin.
- syn0byte 8y agoThe devil you know; I find myself with the opposite problem on occasion. "If only I could just grep and awk out what I wanted instead of using some contrived query and arcane data connectors"
- qwerty456127 8y ago> you can get by with some simple bash string operations. Doing that same operation w/SQL seems like overkill. Coding bash seems an overkill for just so many people. Bash is scary while SQL is intuitive by design.