81–90 of 114 posts
But why is it Windows only? Even as a Windows user, my professional day is spent on a Mac even if my Windows machine is running at the same time. What arcane library does it rely on that it can't just cross-compile for all three operating systems?
If you can do with an even leighter-weight client, you can try my very own https://sqliteviewer.app . It's all browser/wasm-based and works offline, but has some important shortcomings.
Earlier quoted context omitted.
I didn't assume you'd give a helpful answer, but I didn't expect you to give that kind of an answer, either. You're always welcome not to respond if this is taking too much of your time. I figured maybe at least one of us would learn something about high DPI issues, hence why I engaged. And I did just try what you said and the combo box fine to me: https://imgur.com/a/Mb83tPj
That is not the default Win32 combobox. I don't know what you're using, but it's not the plain c api.
Earlier quoted context omitted.
I didn't assume you'd give a helpful answer, but I didn't expect you to give that kind of an answer, either. You're always welcome not to respond if this is taking too much of your time. I figured maybe at least one of us would learn something about high DPI issues, hence why I engaged. And I did just try what you said and the combo box fine to me: https://imgur.com/a/Mb83tPj
That is not the default Win32 combobox. I don't know what you're using, but it's not the plain c api.
Earlier quoted context omitted.
This codebase is very much tied to the win32 API, maybe with the winelib wrapper but otherwise I wouldn't bother. Sibling post here mentioned using under wine but I'm not sure if that's the best idea since wine might not translate locking semantics in the same way and those might be plenty important to avoid corruption with SQLite databases.
SQLite is so very extremely popular that I don’t think you have to worry about corruption under Wine—if it was broken, a lot of software would be broken.
Would the semantics of the Linux based application (with SQLite compiled for Linux) correspond to the UI (with SQLite compiled for Windows) running through an API emulation layer (Wine) that potentially translates semantics to run Windows applications as "natively" as possible.
Sure it might, but I wouldn't put money on it until verified. (Luckily backing up SQLite databases isn't too hard)
Oh this looks good. I've been using: https://sqlitebrowser.org/ This seems to offer way more.
It'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.
I love that this looks very much like Query Analyzer, the lightweight querying tool that came with SQL Server 2000. Back then, server management, querying and profiling were handled by separate utilities that did one thing well. They were all replaced with SSMS, which was a slow abomination. Query Analyzer is my favourite SQL editing environment to this day. It was incredibly snappy, could render thousands of rows wi…
If you want an abomination, the Azure data studio makes SSMS look like query analyzer.
I still mostly use ADS for the git integration, file comparison, terminal, and file picker though.
SSMS only for those admin tasks where it has a nice GUI, or when ADS breaks in some way (happens a lot).
Earlier quoted context omitted.
>Kudos to the author for a meaningful screenshot right at the start. I was thinking about this recently that so many projects on Github missing screenshots. I was thinking to make PRs to at least show some basic functionality.
That's because adding a screenshot is surprisingly hard if you've never discovered that you can create an issue, paste an image into it, and then copy the URL that gives you into your readme without ever actually submitting the issue.
Oh this looks good. I've been using: https://sqlitebrowser.org/ This seems to offer way more.
It'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.
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-practitioner...
Earlier quoted context omitted.
It'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.
Googler 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 ca…