bobs at twft.com
Wed Dec 21 16:54:00 EST 2011
Probably something similar to what I encountered when passing an AES encrypted string that *might* contain commas or characters that would jack a query. Using sqlYoga solved that for me as the insert and update queries are escaped by default (correct me if I am wrong).
On Dec 21, 2011, at 1:22 PM, Pete wrote:
> The problem I had was that it just didn't work using a blob. The encoded
> array got stored OK but LC didn't recognise what came back as an array,
> don't remember all the details.
> The default max size of a text field in SQLite is 1 million characters so I
> think he'd be pretty safe.
> On Wed, Dec 21, 2011 at 12:48 PM, Bob Sneidar <bobs at twft.com> wrote:
>> How can you tell how big the encoded array will be? I would use blobs
>> whenever the size might increase in the future beyond what I expected. But
>> if the array is a fixed size, and you know for certain it will never grow
>> beyond x, then a text column would do fine.
>> On Dec 21, 2011, at 10:35 AM, Pete wrote:
>>> One thing I mentioned earlier that might be relevant to him is that
>>> no need to use blobs when storing LC arrays. Just use base64 encoding and
>>> store it in a text field, works fine. Some folks on this list pointed me
>>> in that direction a few months back.
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
> Molly's Revenge <http://www.mollysrevenge.com>
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the Use-livecode