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
It would be really nice to be able to "update" a plan and query and be able to see all revisions from the same URL. It would be even better if you could do things like show 2 plans side by side or show diffs in the query.
I could see this being useful when trying to optimize a query where you could see old versions and how things change. It could also be useful as a teaching tool. Sometimes I'll create before and after plans with teammates to help show what some optimizations can do to slow queries.
The text was updated successfully, but these errors were encountered:
I frequently need to compare plans. Unfortunately use diff on the json doesn't work so great because while the plans look very similar, all of the numbers are different. Instead I open side-by-side browser windows and keep flipping back and forth.
My "dream feature" for explain.dalibo would be to come up with a way to highlight the biggest differences between two query plans. I think it plays nicely into your versioning idea.
Sometimes I'm comparing the plans for changes to the query itself.
Sometimes I'm comparing plans for the same query where I changed database parameters.
Sometimes I'm comparing plans for the same query but with different date ranges, or other data set variances.
Sometimes I'm comparing plans for the same query, but on two different databases.
It would be really nice to be able to "update" a plan and query and be able to see all revisions from the same URL. It would be even better if you could do things like show 2 plans side by side or show diffs in the query.
I could see this being useful when trying to optimize a query where you could see old versions and how things change. It could also be useful as a teaching tool. Sometimes I'll create before and after plans with teammates to help show what some optimizations can do to slow queries.
The text was updated successfully, but these errors were encountered: