Cooperative operation and maintenance method, system and equipment based on database web client and medium

Abstract

The invention relates to the technical field of database collaborative operation and maintenance, in particular to a collaborative operation and maintenance method, system and equipment based on a database web client and a medium. According to the method, a collaborative session is entered through a collaborative link, so that a collaborator can enter the collaborative session without an independent account, and session validity verification is completed at the same time; through a websocket technology, the real-time display performance of collaborative operation and maintenance is realized; the security and the flexible controllability of the collaborative session are realized through a collaborative credential mechanism, an operation and maintenance right control mechanism and a session right control mechanism; and the flexibility of sql statement control is realized through a collaborative level mechanism.

Description

Technical Field

[0001] The present invention relates to the technical field of database collaborative operation and maintenance, and in particular to a collaborative operation and maintenance method, system, device and medium based on a database web client. Background Art

[0002] In the database field, there is often a need for assistance from others who are not local. In the existing technology, most clients do not provide collaborative functions. In this case, the current database account can only be given to the assistant, or a temporary database account can be created for the assistant to facilitate collaborative operation and maintenance. However, this situation poses a security risk to the database account, and it does not have real-time collaborative display and statement controllability, so the manager cannot control the behavior of the collaborator. A small number of database web clients provide similar collaborative functions, but they also require the collaborator to have his own client system account. The statements of the collaborator during the operation and maintenance process are submitted to the management personnel for approval before execution. In this case, the manager can only control the execution of the statement, and the collaborator can log in to the system at any time, so there is no controllability of the session, and the real-time display of the statement is not high enough.

[0003] Therefore, it is particularly important to provide a collaborative operation and maintenance design method with sufficiently high data account security, real-time display of collaborative operation and maintenance, session controllability, SQL statement controllability, and SQL statement execution flexibility.

[0004] In order to solve the problems of collaborative real-time and statement controllability, the existing technical work order mechanism solves the problems of collaborative real-time and statement controllability from the perspective of work orders. The specific solution is that when the collaborating party runs the SQL statement, some statements that require approval will automatically generate a work order. After the manager logs in to the system, he can view the work order and approve it.

[0005] Although the existing work order mechanism solves the real-time and statement controllability of collaborative operation and maintenance, it requires the collaborator to have his own client system account. Therefore, the collaborator can log in to the client system at any time, so there is no session controllability, and only the SQL statements in the work order will be displayed to the administrator, and the execution results will not be displayed, so the real-time display of the statement is not high enough. Summary of the invention

[0006] In order to solve the problem that the SQL statements in the above-mentioned work orders will be displayed to the administrator but the execution results will not be displayed, and the real-time display of the statements is not high enough, the present invention proposes a collaborative operation and maintenance method, system, equipment and medium based on a database web client; the method enters the collaborative session through a collaborative link, so that the collaborators can enter the collaborative session without a separate account and complete the session validity verification at the same time; the real-time display of collaborative operation and maintenance is realized through websocket technology; the security and flexible controllability of the collaborative session are realized through a collaborative credential mechanism, an operation and maintenance rights control mechanism and a session rights control mechanism; the flexibility of SQL statement control is realized through a collaborative level mechanism.

[0007] The specific implementation contents of the present invention are as follows: A collaborative operation and maintenance method based on a database web client specifically includes the following steps: Step S1: Log in to the database web client and configure the collaboration level; Step S2: generating a collaborative link according to the acquired session information, and sending the collaborative link to the collaborator through an external communication method; Step S3: input the collaborative link into the browser, and determine whether the collaborative link is valid on the database web client. If it is valid, execute step S4; if it is invalid, disconnect the collaborative session; Step S4: Enter the collaborative session according to the collaborative link to perform collaborative operation and maintenance, and determine whether the collaborator has the operation and maintenance rights. If the collaborator does not have the operation and maintenance rights, a permission error is prompted, otherwise, step S5 is executed; Step S5: When executing collaborative operation and maintenance, a SQL statement is generated, and whether the SQL statement needs approval is determined based on the configured collaboration level. If the approval is passed, the collaborative operation and maintenance operation is executed. If the approval fails, an approval rejection prompt is displayed.

[0008] In order to better implement the present invention, further, the step S2 specifically includes the following steps: Step S21: Obtaining session information from the database web client; Step S22: Generate a collaboration credential based on the session information; Step S23: Generate a collaborative link based on the collaborative credentials and the IP information of the session information, and send the collaborative link to the collaborator through an external communication method.

[0009] In order to better implement the present invention, further, the step S3 specifically includes the following steps: Step S31: input the collaborative link into the browser, extract the collaborative credentials from the collaborative link, and deny access if the extraction fails; Step S32: searching the cache for session information related to the collaborative credentials according to the extracted collaborative credentials, and denying access if the session information is not found; Step S33: Associating the collaborative session with the operation and maintenance session according to the session information, and deleting the collaborative credentials in the cache; Step S34: determine whether the collaborative link is valid, if it is valid, execute step S4, if it is invalid, disconnect the collaborative session.

[0010] In order to better implement the present invention, further, the collaboration level in step S1 includes a first level, a second level, a third level, and a fourth level; The first level allows all statements to execute: The second level is used to allow all query statements to be executed, and non-query statements to be executed after approval; The third level is used to allow all query statements to be executed, and non-query statements are automatically rejected; The fourth level is used to approve all statements. Each operation of the collaborator needs to be approved before the next step can be executed.

[0011] In order to better implement the present invention, further, step S5 specifically includes the following steps: Step S51: when performing collaborative operation and maintenance, convert the operation and maintenance operation into a corresponding SQL statement; Step S52: classify the SQL statements into query and non-query categories; Step S53: calling the websocket technology to display the classified SQL statements; Step S54: According to the configured collaboration level and the category of the SQL statement, determine whether the SQL statement needs approval. If the approval is passed, perform collaborative operation and maintenance operations. If the approval fails, prompt approval rejection.

[0012] In order to better implement the present invention, further, the specific operation of step S54 is: according to the configured collaboration level and the category of the SQL statement, determine whether the SQL statement needs approval. If the SQL statement can be executed directly, execute the SQL statement and display the execution result through websocket; if the SQL statement cannot be executed, prompts will be given on the collaborator and manager pages; if the SQL statement needs approval, a pending approval box will pop up on the manager page; if the manager's approval result is "agree", execute the SQL statement and display the execution result through websocket; if the manager's approval result is "reject", do not execute the SQL statement, and prompts will be given on the collaborator and manager pages.

[0013] Based on the above-mentioned collaborative operation and maintenance method based on database web client, in order to better realize the present invention, further, a collaborative operation and maintenance system based on database web client is proposed, which is used to execute the above-mentioned collaborative operation and maintenance method based on database web client; it includes a configuration module, a collaborative credential management module, a session right control module, an operation and maintenance right control module, and a statement control module; The configuration module is used to log in to the database web client and configure the collaboration level; The collaborative credential management module is used to generate a collaborative link according to the acquired session information, and send the collaborative link to the collaborator through an external communication method; The session right control module is used to input the collaborative link into the browser, and determine whether the collaborative link is valid on the database web client. If it is valid, step S4 is executed; if it is invalid, the collaborative session is disconnected; The operation and maintenance rights control module is used to enter the collaborative session according to the collaborative link to perform collaborative operation and maintenance, and determine whether the collaborator has the operation and maintenance rights. If the collaborator does not have the operation and maintenance rights, it prompts that the authority is wrong, otherwise it executes step S5; The statement control module is used to generate SQL statements when executing collaborative operation and maintenance, and determine whether the SQL statements need approval based on the configured collaboration level. If the approval is passed, the collaborative operation and maintenance operation is executed. If the approval fails, the approval rejection is prompted.

[0014] Based on the above-proposed collaborative operation and maintenance method based on a database web client, in order to better realize the present invention, further, an electronic device is proposed, including a memory and a processor; a computer program is stored on the memory; when the computer program is executed on the processor, the above-proposed collaborative operation and maintenance method based on a database web client is implemented.

[0015] Based on the above-proposed collaborative operation and maintenance method based on database web client, in order to better realize the present invention, further, a computer-readable storage medium is proposed, on which computer instructions are stored; when the computer instructions are executed on the above-mentioned electronic device, the above-mentioned collaborative operation and maintenance method based on database web client is implemented.

[0016] The present invention has the following beneficial effects: The present invention realizes the real-time display of collaborative operation and maintenance through websocket technology, realizes the security and flexible controllability of collaborative sessions through collaborative credential mechanism, operation and maintenance right control mechanism and session right control mechanism, and realizes the flexibility of SQL statement control through collaborative level mechanism. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1A schematic diagram of the overall process of the collaborative operation and maintenance method based on the database web client provided by the present invention.

[0018] Figure 2 A schematic diagram of the overall structure of the collaborative operation and maintenance system based on the database web client provided by the present invention. DETAILED DESCRIPTION

[0019] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. It should be understood that the described embodiments are only part of the embodiments of the present invention, not all of the embodiments, and therefore should not be regarded as limiting the scope of protection. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technical personnel in this field without making creative work are within the scope of protection of the present invention.

[0020] In the description of the present invention, it should be noted that, unless otherwise clearly specified and limited, the terms "disposed", "connected", and "connected" 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 a direct connection, or it can be an indirect connection through an intermediate medium, or it can be the internal communication of 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.

[0021] The complete English corresponding to the professional terms and English abbreviations involved in this embodiment are as follows: Database web client: a client system that accesses the database through a browser; websocket: websocket: a full-duplex communication protocol that communicates on a single tcp connection, allowing the service party to actively send data to the client party.

[0022] sql: The full English name is structured query language, which is a computer language for operating databases.

[0023] Client system account: database client system account; Database account: the real database account; Operation and maintenance rights: the right to operate the database; Session rights: The right to use the client system. If there is no session right, the existing session connection will be disconnected.

[0024] Embodiment 1: This embodiment proposes a collaborative operation and maintenance method based on a database web client, which specifically includes the following steps: Step S1: Log in to the database web client and configure the collaboration level.

[0025] Furthermore, the collaboration level in step S1 includes a first level, a second level, a third level, and a fourth level; The first level allows all statements to execute: The second level is used to allow all query statements to be executed, and non-query statements to be executed after approval; The third level is used to allow all query statements to be executed, and non-query statements are automatically rejected; The fourth level is used to approve all statements. Each operation of the collaborator needs to be approved before the next step can be executed.

[0026] Step S2: Generate a collaborative link according to the acquired session information, and send the collaborative link to the collaborator through an external communication method.

[0027] Furthermore, the step S2 specifically includes the following steps: Step S21: Obtaining session information from the database web client; Step S22: Generate a collaboration credential based on the session information; Step S23: Generate a collaborative link based on the collaborative credentials and the IP information of the session information, and send the collaborative link to the collaborator through an external communication method.

[0028] Step S3: Input the collaborative link into the browser, and determine whether the collaborative link is valid on the database web client. If it is valid, execute step S4; if it is invalid, disconnect the collaborative session.

[0029] Furthermore, the step S3 specifically includes the following steps: Step S31: input the collaborative link into the browser, extract the collaborative credentials from the collaborative link, and deny access if the extraction fails; Step S32: searching the cache for session information related to the collaborative credentials according to the extracted collaborative credentials, and denying access if the session information is not found; Step S33: Associating the collaborative session with the operation and maintenance session according to the session information, and deleting the collaborative credentials in the cache; Step S34: determine whether the collaborative link is valid, if it is valid, execute step S4, if it is invalid, disconnect the collaborative session.

[0030] Step S4: Enter the collaborative session according to the collaborative link to perform collaborative operation and maintenance, and determine whether the collaborator has the operation and maintenance rights. If the collaborator does not have the operation and maintenance rights, a permission error is prompted, otherwise step S5 is executed.

[0031] Step S5: When executing collaborative operation and maintenance, a SQL statement is generated, and whether the SQL statement needs approval is determined based on the configured collaboration level. If the approval is passed, the collaborative operation and maintenance operation is executed. If the approval fails, an approval rejection prompt is displayed.

[0032] Furthermore, the step S5 specifically includes the following steps: Step S51: when performing collaborative operation and maintenance, convert the operation and maintenance operation into a corresponding SQL statement; Step S52: classify the SQL statements into query and non-query categories; Step S53: calling the websocket technology to display the classified SQL statements; Step S54: According to the configured collaboration level and the category of the SQL statement, determine whether the SQL statement needs approval. If the approval is passed, perform collaborative operation and maintenance operations. If the approval fails, prompt approval rejection.

[0033] Furthermore, the specific operation of step S54 is: according to the configured collaboration level and the category of the SQL statement, determine whether the SQL statement needs approval. If the SQL statement can be executed directly, execute the SQL statement and display the execution result through the websocket; if the SQL statement cannot be executed, prompts will be given on the collaborator and manager pages; if the SQL statement needs approval, a pending approval box will pop up on the manager page; if the manager's approval result is "agree", execute the SQL statement and display the execution result through the websocket; if the manager's approval result is "reject", do not execute the SQL statement, and prompts will be given on the collaborator and manager pages.

[0034] Working principle: This embodiment is to solve the problem that various database clients in the prior art do not provide real-time collaborative operation and maintenance functions, and the problem that collaborative operation and maintenance functions are provided but the security, real-time performance, flexibility and controllability are not high enough; this embodiment starts from the security, safety, real-time performance, flexibility and controllability of collaborative operation and maintenance, through a collaborative credential mechanism, websocket communication technology, a collaborative level mechanism and an operation and maintenance rights control mechanism, to provide a collaborative operation and maintenance design method based on a database web client to solve the problem of collaborative operation and maintenance of database clients in the prior art.

[0035] This embodiment enters the collaborative session through a collaborative link. This function allows collaborators to enter the collaborative session without a separate account and complete the session validity verification at the same time; by transmitting the executed SQL in real time through websocket, the manager can see all the SQL execution statements and execution results of the collaborators in real time. In the existing work order mechanism, only the SQL statement that triggers the work order can be seen, and the approval result of the work order can be seen, but the execution result of the work order statement cannot be seen; by setting up a collaborative level mechanism, the control flexibility of the statement is made higher; through operation and maintenance authority control and session right control, the controllability of the session is made more flexible.

[0036] Embodiment 2: This embodiment is based on the above embodiment 1. Figure 1 As shown, a specific embodiment is described in detail.

[0037] Step S1: The administrator logs in to the client system and configures the collaboration level.

[0038] Account description for administrators to log in to the client system: Administrators have client system accounts, while collaborators do not have system accounts.

[0039] Step S2: The administrator performs database operation and maintenance; when encountering a situation that requires assistance, the administrator generates a collaborative link and forwards the link to the collaborator through relevant communication methods.

[0040] Description of collaboration level: The collaboration level in step S2 can be divided into the following four types: Level 1 is the first level: all statements are allowed to execute. This level can be set when the manager fully trusts the collaborator. Level 2 is the second level: all query statements are allowed to be executed, and non-query statements require approval. This level is the system default level; Level 3: All query statements are allowed to execute, and non-query statements are automatically rejected; Level 4 is the fourth level: All statements require approval. This level has the highest security, but it will reduce collaboration efficiency. Each operation of the collaborating party needs to be approved before the next step can be executed.

[0041] The steps to generate collaborative links are as follows: a: The administrator clicks the collaboration launch button on the page; b: The system collects the current administrator's session information; c: The system generates a collaborative credential based on the session information in b; d: The system stores the collaboration credentials and session information in the system cache; e: The system generates a collaborative link based on the collaborative credentials and the IP information in the session information.

[0042] Step S3: The collaborator opens the collaborative link in the browser and enters the collaborative session. The manager hands over the operation and maintenance rights to the collaborator.

[0043] After the collaborator opens the collaboration link in the browser, the system will do the following: a: The system extracts the collaboration credentials from the collaboration link. If the extraction fails, access is denied; b: Based on the collaborative credentials, the system searches for relevant session information in the cache. If it is not found, access is denied; c: Based on the session information, the system associates the collaborative session with the manager's operation and maintenance session. The manager can see on his page that the collaborator has entered the collaborative session. d: Delete the collaborative credentials in the system cache to ensure the one-time validity of the system credentials.

[0044] The session control mechanism includes operation and maintenance rights and voice. Operation and maintenance rights mean that only operators with operation and maintenance rights can perform database operation and maintenance operations. Administrators can revoke operation and maintenance rights at any time, and collaborators can also return operation and maintenance rights at any time.

[0045] In step S3, after the collaborator enters the collaborative session, he does not have the operation and maintenance rights and cannot perform operation and maintenance operations. After the manager sees the collaborator enter the collaborative session on his page, he can click a button to give the operation and maintenance rights to the collaborator. At this time, step S4 is entered and the collaborator can start operation and maintenance.

[0046] The client system will maintain the participants of the current session through the cache. The essence of the administrator's allocation or revocation of operation and maintenance rights is to set an operation and maintenance flag for the participants in the cache. Only one person can have this flag at a time. This flag can only be set by the administrator. When a participant has this operation and maintenance flag, he has the operation and maintenance rights.

[0047] During the collaborative operation and maintenance process, if any wrong behavior is found in the collaborator, the administrator can remove the collaborator from the session at any time. The client system will maintain the participants of the current session through cache. The essence of the administrator removing the collaborator from the session is to delete a participant in the system cache, and the remaining ones are those with session rights.

[0048] Step S4: The collaborator starts database operation and maintenance.

[0049] Step S5: The manager can see the SQL statements executed by the collaborator on the page. If approval is required, the manager can approve it. The manager can revoke the operation and maintenance rights at any time, and the collaborator cannot perform any operations after the revoke; the manager can ask the collaborator out at any time, and the collaborative session will be disconnected after the ask is out.

[0050] When collaborators perform maintenance, the system will do the following: 1. Convert various operation and maintenance operations into corresponding SQL statements; 2. Classify SQL statements into query and non-query categories; 3. Use websocket technology to display SQL statements to managers; 4. According to the system level and SQL category, it is processed as follows: a) If SQL can be executed directly, it will be executed and the execution result will be displayed to the administrator through websocket; b) If the SQL statement cannot be executed, a prompt will be automatically displayed on the collaborator and manager page; c) SQL requires approval, and the approval box will automatically pop up on the administrator page; d) If the manager approves the decision and it is "Agree", the SQL statement will be executed and the result will be displayed to the manager through websocket. e) If the manager's approval result is "rejected", the SQL statement cannot be executed, and a prompt will be automatically displayed on the collaborator and manager pages.

[0051] Working principle: This embodiment realizes the real-time display of collaborative operation and maintenance through websocket technology; the security and flexible controllability of collaborative sessions are realized through collaborative credential mechanism, operation and maintenance right control mechanism, and session right control mechanism. The flexibility of SQL statement control is realized through collaborative level mechanism.

[0052] The other parts of this embodiment are the same as those of the above-mentioned embodiment 1, and thus will not be described in detail.

[0053] Embodiment 3: This embodiment is based on any one of the above embodiments 1-2, and is described in detail by taking the collaborative operation and maintenance performed by the manager A and the collaborator B as an example.

[0054] 1) Administrator A logs in to the client system first, using Figure 2 The configuration module in the configuration level is configured as level 2; 2) When manager A encounters a problem during the operation and maintenance process and needs assistance, he clicks a button on the page to generate a collaborative link and sends the link to collaborator B via external communication methods such as WeChat, SMS, etc.; 3) Collaborator B enters the received collaborative link in the browser, and the client system determines the validity of the system link. If it is invalid, the collaborator session is disconnected, otherwise it goes to step 4); 4) Manager A sees on the page that collaborator B has entered the collaborative session and can click the button to Figure 2 The operation and maintenance rights control module in the system transfers the operation and maintenance rights to collaborator B; 5) Collaborator B starts collaborative operation and maintenance; 6) Client system passes Figure 2The session control module checks whether collaborator B has been kicked out of the session. If so, the collaborative session ends; otherwise, it goes to step 7); 7) Client system passes Figure 2 The operation and maintenance rights control module in the process checks whether collaborator B has the operation and maintenance rights. If not, it will prompt an authority error. The collaborator can do nothing or go to step 5 again. Otherwise, it will go to step 8); 8) Collaborator B generates a query statement sql1 and an update statement sql2 during operation and maintenance. The client system determines that query statements can be executed directly, but update statements require approval based on the collaboration level configured by manager A. Therefore, after executing sql1, the client system sends the content and execution result of sql1 to the client. Figure 2 The websocket diagram in the figure is sent to the administrator's browser, and then the content of sql2 and a pending approval mark are sent through Figure 2 The websocket diagram in the figure is sent to the manager's browser. The browser receives sql2 and a pending approval sign, and a pop-up window prompts the manager to approve it. If the approval result is rejected, the client system will send a message to the collaborator's browser that sql2 has been rejected. If the approval result is allowed, sql2 will be executed normally. Then collaborator B can do nothing or go to step 5 again); 9) If manager A needs to perform maintenance, he can take back the maintenance rights, which will result in collaborator B not having maintenance rights in step 7). If manager A encounters problems during the maintenance process, he can give the maintenance rights to collaborator B; 10) Manager A no longer needs to collaborate and can ask collaborator B to leave the session. At this time, collaborator B will not have the session rights in step 6).

[0055] The other parts of this embodiment are the same as any one of the above-mentioned embodiments 1-2, so they will not be repeated here.

[0056] Embodiment 4: This embodiment is based on any one of the above embodiments 1 to 3. Figure 2 As shown, a collaborative operation and maintenance system based on a database web client is proposed, which is used to execute the above-mentioned collaborative operation and maintenance method based on a database web client; it includes a configuration module, a collaborative credential management module, a session right control module, an operation and maintenance right control module, and a statement control module; The configuration module is used to log in to the database web client and configure the collaboration level; The collaborative credential management module is used to generate a collaborative link according to the acquired session information, and send the collaborative link to the collaborator through an external communication method; The session right control module is used to input the collaborative link into the browser, and determine whether the collaborative link is valid on the database web client. If it is valid, step S4 is executed; if it is invalid, the collaborative session is disconnected; The operation and maintenance rights control module is used to enter the collaborative session according to the collaborative link to perform collaborative operation and maintenance, and determine whether the collaborator has the operation and maintenance rights. If the collaborator does not have the operation and maintenance rights, it prompts that the authority is wrong, otherwise it executes step S5; The statement control module is used to generate SQL statements when executing collaborative operation and maintenance, and determine whether the SQL statements need approval based on the configured collaboration level. If the approval is passed, the collaborative operation and maintenance operation is executed. If the approval fails, the approval rejection is prompted.

[0057] This embodiment also proposes an electronic device, including a memory and a processor; a computer program is stored on the memory; when the computer program is executed on the processor, the above-mentioned collaborative operation and maintenance method based on the database web client is implemented.

[0058] This embodiment further proposes a computer-readable storage medium, on which computer instructions are stored; when the computer instructions are executed on the above-mentioned electronic device, the above-mentioned collaborative operation and maintenance method based on the database web client is implemented.

[0059] The other parts of this embodiment are the same as any one of the above-mentioned embodiments 1 to 3, so they will not be repeated here.

[0060] The above description is only a preferred embodiment of the present invention and does not limit the present invention in any form. Any simple modification or equivalent change made to the above embodiment based on the technical essence of the present invention shall fall within the protection scope of the present invention.

Claims

1. A collaborative operation and maintenance method based on a database web client, characterized in that: The specific steps include: Step S1: Log in to the database web client and configure the collaboration level; Step S2: generating a collaborative link according to the acquired session information, and sending the collaborative link to the collaborator through an external communication method; Step S3: input the collaborative link into the browser, and determine whether the collaborative link is valid on the database web client. If it is valid, execute step S4; if it is invalid, disconnect the collaborative session; Step S4: Enter the collaborative session according to the collaborative link to perform collaborative operation and maintenance, and determine whether the collaborator has the operation and maintenance rights. If the collaborator does not have the operation and maintenance rights, a permission error is prompted, otherwise, step S5 is executed; Step S5: When executing collaborative operation and maintenance, a SQL statement is generated, and whether the SQL statement needs approval is determined based on the configured collaboration level. If the approval is passed, the collaborative operation and maintenance operation is executed. If the approval fails, an approval rejection prompt is displayed.

2. According to claim 1, a collaborative operation and maintenance method based on a database web client is characterized in that: The step S2 specifically includes the following steps: Step S21: Obtaining session information from the database web client; Step S22: Generate a collaboration credential based on the session information; Step S23: Generate a collaborative link based on the collaborative credentials and the IP information of the session information, and send the collaborative link to the collaborator through an external communication method.

3. A collaborative operation and maintenance method based on a database web client according to claim 2, characterized in that: The step S3 specifically comprises the following steps: Step S31: input the collaborative link into the browser, extract the collaborative credentials from the collaborative link, and deny access if the extraction fails; Step S32: searching the cache for session information related to the collaborative credentials according to the extracted collaborative credentials, and denying access if the session information is not found; Step S33: Associating the collaborative session with the operation and maintenance session according to the session information, and deleting the collaborative credentials in the cache; Step S34: determine whether the collaborative link is valid, if it is valid, execute step S4, if it is invalid, disconnect the collaborative session.

4. A collaborative operation and maintenance method based on a database web client according to claim 1, characterized in that: The collaboration level in step S1 includes the first level, the second level, the third level, and the fourth level; The first level allows all statements to execute: The second level is used to allow all query statements to be executed, and non-query statements to be executed after approval; The third level is used to allow all query statements to be executed, and non-query statements are automatically rejected; The fourth level is used to approve all statements. Each operation of the collaborator needs to be approved before the next step can be executed.

5. A collaborative operation and maintenance method based on a database web client according to claim 4, characterized in that: The step S5 specifically comprises the following steps: Step S51: when performing collaborative operation and maintenance, convert the operation and maintenance operation into a corresponding SQL statement; Step S52: classify the SQL statements into query and non-query categories; Step S53: calling the websocket technology to display the classified SQL statements; Step S54: According to the configured collaboration level and the category of the SQL statement, determine whether the SQL statement needs approval. If the approval is passed, perform collaborative operation and maintenance operations. If the approval fails, prompt approval rejection.

6. A collaborative operation and maintenance method based on a database web client according to claim 5, characterized in that: The specific operation of step S54 is: according to the configured collaboration level and the category of the SQL statement, determine whether the SQL statement needs approval; if the SQL statement can be directly executed, execute the SQL statement and display the execution result through the websocket; If the SQL statement cannot be executed, a prompt will be displayed on the collaborator and manager page; If the SQL statement requires approval, a pending approval box will pop up on the administrator page; if the administrator's approval result is "agree", the SQL statement will be executed and the execution result will be displayed through websocket; if the administrator's approval result is "reject", the SQL statement will not be executed, and a prompt will be given on the collaborator and administrator pages.

7. A collaborative operation and maintenance system based on a database web client, used to execute the collaborative operation and maintenance method based on a database web client according to claim 1; characterized in that: It includes configuration module, collaborative credential management module, session right control module, operation and maintenance right control module, and statement control module; The configuration module is used to log in to the database web client and configure the collaboration level; The collaborative credential management module is used to generate a collaborative link according to the acquired session information, and send the collaborative link to the collaborator through an external communication method; The session right control module is used to input the collaborative link into the browser, and determine whether the collaborative link is valid on the database web client. If it is valid, step S4 is executed; if it is invalid, the collaborative session is disconnected; The operation and maintenance rights control module is used to enter the collaborative session according to the collaborative link to perform collaborative operation and maintenance, and determine whether the collaborator has the operation and maintenance rights. If the collaborator does not have the operation and maintenance rights, it prompts that the authority is wrong, otherwise it executes step S5; The statement control module is used to generate SQL statements when executing collaborative operation and maintenance, and determine whether the SQL statements need approval based on the configured collaboration level. If the approval is passed, the collaborative operation and maintenance operation is executed. If the approval fails, the approval rejection is prompted.

8. An electronic device, characterized in that: It comprises a memory and a processor; a computer program is stored in the memory; when the computer program is executed on the processor, the collaborative operation and maintenance method based on the database web client as described in any one of claims 1 to 7 is implemented.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions; when the computer instructions are executed on the electronic device as described in claim 8, the collaborative operation and maintenance method based on the database web client as described in any one of claims 1-7 is implemented.

Images