Re: Issues with storage of data in stack

> On 24 Mar 2018, at 7:23 am, Richard Gaskin via use-livecode > wrote: > > Apparently he submitted a pull request last year for what seems like a very > nice solution, using formatting strings: > https://github.com/livecode/livecode/pull/5433 >

Re: Issues with storage of data in stack

Lagi Pittas write: > Sqlite does fine for my single user systems but needing routines to > change between LC dates and sqlite dates is a pain. Indeed it is, or to any format not already handled. There are some requests in the bug DB for other formats: https://quality.livecode.com/show_bug.cgi?i

Re: Issues with storage of data in stack

Hi Mark, Thanks for that - I'd forgotten I'd asked ;-) The times you gave are super impressive - who needs mysql - Im gonna see if I get anytime in the next month - snowed under as usual. I think I have got it - each cluster is in effect a file on the disk? I will understand it more when I have

Re: Issues with storage of data in stack

Hi Lagi, Sorry about the delayed reply. I have been on a long business trip. Your early designs are far more sophisticated than what we put together here. Super impressive history you have. LiveCode really is the champion here in that we are only using arrayEncode() and put myArrayA into url()

Re: Issues with storage of data in stack

Hi Mark, Thanks for the detailed explanation but I have a few (ish) questions ... Hope you don't mind me asking these questions because I did have to write my own access routines in those bad old days before I started on Clipper/Foxpro/Delphi/Btrieve and I do enjoy learning from others on the li

Re: Issues with storage of data in stack

Hi BR, Sorry about that. I have updated the docs page to link back to the main site. https://livecloud.io Mark > On Mar 11, 2018, at 7:18 PM, Sannyasin Brahmanathaswami via use-livecode > wrote: > > Mark Talluto wrote: > >If you are interested in seeing other A

Re: Issues with storage of data in stack

Mark Talluto wrote: If you are interested in seeing other APIs we have found useful, here is a running list. Look under the API dropdown for more ideas. http://canelasoftware.github.io/cassiaDB_docs/ http://canelasoftware.github.io/cassiaDB_docs/ Where does one download the LiveCloud Ma

Re: Issues with storage of data in stack

Hi Lagi, Our LiveCode array database does not use SQL or any other database. In terms of local only database, we do not rely on anything but LiveCode. It is purely a LiveCode derived system. Data is manipulated using familiar methodologies to other databases. The data is encrypted using ‘encryp

Re: Issues with storage of data in stack

Some notes from a while back on using LSON (LiveCode encoded arrays): http://lists.runrev.com/pipermail/use-livecode/2016-May/227330.html -- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web __

Re: Issues with storage of data in stack

HI Mark, I am intrigued by your way of saving only whats changed and also when you say save to disk after arrayencoded. Do you meanas a simple save as a binfile or in an sqlite BLOB? I would really like to see some exampleish code on saving to disk - if it's other than a single array in a single

Re: Issues with storage of data in stack

Hi Peter, Yes. But, you can protect it with a password. 1. arrayEncode(yourDataInAVariable) 2. Encrypt the result above 3. Write out the encrypted value to disk Best regards, Mark Talluto livecloud.io nursenotes.net canelasoftware.com

Re: Issues with storage of data in stack

Hi Peter, If your app could encrypt the arrayEncoded data before writing to disk, and then decrypt it when reading it, that would solve the unwanted-access problem. The amount of time used by encrypt/decrypt processes is negligible, even for large files. I love arrays. They have become one o

Re: Issues with storage of data in stack

Yes, if they had Livecode. In that case encrypt the arraydecode string using a seed that only you know. I use a special seed value that is different for every record I add to a database. Very effective and hard to guess. Bob S > On Mar 8, 2018, at 11:22 , Peter Bogdanoff via use-livecode >

Re: Issues with storage of data in stack

Mark, If the data is written to a file on disk, could someone else arrayDecode the file and gain access to it? Peter Bogdanoff ArtsInteractive > On Mar 8, 2018, at 10:38 AM, Mark Talluto via use-livecode > wrote: > >> On Mar 8, 2018, at 9:03 AM, Lagi Pittas via use-livecode >> wrote: >> >

Re: Issues with storage of data in stack

You would need to arrayencode() before saving an array to a database as well. Bob S > On Mar 8, 2018, at 10:38 , Mark Talluto via use-livecode > wrote: > > I too use arrays as a data store. You could save the arrays to disk directly > with arrayEncode(). _

Re: Issues with storage of data in stack

> On Mar 8, 2018, at 9:03 AM, Lagi Pittas via use-livecode > wrote: > > In the first version of the system I save the arrays which held all > the Clerks orders/totals etc and items into an external stack every > time they added an item. I too use arrays as a data store. You could save the array

Re: Issues with storage of data in stack

I've found that sending binary data over the internet is risky. A zip file or base64 encoded file avoids most transit corruption. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On March 8, 2018 11:06:16 AM Lagi

Re: Issues with storage of data in stack

Hi Mike, I have 60+ machines running windows7 embedded running a POS/TILL system also a few tablets running windows and android with the same system - wth abouth 8 lines of code added to work on Android. In the first version of the system I save the arrays which held all the Clerks orders/tot

Re: Issues with storage of data in stack

Hi. I store data in both external files and within the stack itself. Never used a DB. But no issues of any kind ever. Craig Newman -- Sent from: http://runtime-revolution.278305.n4.nabble.com/Revolution-User-f278306.html ___ use-livecode mailing l

Re: Issues with storage of data in stack

Mike Kerner wrote: > I have to admit, I haven't stored data in a stack in a long time, > since the database options are so easy to use. If you're currently > storing data in a stack, have you run into any issues on any platform > with it, especially on mobile, for instance, where the rules can b