betodealmeida commented on issue #8055: [WIP] Persist SQL Lab state in the backend URL: https://github.com/apache/incubator-superset/pull/8055#issuecomment-522151540 @graceguo-supercat: > Thanks for the implementation. Can you describe the new architecture a little bit, like: > when and where to store sql lab state, > which state data is persist and which are not, > what is flow look like when user interact with multiple tabs and browsers? Everything is synced to the backend, including query, tales (and if expanded or not), data preview, results (fetched from the backend), tab title, active tab, selected DB, etc. All changes are stored asynchronously, and the sync of the SQL query itself is done with debouncing. For multiple tabs and browsers, the old experience remains: the last edit wins. I think we should improve that experience, but the goal for this PR is to move state management to the backend, without changing ay extra functionality.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
