A way to pre-fill database connection information in Navicat Premium application

Abstract

The present invention discloses a method for pre-filling database connection information in a Navicat Premium application, comprising a database, creating an SSH client execution command with a Windows account and manually writing into a registry of a Windows operating system; in the technical solution of the present invention, users of the Navicat Premium application manually fill in the database connection information, while the present solution can pre-fill the connection information for the user, thereby ensuring the security of the database connection information without exposing the database password, and improving the convenience of the user in operating the Navicat Premium application, while bringing a good user experience to the user.

Description

Technical Field

[0001] The present invention relates to the field of computer operation technology, and in particular to a method for pre-filling database connection information in a Navicat Premium application. Background Art

[0002] The current technical solution using Navicat Premium application is to inform the user of the database connection information and let the user fill it in the application manually. This not only exposes the database connection information, but also increases the complexity of the user's use of the application, and also brings a bad user experience. Summary of the invention

[0003] The object of the present invention is to provide a method for pre-filling database connection information in a Navicat Premium application to solve the problems raised in the above background technology.

[0004] To achieve the above object, the present invention provides the following technical solutions:

[0005] A method for pre-filling database connection information in Navicat Premium application, including database, creating SSH client to execute commands with Windows account and manually writing to Windows operating system registry;

[0006] Creating an SSH client to execute commands using a Windows account includes the following steps:

[0007] S101. Use the Windows account username and password to create an SSH client connection.

[0008] S102, obtaining an execution command for creating a new registry entry according to the connection information details of the database;

[0009] S103, execute the command of creating a new registry key: execute the command through the SSH client, and if successful, complete the filling of the database connection information in the Navicat Premium application;

[0010] S104. Access Navicat Premium application: When the Windows account accesses the Navicat Premium application, the database connection information that has been filled in the connection information directory can be viewed and accessed through the connection information;

[0011] Manually writing to the Windows operating system registry includes the following steps:

[0012] S201, open the registry;

[0013] S202: Find the location where the item is to be written according to the connection section information details of the database and manually create a new registry entry to write the database connection information.

[0014] Preferably, the database connection includes a MySQL data connection, an Oracle data connection, a SQL Server data connection, a MongnDB data connection, a PostgreSQL data connection, a MariaDB data connection and a SQLite data connection.

[0015] Preferably, the MySQL data connection includes a database host address, a database port, a database user name and an encrypted database password.

[0016] Preferably, the Oracle data connection includes a database host address, a database port, a database user name, an encrypted database password and a service name.

[0017] Preferably, the SQL Server data connection includes an initial database, a verification method and a Native Client driver.

[0018] Preferably, the MongnDB data connection includes a database host address, a database port, a database user name, an encrypted database password and a connection method.

[0019] Preferably, the PostgreSQL data connection includes a database host address, a database port, a database user name, an encrypted database password and an initial database.

[0020] Preferably, the MariaDB data connection includes a database host address, a database port, a database user name and an encrypted database password.

[0021] Preferably, the SQLite data connection includes a database user name, an encrypted database password and a database file.

[0022] Preferably, the connection mode in the MongnDB data connection includes Standalone, Shard Cluster or Replica Set.

[0023] Compared with the prior art, the present invention has the following beneficial effects:

[0024] The technical solution of the present invention requires users of the Navicat Premium application to manually fill in the database connection information, while the present solution can fill in the connection information for the user in advance, ensuring the security of the database connection information without exposing the database password, and improving the convenience of the user's operation of the Navicat Premium application, while bringing a good user experience to the user. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1 The present invention is a flowchart of creating an SSH client execution command using a Windows account. DETAILED DESCRIPTION

[0026] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention. Example

[0027] See also Figure 1 ,The present invention provides a technical solution: a method for pre-filling database connection information in Navicat Premium application, including database, creating SSH client execution command with Windows account and manually writing into the registry of Windows operating system;

[0028] Creating an SSH client to execute commands using a Windows account includes the following steps:

[0029] S101. Use the Windows account username and password to create an SSH client connection.

[0030] S102, obtaining an execution command for creating a new registry entry according to the connection information details of the database;

[0031] S103, execute the command of creating a new registry key: execute the command through the SSH client, and if successful, complete the filling of the database connection information in the Navicat Premium application;

[0032] S104. Access Navicat Premium application: When the Windows account accesses the Navicat Premium application, the database connection information that has been filled in the connection information directory can be viewed and accessed through the connection information;

[0033] Manually writing to the Windows operating system registry includes the following steps:

[0034] S201, open the registry;

[0035] S202: Find the location where the item is to be written according to the connection section information details of the database and manually create a new registry entry to write the database connection information.

[0036] Specifically, the database connection includes MySQL data connection, Oracle data connection, SQL Server data connection, MongnDB data connection, PostgreSQL data connection, MariaDB data connection and SQLite data connection.

[0037] Specifically, the MySQL data connection includes a database host address, a database port, a database user name and an encrypted database password.

[0038] Specifically, the Oracle data connection includes a database host address, a database port, a database user name, an encrypted database password and a service name.

[0039] Specifically, the SQL Server data connection includes an initial database, a verification method, and a Native Client driver.

[0040] Specifically, the MongnDB data connection includes the database host address, database port, database user name, encrypted database password and connection method.

[0041] Specifically, the PostgreSQL data connection includes a database host address, a database port, a database user name, an encrypted database password and an initial database.

[0042] Specifically, the MariaDB data connection includes a database host address, a database port, a database user name, and an encrypted database password.

[0043] Specifically, the SQLite data connection includes a database user name, an encrypted database password and a database file.

[0044] Specifically, the connection modes in the MongnDB data connection include Standalone, Shard Cluster or Replica Set.

[0045] In the description of the present invention, unless otherwise clearly specified and limited, the terms "installed", "connected", "connected", and "fixed" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be directly connected, directly connected, or indirectly connected through an intermediate medium, and it can be the internal connection of two elements or the interaction relationship between two elements. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0046] The standard parts used in the present invention can all be purchased from the market, and special-shaped parts can be customized according to the description in the specification and the drawings. The specific connection methods of each part adopt conventional means such as mature bolts, rivets, welding, etc. in the prior art. The machinery, parts and equipment all adopt conventional models in the prior art, and the circuit connection adopts the conventional connection method in the prior art, which will not be described in detail here.

[0047] Although embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present invention, and that the scope of the present invention is defined by the appended claims and their equivalents.

Claims

1. A method for pre-filling database connection information in a Navicat Premium application, characterized in that: Including database, creating SSH client execution command with Windows account and manually writing into Windows operating system registry; creating SSH client execution command with Windows account includes the following steps: S101. Use the Windows account username and password to create an SSH client connection; S102, obtaining an execution command for creating a new registry entry according to the connection information details of the database; S103, execute the command of creating a new registry key: execute the command through the SSH client, and if successful, complete the filling of the database connection information in the Navicat Premium application; S104. Access Navicat Premium application: When the Windows account accesses the Navicat Premium application, the database connection information that has been filled in the connection information directory can be viewed and accessed through the connection information; Manually writing into the registry of the Windows operating system includes the following steps: S201, opening the registry; S202, find the location to be written according to the connection section information details of the database and manually create a new registry key to write the database connection information; The database connection includes MySQL data connection, Oracle data connection, SQL Server data connection, MongnDB data connection, PostgreSQL data connection, MariaDB data connection and SQLite data connection; The MongnDB data connection includes the database host address, database port, database user name, encrypted database password and connection method; The connection modes in the MongnDB data connection include Standalone, Shard Cluster or Replica Set.

2. A method for pre-filling database connection information in a Navicat Premium application according to claim 1, characterized in that: The MySQL data connection includes a database host address, a database port, a database user name and an encrypted database password.

3. A method for pre-filling database connection information in a Navicat Premium application according to claim 1, characterized in that: The Oracle data connection includes the database host address, database port, database user name, encrypted database password and service name.

4. A method for pre-filling database connection information in a Navicat Premium application according to claim 1, characterized in that: The SQL Server data connection includes an initial database, a verification method and a NativeClient driver.

5. A method for pre-filling database connection information in a Navicat Premium application according to claim 1, characterized in that: The PostgreSQL data connection includes a database host address, a database port, a database user name, an encrypted database password and an initial database.

6. A method for pre-filling database connection information in a Navicat Premium application according to claim 1, characterized in that: The MariaDB data connection includes the database host address, database port, database user name and encrypted database password.

7. A method for pre-filling database connection information in a Navicat Premium application according to claim 1, characterized in that: The SQLite data connection includes a database user name, an encrypted database password and a database file.

Images