Arrays vs databases

[Bob Sneidar]

If there were a way to "query" an array which returned another array with matching keys, that would be okay. But I cannot search an array right now, so as a database for finding information, it's not all that great. Oh sure, I can write repeat loops to go through every single key to find the ones I need, but I would have to write the logic for all that. Ick! Why not just use a memory based database, or even an sqLite database? I just do not see the point to using arrays as a database when there are single and multiuser solutions all over the place.

Bob S


On May 20, 2016, at 10:35 , Mark Talluto <mark at canelasoftware.com<mailto:mark at canelasoftware.com>> wrote:

Using arrays to make your own key/value type database is very doable. The performance is probably indistinguishable with other databases for many types of apps. You can store data to disk easily with arrayEncode(); LSON as Richard has coined it.

The beauty of existing databases can not be ignored though. They do much more than store/retrieve data. Queries are one of the things that make databases so powerful.

Choosing the right path really depends on your needs. From my experience, LiveCode arrays make a fine database model for a wide range of applications. The best part is they are using a syntax you already know.

If you are interested in seeing a  proof of concept you may want to try LiveCloud. It might give you some ideas on where to go if plan to make your own database. You are definitely embarking on a fun experience. I would suggest you explore it further.

Best regards,

Mark Talluto