A SQLite memory database is the same as a SQLite file database except it's
created for just the instance that app is running. You have to create
table(s) and field(s) for those table(s). Then the app then populates the
data and queries it. SQLite memory database supports the same SQL syntax as
a file based SQLite database. When opening an SQLite database if you don't
supply a file spec then it's created in memory( I think that ":memory:" for
the file spec also works). If you supply a file spec and the db does not
exist then an empty one is created just like a memory database. Of course a
memory database is faster than a disk based database. I find that SQL
invaluable for dealing with complex data relationships.

Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net

-----Original Message-----
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf
Of J. Landman Gay via use-livecode
Sent: Monday, December 31, 2018 4:32 PM
To: How to use LiveCode
Cc: J. Landman Gay
Subject: Re: Refactoring is your friend / moving from 6.x to 9.x

I'm generally deficient when it comes to databases but curious how one
creates a memory based one. Is there a trick, and does it work with others
besides sql?

This is probably a newbie question.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software |
http://www.hyperactivesw.com On December 31, 2018 11:31:15 AM Bob Sneidar
via use-livecode <use-livecode@lists.runrev.com> wrote:

> For multiple recursions into an array I came up with a method for 
> loading an array into a memory based sql database. Subsequent queries 
> take less time, depending of course on how complex they are, but you 
> can do lots of cool thinks, like complex filtering / sorts, 
> calculations, etc. to a cursor, then I have a function that converts a
cursor to an array.
>
> I originally used it to get the topmost, leftmost, bottommost and 
> rightmost objects on a card that were visible by using min and max 
> queries on a list of the objects. But of course the method can be expanded
to do almost anything.
>
> Bob S
>
>
>> On Dec 30, 2018, at 11:33 , Malte Pfaff-Brill via use-livecode 
>> <use-livecode@lists.runrev.com> wrote:
>>
>> Not yet fixable for me:
>> Array operations on larger data sets still slower than they were
>>
>> Non engine related:
>> My SQL-Fu has improved a bit ;-) Quite a bit of performance to gain
there.
>>
>> Did anybody of you happen to refactor old code and if so, do you have 
>> any observations you might want to share?
>>
>> Cheers,
>>
>> Malte
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your 
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode




_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Reply via email to