Feature Request: Saving rendered Table

[satkowski]

One problem I have with tools like sqlSeal and Dataview is, that the rendered output is only temporary. This means, that as soon as I remove the plugin or even use the files within another editor (e.g., VS Code), I cannot see the output of the query.

Therefore, I would like for a feature to save a version of the rendered output directly into the respective markdown file. I could imagine that an additional keyword (similar to "REFRESH" or "EXPLAIN" could be used, or the code block type could be something like "sqlseal-print". If any of such flags are present in the code, the code block will not get rendered as a table (as currently done) but will write the output below the code block in question. In editing mode, the code block is still rendered, while in reading mode, the code block gets hidden/removed.

Something like this would be really neat and would allow me to embed it entirely in my current workflow. Afterall, I want to have all my data present, even if I don't use a plugin anymore.

[kulak-at]

Hi, I converted it to the Discussion Idea so it's easier to track it.
This is good idea even though it's not really in line with the initial idea for this plugin. I can see this potentially as a separate plugin that would embed this new functionality, similarly to the SQLSeal Charts.

From what I understand you would like 2 modes: let's call them REPLACE QUERY and WRMATERIALISEITE TABLE (maybe someone has better idea for the name) that would:

• REPLACE QUERY - replaces whole codeblock once it's executed with the result. It would result with one off query that generates static table inside your note.
• MATERIALISE TABLE - that would create table underneath the query (which could be invisible in Obsidian) but would allow you to access the data from outside Obsidian if needed.

Is there anything else you had in mind here?

[satkowski]

Thanks for picking up on my idea!

You correctly summarized my thoughts. It all boils down to a query that manipulates the markdown content directly. Generally, I'm not a big fan of plugins that write in my files, but I see a high value in having the tables generated by SQL seal present as "real" markdown tables in my files.

Providing this through an additional plugin also makes sense, as this can make it clear that this new plugin can manipulate your content, while the core plugin does not.

Overall, I could also imagine to help with that. I already wanted to try writing plugins for Obsidian, but never came around until now :D

[kulak-at]

Great! It would be awesome if you helped out with that. Me and other in our community can definitely help you with starting it! Join our Discord, we have other contributors starting on their plugins there too!