SQLite is no more multi user than flat files, LSON, or stack files; the developer would need to hand craft record locking with each.
But that's not hard to do, and can be reasonably efficient depending on the particulars of the data and how it's used.
Using an inherently multi user DB like MySQL takes care of that part for you, so if you're going to use SQL you might as well use one designed for multi user scenarios.
But if you're looking to avoid introducing more moving parts into the system, there are many other ways to manage storage for multi user systems.
We know the number of records is small. How large is each record? And how many fields? And does the system require relationality?
Strategy to construct a Stack
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller
-
- VIP Livecode Opensource Backer
- Posts: 9802
- Joined: Sat Apr 08, 2006 7:05 am
- Location: Los Angeles
- Contact:
Re: Strategy to construct a Stack
Richard Gaskin
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
-
- VIP Livecode Opensource Backer
- Posts: 11
- Joined: Mon Oct 31, 2011 3:46 pm
- Location: Edinburgh, Scotland
- Contact:
Re: Strategy to construct a Stack
Thanks for that. I didn't realise that.
IMac MacOSX 10.13
Livecode 9.0.0 Build 15103
Livecode 9.0.0 Build 15103