| List: | General Discussion | « Previous MessageNext Message » | |
| From: | Michael Widenius | Date: | August 6 1999 1:20pm |
| Subject: | Re: how many args to SELECT...IN() | ||
| View as plain text | |||
>>>>> "Paradox" == Paradox <paradox2@stripped> writes: Paradox> There probably isn't a limit, it may be stored in a linked list or other, Paradox> but its going to take a while to parse the entire message as with 50,000 Paradox> strings of length 3 each, the SQL statement will be around 275k. (there Paradox> might be a limit as to the size of the SQL statement buffer, which you may Paradox> need to increase) Paradox> Regards, Dave Paradox> P.S. I still think a JOIN would work a hell of a lot better. Hi! You are right; There shouldn't be a limit other than available memory and the SQL statment buffer. (As long as bison doesn't use stack space while parsing this (which I think is quite unlikely)). Note however that the range optimizer will sort the IN and find the optimal key to use; This will make some extra overhead if the list is really long. Regards, Monty
| Thread | ||
|---|---|---|
| • how many args to SELECT...IN() | Joel Bremson | 6 Aug |
| • Re: how many args to SELECT...IN() | Paradox | 6 Aug |
| • Re: how many args to SELECT...IN() | Thimble Smith | 6 Aug |
| • Re: how many args to SELECT...IN() | Paradox | 6 Aug |
| • Re: how many args to SELECT...IN() | Joel Bremson | 6 Aug |
| • Problem reading tables | Paul McGovern | 6 Aug |
| • Re: how many args to SELECT...IN() | Thimble Smith | 6 Aug |
| • Re: how many args to SELECT...IN() | Alok K. Dhir | 6 Aug |
| • Re: how many args to SELECT...IN() | Paradox | 6 Aug |
| • Re: how many args to SELECT...IN() | Michael Widenius | 6 Aug |
| • Re: how many args to SELECT...IN() | Christian Mack | 6 Aug |
| • Re: how many args to SELECT...IN() | Scott Hess | 6 Aug |
| • Re: how many args to SELECT...IN() | Joel Bremson | 6 Aug |
