You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: rasher [Submitted to the original trac issue database at 12.49pm, Sunday, 12th December 2010]
When opening a large relation, and the data retrieval times out, it would be nice if I could still see the relation tags, which I assume is a pretty lightweight query on the DB.
The text was updated successfully, but these errors were encountered:
Author: TomH [Added to the original trac issue at 8.59am, Monday, 13th December 2010]
This is not really an ideal solution because (a) it would be very hard to do and (b) most people probably give up long before the timeout fires anyway.
Author: Andy Allan [Added to the original trac issue at 12.59pm, Wednesday, 6th November 2019]
Thanks for the suggestion.
However, I think it would be best to concentrate on making the responses happen more quickly, rather than adding additional logic for what to do when they are so slow that they time out.
As such, we're not planning on implementing this fallback behaviour.
Reporter: rasher
[Submitted to the original trac issue database at 12.49pm, Sunday, 12th December 2010]
When opening a large relation, and the data retrieval times out, it would be nice if I could still see the relation tags, which I assume is a pretty lightweight query on the DB.
The text was updated successfully, but these errors were encountered: