mplscorwin
commented
1 year ago I realize it has been quite some time since you opened this issue - I've just volunteered to help with ob-sql-mode and notice yours is the oldest "issue" standing 🥇 (I think it's actually an enhancement idea and have tagged it as such, but LMK..)
I think it might be possible to arrange for the SQL query buffer to pop or become current after a block was evaluated with sql-mode, IIUC.
Given you are still interested in this, did you have a particular ways you imagine this working?
- How should sql-mode know a user wants the sql-query buffer to pop after executing?
- Will users generally toggle this
- once (in init/customize), or
- per buffer (e.g. with header-arg), or
- per block execution (e.g. like a prefix key, which needs to be pressed before each
C-c C-c) - maybe several of these? (and then, in which case, which are most important and why?)
To prevent inserting query output, will :result none do what you want?
Do we also need something that will put the evaluation result into the kill-ring?
(and, if so, would that mean you don't really need to pop the sql result buffer? (and then, if further so does that decrease interest in a requirement to show the sql result buffer? (lol, stupid day jobs), or does it just inform thinking about (e.g.) options for controlling when/if/how the buffer will pop?))
Thank you for the suggestion (and in advance for such further thoughts as interests and time allow you to share)
It is possible to send the query to the sql process buffer and show the result there (without fetch the result on the org file)? I have some queries that I run on daily basis, and then copy the result to some spreadsheat, so I don't need that data on my org file.