LiveCode Forums

There are times when using a database for data that is fairly static needs to be considered a little overkill.
An option would be to place that information into the contents of the field. So, where is that data stored? How stable and reliable is that information? Are there practical limits on how much data can be stored this way?
The reason for this question? If I want to NOT have people delete this information because it it stored in a folder, as SQLite does.
There will be periodic additions and updates to this information but not on a regular basis.
Thoughts?

Even better than fields is storing data in custom properties. The field object is a good choice for display, but to make that rendering happen it carries a lot more overhead than custom properties.

And with custom props you can even use array syntax if you have a large collection you need to traverse by key.

And custom properties come in sets, and you can have any number of properties within any number of custom property sets, so you get a nice two-level hierarchy that's very efficient to work with.

In the User Guide accessible from the Help menu, see page 222 for info on working with custom properties.

I am thinking that, in my application, of moving the Devices table from a Mysql table to a text content or now maybe a custom property.It is not a file that is updated or modified very often. But there may be additions to it in the future.
Thanks, I'll check it out.
BTW I got the the program to run in 2 minutes.

I meant field content.

chipsm wrote:BTW I got the the program to run in 2 minutes.

Excellent!