That capability is built into SQLite already -- it comes with an import utility. textql seems to just be a wrapper around this.
Key differences: - sqlite import demands an on disk db, textql will use an in memory db if it can, increases performance - sqlite import will not accept stdin, breaking unix pipes. textql will happily do so.
I will make a note of this in the project readme, seems to crop up a lot.