4 ms·
Oh this looks good. I've been using: https://sqlitebrowser.org/ https://sqlitebrowser.org/ This seems to offer way more.
by account-5 4y ago
Oh this looks good. I've been using: https://sqlitebrowser.org/ https://sqlitebrowser.org/
This seems to offer way more.
- justinclift 4y agoAs a thought - unlike the current stable build - our nightly builds can open multiple "Browse Data" tabs at the same time. Aka: view multiple tables simultaneously. https://nightlies.sqlitebrowser.org/latest/ https://nightlies.sqlitebrowser.org/latest/ We're really overdue for making a new official release, but the nightly builds are pretty stable in the meantime. :)
- jdthedisciple 4y agoBeen using the same, and I've been very content with it too. Curious about this one.
- MPlus88 4y ago[dead]
- chasil 4y agoI've never tried this, but it appears to be possible to use Oracle SQL Developer to browse SQLite tables. https://github.com/Trivadis/sqldev-jdbc-proxy https://github.com/Trivadis/sqldev-jdbc-proxy Oracle SQL Developer is a Java clone of Toad from Quest software: https://www.oracle.com/database/sqldeveloper/ https://www.oracle.com/database/sqldeveloper/ Toad also bears a resemblance to the Windows app in the post.
- precompute 4y ago>sqlitebrowser Been using this for years. Fantastic tool.
- EMM_386 4y agoI love DB Browser. It's fast, does what I need it to, is open source ... great little tool.
- scary-size 4y agoIt's a blessing. I loath the slow feedback cycles your get in the BigQuery Web UI. Even for "small" tables, that would fit on your machine. When I expect a longer data exploration or debugging phase, I dump the BQ tables to SQLite. Opening that with SQLite browser lets me iterate very fast.
- Jgrubb 4y agoInteresting idea, thanks. I never, ever use the BQ UI for querying unless I absolutely have to. We use Metabase for BI, which we plug into all of our development datasets and do the exploration and iterating there which still requires network round trips and I could see how your approach would be faster.
- kyrra 4y agoGoogler opinions are my own. I know little about BQ. My understanding of Big query is that at least some of the tech it's based on allows for handling very large datasets. I'm talking being able to search BI that is petabytes in size. I don't think it's really designed for small datasets. If you can stick the data in SQLite, I think you're using the wrong tool. Searching around, it looks like BI Engine may help in cases like this. See: https://cloud.google.com/blog/topics/developers-practitioners/speeding-small-queries-bigquery-bi-engine https://cloud.google.com/blog/topics/developers-practitioner...
- scary-size 4y agoThat's true. Most of our production data is in the "petabyte" category. But often we start out with a small amount of data, for example for a new feature or product. That's when a lot of the exploration and query building happens. Once that's done, we leverage BigQuery to scale this up, serving a few hundred million users. There's a platform/standardisation component to this as well. We want our devs to use a single tool for all of their OLAP uses cases.
- kyrra 4y agoTotally makes sense, I guess I do the same thing internally (using partitioned tables, so the queries are a lot smaller, or making sure to only select the minimum columns to prove my query is correct). I also have no clue if my internal queries end up using something like BI Engine where it'll cache data in memory (much of this is opaque to me), but turn around is at least a few seconds per request. Your point is valid here, thanks for raising it.