WO2020015151A1

WO2020015151A1 - Parameter insertion method and apparatus for database table, terminal device, and storage medium

Info

Publication number: WO2020015151A1
Application number: PCT/CN2018/106265
Authority: WO
Inventors: 高梁梁; 王游江
Original assignee: 平安科技（深圳）有限公司
Priority date: 2018-07-18
Filing date: 2018-09-18
Publication date: 2020-01-23
Also published as: CN109063044B; CN109063044A

Abstract

A parameter insertion method and apparatus for a database table, a terminal device, and a storage medium. The method comprises: receiving an insertion instruction, and encapsulating a parameter to be inserted into a user-defined object (S10); receiving a universal Package call instruction, and calling an insertion method in the universal Package to transmit the user-defined object into the insertion method (S20); and based on the insertion method, storing the parameter to be inserted that is encapsulated in the user-defined object to a corresponding insertion position of a database table (S30). By means of the method, a Package is used as the universal Package, the insertion method is pre-written into the universal Package, and when data needs to be stored into the database table, it is only needed to call the pre-written insertion method in the universal Package, and the parameter to inserted that is encapsulated in the user-defined object can be stored into the database table. By means of the method, the present invention achieves the design principle of high cohesion and low coupling in software design, and enables the codes to be concise and readable in the process of storage, improves development efficiency, and reduces the maintenance costs.

Description

Parameter insertion method, device, terminal device and storage medium of database table

This application is based on a Chinese invention patent application filed on July 18, 2018 with the application number 201810788208.2, entitled "Parameter Insertion Method, Device, Terminal Equipment and Storage Medium of Database Table", and claims its priority.

Technical field

The present application relates to the field of data processing, and in particular, to a method, a device, a terminal device, and a storage medium for inserting parameters of a database table.

Background technique

At present, when the parameters need to be stored in the database table, if the same interface is used for storage, a large number of duplicate codes will be generated during the storage process; for example, when multiple parameters are inserted into the database table, multiple parameters need to be transmitted; at the same time Each time the storage process requires a write insert method, multiple storage requires multiple write insert methods and cannot be reused; and, the same parameter may need to be inserted multiple times, at which time the transmission and write insert methods need to be repeated. The stored procedure is very cumbersome and violates the design principles of high cohesion and low coupling in software design.

Summary of the invention

The embodiments of the present application provide a method, a device, a terminal device, and a storage medium for inserting parameters of a database table, which can implement design principles of high cohesion and low coupling in software design, make the code in the storage process simple and readable, and improve development efficiency. Reduce maintenance costs.

In a first aspect, the case of this application provides a method for inserting a parameter into a database table, including:

Receive an insert instruction, and encapsulate the parameter to be inserted into the custom object;

Receiving a general package call instruction, calling the insert method in the universal package to pass the custom object into the insert method;

Based on the insertion method, the parameter to be inserted encapsulated in the custom object is stored to a corresponding insertion position in a database table.

In a second aspect, an example of the present application provides a parameter insertion device for a database table, including:

A packaging module for receiving an insertion instruction and packaging a parameter to be inserted into the custom object;

A calling module, configured to receive a general package calling instruction, call an insert method in the general package, and pass the custom object into the insert method;

An inserting module is configured to store, based on the inserting method, a parameter to be inserted encapsulated in the custom object to a corresponding inserting position in a database table.

According to a third aspect, an example of the present application provides a terminal device including a memory, a processor, and computer-readable instructions stored in the memory and executable on the processor, and the processor executes the computer-readable Implement the following steps when instructing:

According to a fourth aspect, an example of the present application provides one or more non-volatile readable storage media storing computer-readable instructions. When the computer-readable instructions are executed by one or more processors, the one Or multiple processors perform the following steps:

Details of one or more embodiments of the present application are set forth in the accompanying drawings and description below, and other features and advantages of the present application will become apparent from the description, the drawings, and the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to explain the technical solution of the embodiments of the present application more clearly, the drawings used in the description of the embodiments of the application will be briefly introduced below. Obviously, the drawings in the following description are just some embodiments of the application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without paying creative labor.

FIG. 1 is a schematic diagram of an application environment of a parameter insertion method of a database table according to an embodiment of the present application; FIG.

2 is a flowchart of a method for inserting parameters of a database table in an embodiment of the present application;

3 is a flowchart of step S10 of a parameter insertion method of a database table in an embodiment of the present application;

4 is a flowchart of step S10 of a parameter insertion method of a database table in another embodiment of the present application;

5 is a flowchart of a method for inserting a parameter of a database table in another embodiment of the present application;

6 is a flowchart of a method for inserting a parameter of a database table in another embodiment of the present application;

7 is a flowchart of step S30 of a parameter insertion method of a database table in another embodiment of the present application;

8 is a block diagram of a parameter insertion device for a database table in an embodiment of the present application;

9 is a block diagram of a packaging module of a parameter insertion device of a database table in an embodiment of the present application;

10 is a block diagram of a packaging module of a parameter insertion device of a database table in another embodiment of the present application;

FIG. 11 is a schematic diagram of a terminal device in an embodiment of the present application.

detailed description

In the following, the technical solutions in the embodiments of the present application will be clearly and completely described with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, but not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by a person of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

The parameter insertion method of the database table provided in this application can be applied in the application environment as shown in FIG. 1, in which a client (terminal device) communicates with a server through a network. The clients include, but are not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices. The server can be implemented by an independent server or a server cluster composed of multiple servers.

In an embodiment, as shown in FIG. 2, a method for inserting parameters of a database table is provided. The method is applied to the server in FIG. 1 as an example, and includes the following steps:

S10. Receive an insert instruction, and encapsulate a parameter to be inserted into the custom object.

Specifically, encapsulating the parameter to be inserted into the custom object refers to mapping all fields of the parameter to be inserted into the custom object according to a custom method. That is, all fields of the parameter to be inserted are mapped into a custom object, so that the parameter to be inserted corresponds to a corresponding insertion position in the database table, and in this embodiment, a custom object corresponds to A database table. Understandably, the custom method can be set according to requirements. In one embodiment, a custom method Type [Custom Object Name] is record (a custom method type) is used to map all fields of the parameter to be inserted to In a custom object. Since a custom object corresponds to a database table, the custom object stores the table name of the database table in the database table corresponding to it, and the mapping relationship defined in the custom method is as follows: The variable in the custom object is mapped to a table field at a position (a corresponding insertion position in the database table) corresponding to both a table name and a field name in a database table. That is, the above-mentioned mapping of all fields of the parameter to be inserted into the custom object using the custom method refers to: using the fields in the parameter to be inserted as variables in the custom object, and in the custom method An association relationship is established between the variable and the insertion position in the database table. S20. Receive a general package (a concept of a package provided in the Java program development) call instruction, and call the insert method in the general package to pass the custom object into the insert method.

Understandably, the insert method is written when the universal package is created, and is used to store the parameters to be inserted encapsulated in the custom object into a database table; the insert method is used to define the following stored procedure: The custom object is passed into the insert method, and in the process, the variables written in the custom object correspond to the insertion position in the database table (the table name and field name in the database table both correspond The corresponding relationship between the positions), and finally the variables in the custom object are stored as the values of the table fields of the corresponding insertion positions in the database.

That is, after the current to-be-inserted parameter is encapsulated into a custom object (or it is confirmed that the current to-be-inserted parameter is encapsulated in the custom object), the server receives a general package call instruction, and the general package call instruction is provided by a service The package is issued, and the business package calls the insert method in the universal package, and finally achieves the purpose of storing the parameters to be inserted encapsulated in the custom object to the corresponding location in the database table. After the custom object is passed into the insert method, the server can obtain the parameters to be inserted encapsulated in the custom object through the insert method.

In this embodiment, multiple universal service execution methods can be written in a universal package, such as the insert method, the log recording method, and the deduplication log method (to ensure the uniqueness of the log). The business package writes business logic (such as calling the general package's business logic). When different services are executed, the corresponding services in the general package can be called through different service packages (different from the general package). Execution method executes instructions.

S30. Based on the insertion method, the parameters to be inserted encapsulated in the custom object are stored to the corresponding insertion positions in the database table.

Understandably, after the parameter to be inserted is encapsulated into a custom object, the parameter to be inserted has been inserted into the custom object and stored in the custom object. In the subsequent process, if the When the parameters encapsulated in the custom object are stored in the database table, there is no need to repeatedly insert the parameters into the custom object, but directly call the insert method in the universal package to pass in the custom object. Just fine. If there are multiple parameters inserted at a time, only the parameters that are not encapsulated in the custom object need to be inserted into the custom object, and the parameters that have been previously encapsulated in the custom object do not need to be inserted again In this way, for the parameters that need to be repeatedly inserted, you can directly pass only the custom object that has encapsulated the parameters, without repeated insertion and transmission. The program is concise, improves development efficiency, and reduces maintenance costs.

The parameter insertion method of the database table in the above embodiment uses a Package as a general package, and the insert method is written into the general package in advance. When data needs to be stored in the database table, all the parameters to be inserted need only be customized The field is encapsulated into a custom object, and then the pre-written insert method in the universal package is called to complete the action of storing the parameters to be inserted encapsulated in the custom object to the corresponding insert position in the database table. This application realizes the design principles of high cohesion and low coupling in software design, and makes the code in the stored process concise and readable, which improves development efficiency and reduces maintenance costs.

In an embodiment, as shown in FIG. 3, the step S10, that is, receiving an insert instruction, and packaging the parameters to be inserted into the custom object includes the following steps:

S101. Receive an insertion instruction, and detect whether a parameter to be inserted included in the insertion instruction meets an insertion condition of a corresponding insertion position in a database table.

In this step, the server first receives an insert instruction, that is, a certain parameter to be inserted needs to be first inserted into the custom object for encapsulation, because when the custom object is encapsulated, the to-be-inserted parameter needs to be inserted at the same time. The parameter corresponds to the position where it needs to be inserted. Therefore, it is first necessary to detect whether the parameter to be inserted included in the insert instruction meets the insertion condition of the corresponding insertion position in the database table.

In an embodiment, the database is an Oracle database; the insertion condition is set according to specific requirements in a database table. For example, when the insertion condition includes a parameter type, it is necessary to detect whether the parameter type of the parameter to be inserted is Whether the parameter type matches the corresponding insertion position in the database table. When the two do not match, the current parameter to be inserted is not encapsulated into a custom object.

S102. When the insertion condition of the corresponding insertion position in the database table is not met, an abnormal prompt is issued. That is, when the parameter to be inserted does not meet the insertion conditions of the corresponding insertion position in the database table, an abnormal prompt needs to be issued to prompt the user to modify or other subsequent operations; for example, the parameter type and database of the parameter to be inserted are prompted When the parameter type corresponding to the insertion position in the table does not match, the user needs to modify the parameter type or replace the parameter to be inserted.

S103. When the insertion conditions of the corresponding insertion position in the database table are met, all fields of the parameter to be inserted are mapped into the custom object according to a custom method, and are associated with the corresponding insertion position in the database table. That is, when the parameter to be inserted meets the insertion condition of the corresponding insertion position in the database table, the parameter to be inserted is encapsulated into a custom object, and it corresponds to a corresponding position in the database table.

In an embodiment, as shown in FIG. 4, before step S101, that is, receiving an insert instruction, and detecting whether a parameter to be inserted included in the insert instruction meets an insert condition of a corresponding insert position in a database table, the following steps are included: :

S104. Detect whether the current parameter to be inserted is encapsulated in the custom object. In this step, it is determined whether the current parameter to be inserted is encapsulated in the custom object to determine whether it is necessary to continue inserting it into the custom object. In a custom object.

S105. When the current parameter to be inserted is encapsulated in the custom object, send a general Package call instruction; that is, when the current parameter to be inserted is encapsulated in the custom object, it is not necessary to insert it into the custom object again. In the custom object, it is only necessary to send a general package call instruction, and directly call the insert method in the general package to pass in the custom object. At this time, it proceeds to the above step S20, that is, the server receives the general package call instruction, and calls the insert method in the general package to pass the custom object into the insert method.

S106. When the current parameter to be inserted is not encapsulated in the custom object, an insert instruction is sent. That is, when it is confirmed that the current parameter to be inserted is not encapsulated in the custom object, the current parameter to be inserted needs to be inserted into the custom object. At this time, turning to step S101, the server receives the insertion instruction, and detects whether the parameter to be inserted included in the insertion instruction meets the insertion condition of the corresponding insertion position in the database table.

In an embodiment, as shown in FIG. 5, before step S10, that is, before receiving an inserting instruction and packaging the parameters to be inserted into the custom object, the method includes the following steps:

S40. Receive a custom object creation instruction to create a custom object. That is, in this embodiment, before step S10 is performed, it is preferred to create a custom object to encapsulate the parameters to be inserted.

In an embodiment, as shown in FIG. 6, before step S20, that is, before receiving a general package call instruction, before calling the insert method in the general package to pass the custom object into the insert method, The following steps are also included:

S50. Write the insertion method in a universal package in advance. In this embodiment, the insertion method is written when the universal package is created, and is used to store a parameter to be inserted encapsulated in a custom object into a database table. Understandably, in this application, multiple universal service execution methods (such as the insert method) can be written into a universal package. The universal service execution methods also include a log recording method and a deduplication log method (guaranteed Uniqueness of logs) and so on. When executing different services, corresponding service execution methods in the general package can be called to execute instructions through different service packages.

In an embodiment, as shown in FIG. 7, the step S30, that is, based on the insertion method, stores the parameters to be inserted encapsulated in the custom object to a corresponding insertion position in a database table, including the following steps: :

S301. Interpret the custom object by the insert method, and obtain parameter information of a parameter to be inserted encapsulated in the custom object, where the parameter information includes a value of the parameter to be inserted and a parameter to be inserted in the database table. The corresponding insertion position; understandably, the parameter information can be set according to requirements, and is not limited to that described in this embodiment; the insertion method can interpret and obtain the parameters of the to-be-inserted parameters encapsulated in the custom object Parameter information.

S302. Generate a storage instruction for storing the parameter to be inserted into a corresponding insertion position in the database table according to the parameter information; that is, after obtaining the parameter information through the insertion method, a A storage instruction for storing the parameter to be inserted into a corresponding insertion position in the database table.

S303. Store the parameter to be inserted into a corresponding insertion position in the database table according to the storage instruction.

It should be understood that the size of the sequence numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

In an embodiment, as shown in FIG. 8, a parameter insertion device for a database table is provided, and the parameter insertion device for the database table corresponds to the parameter insertion method for the database table in the above-mentioned embodiment. The device includes:

The encapsulation module 110 is configured to receive an insertion instruction and encapsulate a parameter to be inserted into the custom object;

An invoking module 120, configured to receive a general package call instruction, call an insert method in the general package, and pass the custom object into the insert method;

The inserting module 130 is configured to store, based on the inserting method, a parameter to be inserted encapsulated in the custom object to a corresponding inserting position in a database table.

The parameter insertion device of the database table in the above embodiment uses a Package as a general package, and writes the insert method into the general package in advance. When data needs to be stored in the database table, as long as a custom method is used, all The field is encapsulated into a custom object, and then the pre-written insert method in the universal package is called to complete the action of storing the parameters to be inserted encapsulated in the custom object to the corresponding insert position in the database table. This application realizes the design principles of high cohesion and low coupling in software design, and makes the code in the stored process concise and readable, which improves development efficiency and reduces maintenance costs.

In an embodiment, as shown in FIG. 9, the packaging module 110 includes:

A first detection sub-module 111, configured to receive an insertion instruction and detect whether a parameter to be inserted included in the insertion instruction meets an insertion condition of a corresponding insertion position in a database table;

Prompt submodule 112, which is used to issue an abnormal prompt when the insert condition of the corresponding insert position in the database table is not met;

A mapping sub-module 113, configured to map all fields of the parameter to be inserted into a custom object according to a custom method when the insertion conditions of the corresponding insertion position in the database table are met, and associate them with the corresponding insertion position in the database table .

In an embodiment, as shown in FIG. 10, the packaging module 110 further includes:

A second detection sub-module 114, configured to detect whether a parameter to be inserted is currently encapsulated in the custom object;

A first instruction sending sub-module 115 is configured to send a general package calling instruction when a parameter to be inserted is currently encapsulated in the custom object; the first instruction sending sub-module 115 is communicatively connected to the calling module 120;

The second instruction sending submodule 116 is configured to send an insertion instruction when a parameter to be inserted is not encapsulated in the custom object. The second instruction sending sub-module 116 is communicatively connected to the first detecting sub-module 111.

In an embodiment, the device is further configured to receive a custom object creation instruction and create a custom object before receiving an insert instruction and encapsulating a parameter to be inserted into the custom object; and also used to receive a universal package The calling instruction calls the insert method in the universal package before the custom object is passed into the insert method, and the insert method is written in the universal package in advance.

In an embodiment, the inserting module is further configured to interpret the custom object through the inserting method, and obtain parameter information of a parameter to be inserted encapsulated in the custom object, where the parameter information includes a parameter to be inserted. A corresponding insertion position of the value and the parameter to be inserted in the database table; and a storage instruction for storing the parameter to be inserted into the corresponding insertion position in the database table according to the parameter information; according to the storage instruction, Storing the parameter to be inserted into a corresponding insertion position in the database table.

For the specific limitation of the parameter insertion device of the database table, refer to the foregoing limitation on the method of parameter insertion of the database table, which will not be repeated here. Each module in the parameter insertion device of the database table may be implemented in whole or in part by software, hardware, and a combination thereof. Each of the above modules may be embedded in the processor in the form of hardware or independent of the processor in the terminal device, or may be stored in the memory of the terminal device in the form of software to facilitate the processor to call and execute the operations corresponding to the above modules.

In one embodiment, a terminal device is provided. The terminal device may be a server, and its internal structure diagram may be as shown in FIG. 11. The terminal device includes a processor, a memory, a network interface, and a database connected through a system bus. The processor of the terminal device is used to provide computing and control capabilities. The memory of the terminal device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer-readable instructions, and a database. The internal memory provides an environment for operating the operating system and computer-readable instructions in a non-volatile storage medium. The network interface of the terminal device is used to communicate with external terminals through a network connection. The computer-readable instructions are executed by a processor to implement a method for inserting parameters into a database table.

In one embodiment, a terminal device (ie, a computer device) is provided, which includes a memory, a processor, and computer-readable instructions stored on the memory and executable on the processor, and the processor executes the computer-readable instructions. To achieve the following steps:

Receiving an insert instruction, and packaging a parameter to be inserted into the custom object; receiving a general package call instruction, calling an insert method in the general package to pass the custom object into the insert method; based on the insert Method: Store the parameter to be inserted encapsulated in the custom object to a corresponding insertion position in a database table.

The terminal device of the above embodiment uses a Package as a universal package, and writes an insert method into the universal package in advance. When data needs to be stored in a database table, as long as a custom method is used to encapsulate all fields of the parameters to be inserted into the package In the defined object, the pre-written insert method in the universal package is called, and then the action of storing the parameters to be inserted encapsulated in the custom object to the corresponding insert position in the database table can be completed. This application realizes the design principles of high cohesion and low coupling in software design, and makes the code in the stored process concise and readable, which improves development efficiency and reduces maintenance costs.

In one embodiment, one or more non-volatile readable storage media storing computer readable instructions are provided, and the non readable storage medium stores computer readable instructions, the computer readable instructions When executed by one or more processors, causes the one or more processors to perform the following steps:

The computer-readable storage medium of the above embodiment uses a package as a universal package, and writes an insert method into the universal package in advance. When data needs to be stored in a database table, as long as all fields of the parameters to be inserted are used by a custom method The package is encapsulated into a custom object, and then the insert method written in the general package is called to complete the action of storing the parameters to be inserted encapsulated in the custom object to the corresponding insert position in the database table. This application realizes the design principles of high cohesion and low coupling in software design, and makes the code in the stored process concise and readable, which improves development efficiency and reduces maintenance costs.

Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be implemented by computer-readable instructions to instruct related hardware. The computer-readable instructions can be stored in a non-volatile computer. In the readable storage medium, the computer-readable instructions, when executed, may include the processes of the embodiments of the methods described above. Wherein, any reference to the memory, storage, database or other media used in the embodiments provided in this application may include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous chain Synchlink DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

Those skilled in the art can clearly understand that, for the convenience and brevity of the description, only the above-mentioned division of functional units and modules is used as an example. In practical applications, the above functions can be allocated by different functional units according to needs. Module completion, that is, dividing the internal structure of the device into different functional units or modules to complete all or part of the functions described above.

The above-mentioned embodiments only describe the technical solutions of the present application, rather than limiting the present invention. Although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still apply the foregoing embodiments. The recorded technical solutions are modified, or some of the technical features are equivalently replaced; and these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the application, and should be included in the application. Within the scope of protection.

Claims

A method for inserting parameters into a database table, which includes:

Receive an insert instruction, and encapsulate the parameter to be inserted into the custom object;

Receiving a general package call instruction, calling the insert method in the universal package to pass the custom object into the insert method;

Based on the insertion method, the parameter to be inserted encapsulated in the custom object is stored to a corresponding insertion position in a database table.
The method for parameter insertion of a database table according to claim 1, wherein the receiving an insert instruction and encapsulating the parameter to be inserted into the custom object comprises:

Receiving an insert instruction, and detecting whether the parameter to be inserted contained in the insert instruction meets an insert condition of a corresponding insert position in a database table;

When the insert condition of the corresponding insert position in the database table is not met, an exception prompt is issued;

When the insertion conditions of the corresponding insertion position in the database table are met, all fields of the parameter to be inserted are mapped into the custom object according to a custom method, and are associated with the corresponding insertion position in the database table.
The method for parameter insertion of a database table according to claim 2, wherein before receiving the insert instruction, detecting whether the parameter to be inserted contained in the insert instruction meets an insert condition of a corresponding insert position in the database table, comprises:

Detecting whether the current parameter to be inserted is encapsulated in the custom object;

Sending a general Package call instruction when the currently to-be-inserted parameters have been encapsulated in the custom object;

When the current parameter to be inserted is not encapsulated in the custom object, an insert instruction is sent.
The method for parameter insertion of a database table according to claim 1, wherein before the receiving an insert instruction and encapsulating a parameter to be inserted into the custom object, comprises:

Receive custom object creation instructions to create custom objects;

Before the receiving a general package calling instruction, calling the insert method in the universal package, and before passing the custom object into the insert method, the method further includes:

The insertion method is written in a universal package in advance.
The method for inserting a parameter of a database table according to claim 1, wherein, based on the method for inserting, storing the parameter to be inserted encapsulated in the custom object to a corresponding insertion position in the database table, include:

Interpret the custom object by the insert method, and obtain parameter information of the parameter to be inserted encapsulated in the custom object, where the parameter information includes a value of the parameter to be inserted and a corresponding parameter in the database table. Insertion position

Generating a storage instruction for storing the parameter to be inserted into a corresponding insertion position in the database table according to the parameter information;

Storing the parameter to be inserted into a corresponding insertion position in the database table according to the storage instruction.
A parameter insertion device for a database table, comprising:

A packaging module for receiving an insertion instruction and packaging a parameter to be inserted into the custom object;

A calling module, configured to receive a general package calling instruction, call an insert method in the general package, and pass the custom object into the insert method;

An inserting module is configured to store, based on the inserting method, a parameter to be inserted encapsulated in the custom object to a corresponding inserting position in a database table.
The parameter insertion device for a database table according to claim 6, wherein the encapsulation module comprises:

A first detection submodule, configured to receive an insertion instruction and detect whether a parameter to be inserted included in the insertion instruction meets an insertion condition of a corresponding insertion position in a database table;

Prompt submodule, which is used to issue an exception prompt when the insert condition of the corresponding insert position in the database table is not met;

A mapping sub-module is used to map all fields of the parameter to be inserted into a custom object according to a custom method when the insert condition of the corresponding insert position in the database table is met, and associate it with the corresponding insert position in the database table.
The parameter insertion device for a database table according to claim 7, wherein the encapsulation module further comprises:

A second detection submodule, configured to detect whether a parameter to be inserted is currently encapsulated in the custom object;

A first instruction sending submodule, configured to send a general package call instruction when a parameter to be inserted is currently encapsulated in the custom object;

The second instruction sending submodule is configured to send an insertion instruction when a parameter to be inserted is not encapsulated in the custom object.
The parameter insertion device for a database table according to claim 6, wherein the device is further configured to receive a custom object creation instruction before receiving an insert instruction and encapsulate the parameter to be inserted into the custom object, and create A custom object; it is also used to write the insert method in the universal package before receiving the universal package call instruction and calling the insert method in the universal package to pass the custom object into the insert method.
The method for inserting a parameter of a database table according to claim 6, wherein the inserting module is further configured to interpret the custom object through the inserting method, and obtain a parameter to be inserted encapsulated in the custom object. Parameter information, the parameter information including the value of the parameter to be inserted and the corresponding insertion position of the parameter to be inserted in the database table; according to the parameter information, generating the corresponding parameter to be stored in the database table A storage instruction for an insertion position; and storing the parameter to be inserted into a corresponding insertion position in the database table according to the storage instruction.
A terminal device includes a memory, a processor, and computer-readable instructions stored in the memory and executable on the processor, and is characterized in that the processor implements the computer-readable instructions as follows: step:

Receive an insert instruction, and encapsulate the parameter to be inserted into the custom object;

Receiving a general package call instruction, calling the insert method in the universal package to pass the custom object into the insert method;

Based on the insertion method, the parameter to be inserted encapsulated in the custom object is stored to a corresponding insertion position in a database table.
The terminal device according to claim 11, wherein the receiving an insert instruction and encapsulating a parameter to be inserted into the custom object comprises:

Receiving an insert instruction, and detecting whether the parameter to be inserted contained in the insert instruction meets an insert condition of a corresponding insert position in a database table;

When the insert condition of the corresponding insert position in the database table is not met, an exception prompt is issued;

When the insertion conditions of the corresponding insertion position in the database table are met, all fields of the parameter to be inserted are mapped into the custom object according to a custom method, and are associated with the corresponding insertion position in the database table.
The terminal device according to claim 12, wherein before receiving the insertion instruction and detecting whether the parameter to be inserted included in the insertion instruction meets an insertion condition of a corresponding insertion position in a database table, comprises:

Detecting whether the current parameter to be inserted is encapsulated in the custom object;

Sending a general Package call instruction when the currently to-be-inserted parameters have been encapsulated in the custom object;

When the current parameter to be inserted is not encapsulated in the custom object, an insert instruction is sent.
The terminal device according to claim 11, wherein when the processor executes the computer-readable instructions, the following steps are implemented:

Receive custom object creation instructions to create custom objects;

The insertion method is written in a universal package in advance.
The terminal device according to claim 11, wherein the storing the parameters to be inserted encapsulated in the custom object to a corresponding insertion position in a database table based on the insertion method comprises:

Interpret the custom object by the insert method, and obtain parameter information of the parameter to be inserted encapsulated in the custom object, where the parameter information includes a value of the parameter to be inserted and a corresponding parameter in the database table. Insertion position

Generating a storage instruction for storing the parameter to be inserted into a corresponding insertion position in the database table according to the parameter information;

Storing the parameter to be inserted into a corresponding insertion position in the database table according to the storage instruction.
One or more non-volatile readable storage media storing computer-readable instructions, wherein when the computer-readable instructions are executed by one or more processors, the one or more processors execute The following steps:

Receive an insert instruction, and encapsulate the parameter to be inserted into the custom object;

Receiving a general package call instruction, calling the insert method in the universal package to pass the custom object into the insert method;

Based on the insertion method, the parameter to be inserted encapsulated in the custom object is stored to a corresponding insertion position in a database table.
The non-volatile readable storage medium of claim 16, wherein packaging the parameters to be inserted into the custom object comprises:

Receiving an insert instruction, and detecting whether the parameter to be inserted contained in the insert instruction meets an insert condition of a corresponding insert position in a database table;

When the insert condition of the corresponding insert position in the database table is not met, an exception prompt is issued;

When the insertion conditions of the corresponding insertion position in the database table are met, all fields of the parameter to be inserted are mapped into the custom object according to a custom method, and are associated with the corresponding insertion position in the database table.
The non-volatile readable storage medium according to claim 17, wherein before receiving the insert instruction, detecting whether a parameter to be inserted contained in the insert instruction meets an insert condition of a corresponding insert position in a database table, include:

Detecting whether the current parameter to be inserted is encapsulated in the custom object;

Sending a general Package call instruction when the currently to-be-inserted parameters have been encapsulated in the custom object;

When the current parameter to be inserted is not encapsulated in the custom object, an insert instruction is sent.
The non-volatile readable storage medium of claim 16, wherein when the computer-readable instructions are executed by one or more processors, the one or more processors further perform the following steps:

Receive custom object creation instructions to create custom objects;

The insertion method is written in a universal package in advance.
The non-volatile readable storage medium according to claim 16, wherein, based on the inserting method, the storing the parameters to be inserted encapsulated in the custom object to a corresponding insert in a database table Location, including:

Interpret the custom object by the insert method, and obtain parameter information of the parameter to be inserted encapsulated in the custom object, where the parameter information includes a value of the parameter to be inserted and a corresponding parameter in the database table. Insertion position

Generating a storage instruction for storing the parameter to be inserted into a corresponding insertion position in the database table according to the parameter information;

Storing the parameter to be inserted into a corresponding insertion position in the database table according to the storage instruction.