2 ms·

Moving dataview entries between data views is fundamentally at odds with the paradigm in which dataview operates. The point is that it's ephemeral data that's e

Moving dataview entries between data views is fundamentally at odds with the paradigm in which dataview operates. The point is that it's ephemeral data that's entirely derived from the state of your notes. Maybe there are some basic queries that could support "two-way binding" of this sort, but it would be fiendishly complex and ultimately better solved by a different tool altogether

slightwinder 4y ago
> Moving dataview entries between data views is fundamentally at odds with the paradigm in which dataview operates. It doesn't need to be between dataviews. Just temporary filter the view, or export it in a regular static table. This is just about enhancing the View, not changing the concept. Which opens the question, can dataview also take tables as data-source? > Maybe there are some basic queries that could support "two-way binding" of this sort I'm not talking about Two-way-bindings. Though this would be awesome. And I don't think it would be that hard to implement in general, depening on how exactly obsidian works internally with dataview.