7 replies to this topic

[David Wikström]

Does anybody know the what the maximum length of a SQL statement in FQL is? Is there indeed a specific limit, or does it depend on system resources?

[Tim Anderson]

I'm guessing, as it will be in a calculation, 30,000 characters in total

[David Wikström]

That's what I would have though too, but I actually tried some 34,000 and it still worked...

[Tim Anderson]

Wow, some length of SQL statement!

[David Wikström]

Well, it's actually a real-life scenario, not just me inventing stuff for fun (which does happen).
I'm doing a select "IN" on a list of 13-digit ISBNs, and that list can contain the ISBNs for thousands, even tens of thousands of book titles.  Not necessarily the best way of doing what I'm doing, but it got me thinking about this question. And it actually works pretty well, considering...
If there is a limit, I'd like to have a check on the length before I run the statement so the user can get a more specific error message than just "Error".

[David Wikström]

For anyone following this, I can let you know that I just ran a SQL statement that was 458,215 characters long. Worked like a charm, as long as you're patient (8 minutes).

[Tim Anderson]

Interesting. Don't suppose you plan on continuing testing to see how long the statement can be?

[David Wikström]

Depends on my client. If their company keeps growing, I probably will!

Though in real life, I'm going to implement at the very least a severe warning to the user once the statement includes a more than a couple of thousand ISBNs.