George Herson wrote:
> Thanks for the info, Rich Shepard and Jan Kandziora.
>
> 3 documention-related suggestions about this:
>
> It seems to me that
> http://www.sqlite.org/lang_createtable.html should
> mention the ramifications of not passing in a database
> name when using the sqlite3 executable.
That page documents the behaviour of the library, not the sqlite shell
Follow the 'contents' link at the top left of that page.
> the executable should confirm an exit involving
> impending data loss.
eorge Herson wrote:
> Thanks for the info, Rich Shepard and Jan Kandziora.
>
> 3 documention-related suggestions about this:
>
> It seems to me that
> http://www.sqlite.org/lang_createtable.html should
> mention the ramifications of not passing in a database
> name when using the sqlite3 executable.
That page documents the behaviour of the SQLite library, not the sqlite3
executable. Follow the 'contents' link at the top left of that page.
> the executable should confirm an exit involving
> impending data loss.
>
> the executable should print at the start a caution
> when started without a database name.
You could always submit a patch... ;)
http://www.sqlite.org/quickstart.html does explain that the argument
after sqlite3 is the name of the database.
Martin
You could submit a patch... ;)
> the executable should print at the start a caution
> when started without a database name.
http://www.sqlite.org/quickstart.html explains that the argument after
sqlite3 is the name of the database.
Martin
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
