SQLite Forum

Shell command parsing bugs with .open
To help someone in another thread, I was trying to get this to work:

        .once foo.sql ; .dump

I tried it two different ways: once in the interactive shell and once as parameters to the `sqlite3` command after the DB file name. Either way, it gave a "usage" message, from which I infer that the SQLite shell command processor is not seeing that it's getting a file name parameter. Perhaps it's trying to interpret the semicolon as part of the file name?

Regardless of the "why," it would be useful if this would work because you could then do a dump-to-SQL without any I/O redirection on the command.