We need to redo the error page for when a query times out.
This is what it looks like now:
I have a couple suggestions. Where it says:
"0 rows were selected on main before query timed out. For unlimited query execution time, download Dolt and execute the following:"
It should say:
"0 rows were selected on main before query timed out.
Dolt is a decentralized database. You can clone a copy locally to read and write with unlimited query time."
Then below the query. There should be a "Why did this query time out?" section.
It should say something like:
"DoltHub is an offline copy of Dolt. In order to execute the query, DoltHub's API has to clone the database into memory and execute the query. So query execution time is effectively clone + query time. For large databases (> 1GB), clone itself will likely consume all the query time. See more DoltHub query execution architecture details [here]()."
That here should link to a blog or documentation page with some pictures.
We need to redo the error page for when a query times out.
This is what it looks like now:
I have a couple suggestions. Where it says:
"0 rows were selected on main before query timed out. For unlimited query execution time, download Dolt and execute the following:"
It should say:
"0 rows were selected on main before query timed out.
Dolt is a decentralized database. You can clone a copy locally to read and write with unlimited query time."
Then below the query. There should be a "Why did this query time out?" section.
It should say something like:
"DoltHub is an offline copy of Dolt. In order to execute the query, DoltHub's API has to clone the database into memory and execute the query. So query execution time is effectively clone + query time. For large databases (> 1GB), clone itself will likely consume all the query time. See more DoltHub query execution architecture details [here]()."
That here should link to a blog or documentation page with some pictures.