SQLite, keep connection open or close every time?

[Peter Haworth]

I recommend that book for anyone who wants to be serious about using SQLite.

Pete
lcSQL Software <http://www.lcsql.com>
Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and
SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html>

On Tue, Nov 24, 2015 at 12:42 PM, Richard Gaskin <ambassador at fourthworld.com
> wrote:

> Dr. Hawkins wrote:
>
>> Doesn't a :memory: database get deleted by live code when closed.
>>
>
> I would assume that any memory structure goes away when the process using
> it is completed.
>
>
> And as I discovered playing around with sqlite, multiple potential users
>> can be a *real* problem.
>>
>> If a second user tries to open it, it appears to work.  It may even work
>> if
>> only one writes, but once there is a write, it gets strange.
>>
>
> In his book Using SQLite, Jay A. Kreibich says that SQLite DBs can be read
> by any number of concurrent users, but can only be written to by one at a
> time, with a further caveat that SQLite itself doesn't impose restrictions
> on writes, so preventing concurrent writes is, as with most files, up to
> the application.
>
> --
>  Richard Gaskin
>  Fourth World Systems
>  Software Design and Development for the Desktop, Mobile, and the Web
>  ____________________________________________________________________
>  Ambassador at FourthWorld.com                http://www.FourthWorld.com
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>