My thought here is that this was failing due to mutating the underlying data, as simply spreading state to make a copy only made a shallow 1-layer deep copy, so the delete command was trying to directly mutate data in the store (because queries.queriesById is only a pointer at this point, not a copied value) - _.omit() returns a brand new object without mutating, and this is generally regarded as best practice. I fixed that by bringing in lodash.omit and just omitting that key instead. In this PR I also made the selectedQuery value get passed into the actions - my initial plan for implementation was going to have me updating only changed parts, but decided it was easier to just store an entire snapshot of the queries object from the store.ĭuring this PR I somehow introduced a bug in the REMOVE_QUERY reducer, at the line where the removed query was being deleted from the queriesById object. ~~I think I'm going to just default to tab 1 on every load, because if tab 1 is the initial tab it works fine.~~ Fixed it - See below I don't know why, but if I can't figure that out.~~ ~~Right now I have an odd bug in that if your last selected tab was any besides the first, and you log out then back in and select tab 1, it won't pop in the text for tab 1 until you click the editor pane. When selecting a server, upon successful connection I'm retrieving the stored data and dispatching an action to put it in the store if a stored query list exists. I'm persisting store.queries by serverId in the sqlectron.json file on every action that updates queries, debounced by 500ms.
SQLECTRON SCREENSHOTS INSTALL
~~Currently in progress but looking for feedback - Mostly done, just need to thoroughly test it.~~ Finished Things you'll like about Sqlectron: Probability a database or language-agnostic Simple and easy to use Easy database environment configuration Prestigous authorship Sqlectron Screenshots: Installation Quick Start To install Sqlectron, the default Python version is required to be 2.7. (/home/grelek/downloads/sqlectron-gui-1.8.0/node_modules/electron-builder/src/build-cli.ts:47:2)Īt Object.Module._extensions.js (module.js:550:10)Īt Function.Module._load (module.js:407:3)Īt (module.js:575:10)Īlso, here's Gist of the npm-debug.log file.
(/home/grelek/downloads/sqlectron-gui-1.8.0/node_modules/electron-builder/src/platformPackager.ts:245:13)Īt processImmediate (timers.js:523:5)Īt tsAwaiter (/home/grelek/downloads/sqlectron-gui-1.8.0/node_modules/electron-builder/src/awaiter.ts:10:47)Īt Object.build (/home/grelek/downloads/sqlectron-gui-1.8.0/node_modules/electron-builder/src/builder.ts:30:59)Īt Object. github/ workflows Replace GHTOKEN with GITHUBTOKEN last year.
SQLECTRON SCREENSHOTS CODE
sqlectron / sqlectron-gui Public main 8 branches 54 tags Code MasterOdin Fix spurious sqlite e2e test failure ( 704) 5ec4fec on 1,061 commits. Seems like a wrong configuration.Īt LinuxPackager. GitHub - sqlectron/sqlectron-gui: A simple and lightweight SQL client desktop with cross database and platform support. out/browser/main.js could not be found in package. Custom Scrollbar React Libraries Forms Material Design React UI Component React Integration Sqlectron-gui - A simple and lightweight SQL client desktop with cross database and platform support. The installation worked fine, but the build command fails with following message: Error: Application entry file. Sqlectron-gui - A simple and lightweight SQL client desktop with cross database and platform support. Main use case is data scientists / data analysts / SQL power users.I tried to build sqlelectron 1.8 from source on Arch Linux and the build command fails.
Perhaps a fork with the admin features stripped out, some additional plumbing added, and read-only connections, I'm not sure. I've seen a few applications that are coming close listed on HN lately, but would be nice to have something as pretty as this and which is open source. Something lighter weight than BI tools such as Power BI, Tableau, Qlik, etc., definitely lighter weight than tools such as SSMS, DBeaver, SQuirrel, etc. And not embedded in MS Excel, like PowerQuery or PowerPivot (although it's powerful!). A simple "SQL notebook" that was cross platform, if you will, but worked more like a traditional query tool. On a side-note, I'd love to see an even more minimalist stripped-down, read-mostly query/tabular result only (with pivot tables) tool, which had some local columnar storage caching/query engine, and simple import/export to common file formats as well. I observed the fact that SQL Server had no management tool that was cross-platform, and thought perhaps I would build such a thing.
I guess it's a good thing I didn't do the project I was thinking about. Sqlectron - One single DB client for any relational DB A simple and lightweight SQL client desktop/terminal with cross database and platform support.
0 kommentar(er)
