On 11 Feb 2014 at 21:49, Stephen Chrzanowski <[email protected]> wrote:
> I don't like the idea of letting the software decide what should be done
> based on a configuration file.
The .sqliterc file already exists, so you're too late.
> Linux and Windows both can isolate processes from each other, be
> completely independent, and not worry about pesky configuration files.
> Yeah most linux distros do have a /home directory, but some 'root only'
> devices don't, or may not even have ${HOME} defined as per James suggested.
Who is going to be running a CLI program on such devices?
> If you're going to go as far as throwing parameters at
> sqlite3.exe/sqlite3.so/sqlite3.whatever to indicate where a configuration file
> is, you might as well start including the database you want to write to.
AIUI, the suggestion is for a change to the CLI program only. And it already
knows where the .sqliterc configuration file is to be found, at least on OS X.
I imagine it'll be the same place for linux, I've no idea about Windows.
--
Cheers -- Tim
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
