Maximum length of mySQL request ?

[Bob Sneidar]

OIC you are searching arrays to obtain your IDs. That would make sense because arrays are memory based. SQL is file based as in sqLite, or else accessed (typically) over a network which would account for the speed disparity. Of course, to be fail, you will have to add the time to search the arrays, THEN the time to query your SQL database with the IDs to make that comparison equal. 

Bob S


> On May 20, 2022, at 08:56 , jbv via use-livecode <use-livecode at lists.runrev.com> wrote:
> 
> Le 2022-05-20 11:24, Bob Sneidar via use-livecode a écrit :
>> I googled around a bit and there doesn't seem to be a limit on
>> statement length. I will say though that the nature of the query
>> indicates a possible design issue with the database. I suspect however
>> that you are at the mercy of someone else's schema. That there is no
>> common denominator you can query on is to me remarkable. How are you
>> obtaining your IDs then?
> 
> Thank you for your reply.
> I also did some google search before asking the question, but didn't
> find anything, only about the size of the data returned by mySQL.
> 
> What makes you think of a possible design issue ?
> The ids are auto-incremented every time a new entry is added to the
> table, and the ids in the request are obtained by intersecting various
> multi-dimensional arrays that make very complex searches very fast
> (less than 1 sec, when it takes 5 to 10 sec with regular SQL queries).
> 
> _______________________________________________
> 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