add tag
Anonymous 2333
This SQL statement produces an "{"message":"Internal Server Error"}"
```
select * from information_schema.`COLUMNS`
```

I was trying to do this query because of this stackoverflow:
https://stackoverflow.com/questions/73660965/select-column-from-multiple-unknown-tables

While it may be logical that this query is not allowed, it would be nice if a simple error was returned instead of the "Internal Server Error".

Top Answer
Jack Douglas
Thanks for prompting me to fix this bug

In the background, some db<>fiddle engines now produce markdown for their results, which is rendered server-side 'on the fly'. With a big (lots of rows and columns) result like that we were getting timeout errors. I've increased the timeout from 3s to 30s (the maximum) and also increased the memory available to the lambda that does the rendering - the latter has made a big difference.

You still have to wait 5+ seconds for the page to load with that query.

> it would be nice if a simple error was returned instead of the “Internal Server Error”.

I agree but now I'm tracking these errors too with Sentry I hope to be able to get rid of them more or less completely.

Enter question or answer id or url (and optionally further answer ids/urls from the same question) from

Separate each id/url with a space. No need to list your own answers; they will be imported automatically.