There may be an environment variable you need to set to increase it. Because
it's network based, it stands to reason that an unlimited query string can be
exploited as a denial of service strategy.
Bob S
> On May 24, 2022, at 10:19 , doc hawk via use-livecode
> wrote:
>
> When opening a
When opening a “file”, my software makes a compound query with several hundred
queries within it, so . . .
This is possible on Postgres and SQLite, but (last I checked) not on MySQL
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please
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
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
Le 2022-05-20 08:00, Paul Dupuis via use-livecode a écrit :
You can save some characters by the following:
SELECT ... FROM myTable WHERE id IN (5523,7831,162814,34895,...)
which is the same as using multiple OR equals in your example.
Thank you. Yes I will try that.
And I have no idea why
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
You can save some characters by the following:
SELECT ... FROM myTable WHERE id IN (5523,7831,162814,34895,...)
which is the same as using multiple OR equals in your example.
If you need to break this up further, you can UNION the results of
multiple queries, such as:
SELECT ... FROM
