Re: Thoughts on BLOBs in SQLite

The advantage comes if you are displaying the image through a web browser - you can put in the URL for the image and let the webview handle concurrent image loading. I still went the other way, for other reasons, but that is one of the advantages. The other is database file size. Sent from

Re: Thoughts on BLOBs in SQLite

Tom Glod wrote: so I base encode the binary variable and then save it in a text field in table. no problems and no bs ever. Others do this also. I'm curious from an "uber architecture" point of view, what pros there are to keeping the image data in a base encoded form in the data

Re: Thoughts on BLOBs in SQLite

Ahhh yes. I remember the first time Hypercard corrupted one of my stacks. It was like learning my girlfriend cheated on me for the first time. And then to discover that Hypercard was going to regularly corrupt my stacks was like learning she was a prostitute in her spare time! The

Re: Thoughts on BLOBs in SQLite

I rely very much on SQLite and I do not use & store blobs at all. reason 1 is that it always required special handling which is a red flag reason 2 when I googled it ..it was all problems. so I base encode the binary variable and then save it in a text field in table. no problems and no bs

Re: Thoughts on BLOBs in SQLite

Thanks Steve...it looks like (in my current case) that the encode / decode SQLite text field is the easiest way to get me solution. Glen On Wed, Aug 23, 2017 at 1:43 PM, Stephen MacLean via use-livecode < use-livecode@lists.runrev.com> wrote: > Hi Glen, > > First, as Richard G. mention,

Re: Thoughts on BLOBs in SQLite

> On Aug 23, 2017, at 09:36 , Richard Gaskin via use-livecode > wrote: > > Glen Bojsza wrote: > > > 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

Re: Thoughts on BLOBs in SQLite

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

Re: Thoughts on BLOBs in SQLite

For Augmented Earth, the images are base 64 encoded. This is needed for transmitting. Also, I can store a variable number of images in a single blob cell, using a character outside of the base64 range as a delimiter between encoded images. Sent from my iPhone > On Aug 23, 2017, at 12:48 PM,

Re: Thoughts on BLOBs in SQLite

My databases will be fixed in their content (basically they are going to be different test engines for students) so the images will not be edited nor changed. I am thinking that this may help me avoid any future issues that may arise if different platforms have different directory structures and

Re: Thoughts on BLOBs in SQLite

Glen Bojsza wrote: > 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. This is a religious issue in some circles, and there may be technical

Re: Thoughts on BLOBs in SQLite

You can also store multiple images in a single blob, which can be helpful. Sent from my iPhone > On Aug 23, 2017, at 12:25 PM, Bob Sneidar via use-livecode > wrote: > > Better is a relative term. Do you need to occasionally edit the images? Will > the database

Re: Thoughts on BLOBs in SQLite

Better is a relative term. Do you need to occasionally edit the images? Will the database continue to grow over time? My instinct is to keep files as files on the disk, because managing them is not dependent on access to a database. However, having the images universally accessible in a