saaj

I don't think SQLite is needed in between in this case. Yes, then there's an issue with inconsistency of the SQL dialect(s) in UI ([datafusion][1]'s in case of `roapi`), but...

> It took me a second to understand the thought process [...] That's reciprocal ;-) But I'm curios to understand your idea. How sqliteviz works now (and should continue) --...

> I agree in that scenario I am not sure how you would standardize all the functions and operations across multiple platforms. I guess there has already been some standardisation...

https://asciiflow.com/

No, even though one can emulate [temporary tables][1] with `DROP TABLE IF EXISTS`, transactions, `DELETE` or what not. Current solution (connection per query) is optimal for: - providing users temporary...

The application's design and trade-offs obviously cater to only its existing features. Currently sqliteviz operates on single SQLite database and doesn't support `ATTACH` (in any meaningful way). Hence a discussion...

Here's a [Hacker News discussion][1] on [dpapathanasiou/simple-graph][2] (which goes all over the place and can be a good overview) which has similar approach to storing graphs in SQLite (document-oriented upfront,...

The workflow w.r.t. filtering should stay as is for any new visualisation components. 1) Drop database/CSV, 2) write SQL to produce desired result set, 3) explore the result set with...

The same here: - Linux Mint 17.1 - Thunderbird 31.7.0 - FireTray 0.5.6.1

For PulseAudio there's great [PulseEffects][1] (available on FlatHub so it's very easy to install) which is the EQ suggested by [AutoEq][2] (the project that helps to neutralise frequency response of...