4 ms·

Doesn't seem to support sqlite3 dot commands such as .mode/.separator/.import/.output/.headers... (these are really implemented in sqlite3 CLI and not part of t

Doesn't seem to support sqlite3 dot commands such as .mode/.separator/.import/.output/.headers... (these are really implemented in sqlite3 CLI and not part of the sqlite library). These are, at least for me, among the main reasons to use the CLI in conjunction with SQLite. (The SQLite CLI is very good for massaging CSV data into the correct shape; as far as I know there is no canonical file extension for CLI scripts, I use .sqs, and the CLI has no parameter to run scripts directly, so you have to start the CLI manually and do .read foo.sqs).

amjith 8y ago
We don't support all of the special commands but we do support a small subset of them. We support .mode .schema, .table and a few others.
vram22 8y ago
>and the CLI has no parameter to run scripts directly, so you have to start the CLI manually and do .read foo.sqs). It does work, but only sort of. Just did: $ sqlite3 -init select_contact.sql test_sqlite.db -- Loading resources from select_contact.sql Alan|Acre|50|Male|100.0 Betty|Smith|20|Female|200.0 Charlie|Copenhagen|30|Male|400.0 Dorothy|Delhi|80|Female|400.0 Edwin|Bombay|40|Male|100.0 Edwin|Pune|55|Female|110.0 SQLite version 3.8.11 2015-07-27 13:49:41 Enter ".help" for usage hints. sqlite> where select_contact.sql contains "select * from contact;" So it can run a script given as a parameter. But it leaves you in the CLI instead of cleanly exiting. And prints those extra headers, etc. Not very Unix-philosophy-adherent, it seems. Edit: formatting