Using stacks as a database for very large data sets

Frank D. Engel, Jr. fde101 at
Wed Jan 26 11:44:06 EST 2005

Hash: SHA1

You might do best to split the data onto separate stacks and save them 
independently.  When the data is needed, you can retrieve it from the 
appropriate stack; when you change it, you copy it back to the data 
stack it belongs in and, at an appropriate time, save the data stack.

On Jan 26, 2005, at 10:53 AM, Lynch, Jonathan wrote:

> Saving a large stack can be time consuming - especially across a
> network.
> Would it be possible to have some sort of write-to-file scheme that 
> just
> changes the stored data for single card, but not the entire stack?
> _______________________________________________
> use-revolution mailing list
> use-revolution at
- -----------------------------------------------------------
Frank D. Engel, Jr.  <fde101 at>

$ ln -s /usr/share/kjvbible /usr/manual
$ true | cat /usr/manual | grep "John 3:16"
John 3:16 For God so loved the world, that he gave his only begotten 
Son, that whosoever believeth in him should not perish, but have 
everlasting life.
Version: GnuPG v1.2.4 (Darwin)


$0 Web Hosting with up to 120MB web space, 1000 MB Transfer
10 Personalized POP and Web E-mail Accounts, and much more.
Signup at

More information about the Use-livecode mailing list