On Feb 10, 2014, at 10:20 AM, Jay Kreibich <j...@kreibi.ch> wrote: > On Feb 10, 2014, at 10:15 AM, Richard Hipp <d...@sqlite.org> wrote: > >> What if, instead of opening a standard database, the sqlite3.exe >> command-line shell just issued a warning message reminding the user that >> they are working on a transient in-memory database and suggesting the use >> of the ".open" command to connect to a persistent on-disk database. Like >> in this patch: >> >> http://www.sqlite.org/src/info/90e9deae4a > > > I think a warning is the best solution. In addition to the .open reminder, > I would add a ".save" shell command that dumps the current main database to a > file. This might be a simple alias to the .backup command. >
Actually... let me amend this. I like the suggestion of having an .quit warning when "main" is an in-memory database. In addition, I'd suggest a .save shell command that dumps the current main database to disk, and then opens the file as the new main. This would provide a "document" model that many desktop users are already used to dealing with. > -j > > -- > Jay A. Kreibich < J A Y @ K R E I B I.C H > > > "Intelligence is like underwear: it is important that you have it, but > showing it to the wrong people has the tendency to make them feel > uncomfortable." -- Angela Johnson > > > > -- Jay A. Kreibich < J A Y @ K R E I B I.C H > "Intelligence is like underwear: it is important that you have it, but showing it to the wrong people has the tendency to make them feel uncomfortable." -- Angela Johnson _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
