Hi all,
my tests found:
Using a file test.sql and decommenting the .commands as required
-- + .databases
-- + .dump
-- + .echo ON
-- + .exit
-- + .explain
-- + .header ON
-- + .help
-- + .indices table
-- + .mode list
-- + .mode insert table
-- / .nullvalue 'nil'
-- + .output filename
-- + .output stdout
-- / .prompt '1' '2'
-- + .quit
-- + .read filename
-- + .schema
-- / .separator '-'
-- + .show
-- + .tables
-- + .timeout 1
-- + .width 10 10
select 'Hello, this is SQLite!', 123;
with the command line
sqlite.exe test.db .read test.sql
under WinNT shows, that the commands
.nullvalue, .prompt and .separator
are not working a expected but providing an output like
unknown command or invalid arguments: .command. Enter .help for help
All other commands obviously are working allright.
Michael Hanssen
-Ursprüngliche Nachricht-
Von: D. Richard Hipp
Gesendet am: Dienstag, 9. März 2004 04:21
An: rayB
Cc: [EMAIL PROTECTED]
Betreff: Re: [sqlite] SQLite 2.8.13. Issues found with SQLite.exe
rayB wrote:
Seems that dot-commands (.output, .separator, .nullvalue, etc) are now being
rejected by SQLite.exe 2.8.13 when contained in files executed via the .read
command.
Error message text is: 'unknown command or invalid arguments: output.
Enter .help for help'
I tired it and everything appears to be working fine. Please provide
more details about the problem and I will look into it further.
--
D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]