On Mon, Feb 10, 2014 at 4:23 PM, Richard Hipp <d...@sqlite.org> wrote:
> Proposed Change To Address The Problem: > > When launching sqlite3.exe with a double-click, have it open a standard > database in a standard place instead of an in-memory database as you would > get when launching sqlite3.exe with no arguments. Possibly also give > additional hints, such as references to the ".open" command, when launching > by double-click. > Personally, I don't care much for this change... I noticed you didn't ask for +1 / -1 on this, but most REPLs behave like sqlite3 does now, i.e. pure in-memory changes, and you need to explicitly do something to persist your experimentations. My $0.02. --DD Questions: > > (4) What should the name of the "standard" database file be? > In keeping with sqlite_master, I'd name it sqlite_default.db > (5) In what folder should the "standard" database file be created? > It depends on the Windows version I'm afraid. On Win7, %HOMEDRIVE%\%HOMEPATH% seems like a sensible default, or perhaps %USERPROFILE% too. Didn't remember the previous Windows / DOS equivalents for Vista, XP, and earlier. --DD C:\Users\DDevienne>set USER USERDNSDOMAIN=... USERDOMAIN=... USERNAME=DDevienne USERPROFILE=C:\Users\DDevienne C:\Users\DDevienne>set HOME HOMEDRIVE=C: HOMEPATH=\Users\DDevienne _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
