Data Persistence

Mike Bonner bonnmike at gmail.com
Fri Jul 27 18:19:54 EDT 2018


On the subject of sqLite/memory databases and preferences/data persistence,
rather than using an array, and doing the encode/decode stuff, would it
make sense to do the following..
1. open an empty in memory database
2. attach a disk based database
3. copy the required table(s) from disk base to memory base

At this point, for data reads you have a super fast sqlite in memory
database.  For updates, do a double update, both in memory, and disk.

It seems like this would be more efficient than re-encoding an array every
time there is an update and writing the whole thing out to disk each time,
rather than updating just whatever small change might need to be made to
sqlite.

The affects and requirements would be similar. Update the array, (1 update)
ecode and write to disk (second update)  vs update in mem sqlite, and
update attached sqlite database.

Does my thinking make sense?

On Fri, Jul 27, 2018 at 4:11 PM Bob Sneidar via use-livecode <
use-livecode at lists.runrev.com> wrote:

> I tried reading an "LSON" format, but it's not straight forward. It's
> easier to simply arrayDecode the LSON and work with the array. And since
> you can convert the array to a memory sqLite database and back again with
> my handy dandy handlers, everybody wins!
>
> Bob S
>
>
> > On Jul 27, 2018, at 12:52 , Alex Tweedly via use-livecode <
> use-livecode at lists.runrev.com> wrote:
> >
> > On 27/07/2018 20:17, Richard Gaskin via use-livecode wrote:
> >
> >>
> >> >  Using arrays intigues me, especially if I can just keep it in RAM (It
> >> > is a small amount of data for sure).
> >>
> >> One great thing about LC's built-in support for arrays is that it's
> built-in.
> >>
> >> JSON has become used in so many other languages that we've forgotten
> why it was invented:  to serialize JavaScript objects as simply and
> efficiently as possible using features already built into the JavaScript
> interpreter.
> >>
> >> LSON is that for us, as much a with-the-grain approach to data handling
> in LiveCode as JSON is for JavaScript.
> > I just wish there was a human-readable, human-editable-in-a-text-editor
> variant of LSON :-)
> >
> > Someday, when I have some spare time, ...
> >
> > -- Alex.
>
>
> _______________________________________________
> 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