SQL IN() function

[Bob Sneidar]

When I only have one value type to keep track of, it seems more efficient to me to simply put the values in a list. It’s something that has carried over from my Foxpro days developing for SBT. Of course back then, efficient use of storage was a big deal. But I figured a way to search for values in a list no matter which flavor of SQL I use, so problem solved. 

Bob S


> On May 22, 2015, at 23:39 , Peter Haworth <pete at lcsql.com> wrote:
> 
> Hard to tell without knowing more about the app, but it feels like your
> devicelist should be a separate table with one entry per device and
> probably keyed by the key of the original table
> 
> Pete
> lcSQL Software
> On May 23, 2015 2:32 AM, "Dr. Hawkins" <dochawk at gmail.com> wrote:
> 
>> On Fri, May 22, 2015 at 1:13 PM, Bob Sneidar
>> <bobsneidar at iotecdigital.com> wrote:
>>> Because it is a list of integers, which is a string. I suppose I could
>> have used archer, but when I am uncertain how many values might end up in
>> the column, I always go with some kind of blob to be safe.
>> 
>> 
>> There is also TEXT, which has no limit.
>> 
>> 
>> --
>> Dr. Richard E. Hawkins, Esq.
>> (702) 508-8462
>> 
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode at 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 at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode