Multi user sqlite via shared-cache mode?

Peter Haworth pete at lcsql.com
Sat Mar 15 15:51:04 EDT 2014


Not sure how you would do that unless you mean switching on shared cache.
 Unfortunately, you can't do that in LC even with the updated SQLite
library because LC doesn't support URI filenames in revOPenDatabase and
that's how you switch on shared cache. I've entered a bug report about
that, waiting to hear if it will be fixed or not.

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 Sat, Mar 15, 2014 at 8:56 AM, Dr. Hawkins <dochawk at gmail.com> wrote:

> On Tue, Mar 11, 2014 at 9:34 AM, Peter Haworth <pete at lcsql.com> wrote:
>
> > In general, it's risky accessing SQlite databases over a network unless
> you
> > are only querying the database and not doing any insert/update/delete
> > operations for the reasons explained in the link.
> >
>
> How about sharing a :memory: instance between two apps of the same user and
> machine.
>
> This would go a long way on my master/slave issue of syncing to a remote
> database without locking up the user interface . . . (at the moment, I
> watch for time since last keystroke, and if it's long enough, risk the
> update.  I'm thinking to pass the UPDATE/SELECT command to to a slave
> process, but having the slave access the internal db would be better . .
> .).
>
>
> --
> Dr. Richard E. Hawkins, Esq.
> (702) 508-8462
> _______________________________________________
> 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
>



More information about the use-livecode mailing list