Joe Wilson <[EMAIL PROTECTED]> writes: > I've seen this same behavior when running a MinGW-compiled sqlite3.exe in the > cygwin shell. It has > something to do with the lack of flushing of information written to stdout > (until close() anyway). > If you blindly type in the sqlite commands - it does work. Once you exit the > shell via .q you can > see the entire output of the session. > > One workaround is to use a cygwin-compiled sqlite3.exe. Perhaps hacking the > sqlite shell not to > buffer its console output would also do the trick. >
I entered the commands (which I didn't do before) and I can see the output immediately. So the only hitch is a command line without a prompt sqlite>. -- Radek
