Hi Glen, First, as Richard G. mention, internet wars have been fought over this issue… to me it’s your choice.
I’ve done both and both have their ups and downs. For mobile, I’ve sided with keeping it in the DB. It keeps everything together and the way I’m querying the DB, I’m already pulling the data and the image just comes along with it. My experience is that it’s very fast. As does Jonathan L, I store my images as base64 encoded so they can be transmitted over the internet as needed and decode them on the fly when needed by the app. The added benefit is you can store them in a TXT field in SQLite. LC is very fast at decoding them. As for growing in size, especially for mobile, something is going to grow either way… wether it’s the files on the file system or the DB file, as you add, it’s going to grow. Sorry, I don’t have anything resembling a example stack to share, but in keeping the above in mind, it’s not too hard to implement. HTH, Steve MacLean > On Aug 23, 2017, at 12:11 PM, Glen Bojsza via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Hello, > > I was looking for feedback on whether it is better to store images as BLOBs > in an SQLite database for a LC app or store paths to the images in the > SQLite database and the images in a separate folder. > > Any help in understanding possible performance and memory issues is what I > am looking for. > > Can I assume that any issues would be the same for both Android and iOS? > > thanks, > > Glen > _______________________________________________ > 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
