Sqlectron create a new database
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. For example, when a user submits a new manifest, the operator fetches that manifest and spawns a new Postgres cluster along with all necessary entities such as Kubernetes StatefulSets and Postgres roles. ~~Currently in progress but looking for feedback - Mostly done, just need to thoroughly test it.~~ Finished The operator watches additions, updates, and deletions of PostgreSQL cluster manifests and changes the running clusters accordingly. (/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. Seems like a wrong configuration.Īt LinuxPackager. out/browser/main.js could not be found in package.
The installation worked fine, but the build command fails with following message: Error: Application entry file. You don’t need to append a semicolon to dot-commands like you do with SQL statements.I tried to build sqlelectron 1.8 from source on Arch Linux and the build command fails. These are interpreted by the command-line utility and not by SQLite itself. databases command is known as a “dot-command”. You can also navigate to the file using your computer’s file system. databases command to check that the database was created.databases For example: sqlite3 /Users/Shared/Pets.db Check that the Database was Created
#Sqlectron create a new database full
You can also use the full path to specify a database in another folder. If it had already existed the file would have been opened. That creates a new database file in the current directory called Pets.db.
#Sqlectron create a new database mac
So in my case, I can open the Terminal on my Mac and enter the following command: sqlite3 Pets.db If such a file exists, it will be opened, if not, a new database file will be created with that name. When you connect to SQLite, you have the option of providing a database file name. When you create a database with SQLite however, you do so by simply providing a filename. Most of the popular relational database management systems such as MySQL, SQL Server, PostgreSQL, and so on, use the CREATE DATABASE statement to create a database. SQLite uses a different syntax for creating databases to what many other relational database management systems use.