-
Notifications
You must be signed in to change notification settings - Fork 4.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow for forking the query and retaining the schedule #424
Comments
Actually this is by design. I wanted to avoid situation that queries get scheduled by mistake, just because the original one was scheduled. |
mrmr. I'm mostly forking queries to make them execute at another does the query results cache works by hashing the query text or it does it On Mon, May 11, 2015 at 2:48 PM, Arik Fraimovich notifications@github.com
|
Well, the use case around fork is usually different: you want to fork it to play around with the query or change something. In such cases, caching won't help as the user will end up running a different query (but you're correct that it's done using query text). I won't change the default behavior of fork, but it's possible to add another fork button that retains the scheduling... |
Super Fork? On Tue, May 12, 2015 at 2:56 AM, Arik Fraimovich notifications@github.com
|
It's not a common enough use case to make the UI more complex than it is now. |
The text was updated successfully, but these errors were encountered: