3 ms·
Alternatively: a new type of cell in jupyter itself alongside 'code' and 'markdown' for sql work available regardless of kernel choice.
by seemslegit 6y ago
Alternatively: a new type of cell in jupyter itself alongside 'code' and 'markdown' for sql work available regardless of kernel choice.
- jedimastert 6y agoWhat's the distinction between "SQL" and "code"?
- seemslegit 6y ago'code' would be the code of whatever kernel is in use and 'sql' would a notebook-level feature like 'markdown' is today.
- 3l3ktr4 6y agoYeah, I had this idea at first, but it's not trivial to run more than one kernel at the same time. I know some examples of people who did it, and some projects that I could plug in and try to make it work with my kernel, but this was a first version to see how the community responds! Let's see, might do something like it in the future. I think it'd be really cool and powerful to make it interact with Python for example.
- cheez 6y agoYes this is a great first step. Would absolutely love a way to use this alongside my Python code.
- pletnes 6y agoThere’s already the %%bash cell magic, which does that for bash.