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
Opening this on behalf of a user who proposed this. I think the behavior would simply be that when you click on new question -> native/sql, that it would default to whichever database you last selected in that database dropdown. This would remove a click if you tend to query the same database most of the time.
⬇️ Please click the 👍 reaction instead of leaving a +1 or update? comment
The text was updated successfully, but these errors were encountered:
It would probably easiest to just use the browser's localStorage for things like this, unless we want to add some sort of user preferences JSON object that gets persisted on the users table. The only downside of localStorage is it wouldn't persist for the user across multiple browsers/devices, but that seems like a pretty minor inconvenience.
If we're trying to reduce friction we could also just add a user setting for "Default ask a question to SQL" so if you hit the new question button you go right to the sql editor. I'd imagine if you're writing a lot of SQL both the "SQL" choice and which DB selection are both frequent friction points.
Opening this on behalf of a user who proposed this. I think the behavior would simply be that when you click on new question -> native/sql, that it would default to whichever database you last selected in that database dropdown. This would remove a click if you tend to query the same database most of the time.
⬇️ Please click the 👍 reaction instead of leaving a
+1
orupdate?
commentThe text was updated successfully, but these errors were encountered: