[sqlite] Possible bug in shell .open command?

2015-06-17 Thread Jean Chevalier
The aftermath... dir *. /x /b h8 08 @_8 0o8 hN Q N xa8 b8 0f8 10 soubor?, 14,336 bajt?

[sqlite] Possible bug in shell .open command?

2015-06-17 Thread Jean Chevalier
I took that the .open command could be issued as ".open" to open a new in-memory database and ".open ''" (followed by a pair of single quotes) to open a new unnamed temporary file database. I wonder what is going on here: After issuing a short combination of these commands with/without putting any

[sqlite] Possible bug in shell .open command?

2015-06-17 Thread Richard Hipp
Should be fixed now on trunk. On 6/17/15, Jean Chevalier wrote: > I took that the .open command could be issued as ".open" to open a new > in-memory database and ".open ''" (followed by a pair of single quotes) > to open a new unnamed temporary file database. > > I wonder what is going on here: A