Description
First of all, awesome integration between two awesome tools. Quickly explored the marimo notebook inside DataSpell and it seems to be working very nicely.
One of the best features in DataSpell with Jupyter Notebooks is the possibility to add a '%sql' cell.
This cell allows to define a sql query in the cell, select a connection from dataspell to any of your sources and execute the sql statement, returning it as a dataframe for further processing. Very powerful feature where you don't have to setup new connection/import packages, but use the DataSpell wrapper.
If this could be a feature inside the marimo notebook plugin, where you can pick one of the existing DataSpell/DataGrip database connections as a connection in the notebook - that would be awesome.
The only caveat (also with the .ipynb files) is that it always has to run inside DataSpell and does need some tampering to make it run standalone. But for teams standardizing on DS that would not be an issue.
Alternatives
No response
Additional context
No response
Are you willing to submit a PR? (Please confirm the feature fits the roadmap before submitting.)
Description
First of all, awesome integration between two awesome tools. Quickly explored the marimo notebook inside DataSpell and it seems to be working very nicely.
One of the best features in DataSpell with Jupyter Notebooks is the possibility to add a '%sql' cell.
This cell allows to define a sql query in the cell, select a connection from dataspell to any of your sources and execute the sql statement, returning it as a dataframe for further processing. Very powerful feature where you don't have to setup new connection/import packages, but use the DataSpell wrapper.
If this could be a feature inside the marimo notebook plugin, where you can pick one of the existing DataSpell/DataGrip database connections as a connection in the notebook - that would be awesome.
The only caveat (also with the .ipynb files) is that it always has to run inside DataSpell and does need some tampering to make it run standalone. But for teams standardizing on DS that would not be an issue.
Alternatives
No response
Additional context
No response
Are you willing to submit a PR? (Please confirm the feature fits the roadmap before submitting.)