CN111459933B

CN111459933B - GDB data dynamic expansion method, device and storage medium

Info

Publication number: CN111459933B
Application number: CN202010170076.4A
Authority: CN
Inventors: 陈筱倜; 冯心; 陈子超; 张振伟; 林军
Original assignee: Ping An Technology Shenzhen Co Ltd
Current assignee: Ping An Technology Shenzhen Co Ltd
Priority date: 2020-03-12
Filing date: 2020-03-12
Publication date: 2023-06-06
Anticipated expiration: 2040-03-12
Also published as: WO2021179636A1; CN111459933A

Abstract

The invention relates to the technical field of big data platforms, and provides a GDB data dynamic expansion method, a device and a storage medium, wherein the method comprises the following steps: establishing a report system database corresponding to a GDB database through selecting a development mode, wherein the report system database comprises a GDB database table and a data table corresponding to the GDB database table; the development mode comprises a selection mode of a GDB summary processor total interface, a calling mode of a database table and a calling mode of a storage process; the report system database calls the data of the GDB database by taking the data table as a unit based on the development mode, and obtains logic operation data through the called data of the GDB database; and presenting the acquired logic operation data on a terminal interface. The report system database is built through the custom factory proxy mode, so that JAVA code processing links are reduced, the development process is simplified, and the pressure of a server is relieved.

Description

GDB data dynamic expansion method, device and storage medium

Technical Field

The present invention relates to the field of big data platforms, and in particular, to a method, an apparatus, and a storage medium for dynamically expanding GDB data.

Background

The enterprise report board system may assist the enterprise in accessing, formatting, and presenting data information to the user in a secure and reliable manner. The current enterprise report billboard system needs to combine and calculate the multi-dimension index data.

The existing enterprise report billboard system takes data imported through an Execl table as a data source and stores data information in a large data platform in a centralized way; when data needs to be displayed, the data needs to be acquired from a large data platform. The data acquisition method comprises the steps of transmitting the data to a report system through a data interface provided by a large data platform, enabling the report system to fall to a database through development of the data interface, then performing logic operation, and finally enabling the report system to display the calculated data on a client or a foreground page. The disadvantages are as follows:

1) The report system and the data platform are developed, so that the workload is huge;

2) When the report system is on line, the report system and the data platform are required to be matched with each other to be on line, and unpredictable risks are increased for the on line;

3) When the report system needs new type business data, new data customization needs to be carried out on the report system and the data platform at the same time, so that the workload is high, and development and debugging risks of a new interface are required.

Therefore, there is a need for a GDB data expansion method with high scalability and high stability.

Disclosure of Invention

The invention provides a GDB data dynamic expansion method, an electronic device and a computer readable storage medium, which mainly reduce JAVA code processing links through customizing factory proxy modes, realize simplified development flow and lighten server pressure.

In order to achieve the above object, the present invention further provides a method for dynamically expanding GDB data, applied to an electronic device, the method comprising:

s110, establishing a report system database corresponding to a GDB database through selecting a development mode, wherein the report system database comprises a GDB database table and a data table corresponding to the GDB database table; the development mode comprises a selection mode of a GDB summary processor total interface, a calling mode of a data table and a calling mode of a storage process;

s120, the report system database calls the data of the GDB database by taking the data table as a unit based on the development mode, and obtains logic operation data through the called data of the GDB database;

s130, presenting the acquired logic operation data on a terminal interface.

Further, preferably, the method for calling the GDB database data in step S120 includes:

s210, the report system database stores a storage process according to the index requirement of the report system;

s220, performing one-to-one correspondence between the implementation class of the GDB summarization processor interface, a data table and a storage process based on the method of the GDB summarization processor total interface of the development mode;

s230, the report system database calls a corresponding storage process according to the implementation class.

Further, preferably, the storage process writes an SQL statement set containing logical operation data in a database table unit for the GDB database.

Further, it is preferred that the reporting system database is created by creating a new user on a database server for the GDB database and granting write rights to the new user. .

Further, preferably, the process of acquiring the logical operation data in the step S120 further includes a write-back process, and the write-back process includes:

s310, writing the obtained logic operation data back to the report system database;

s320, the report system database displays the logic operation data on a terminal interface.

In order to achieve the above purpose, the present invention provides a dynamic expansion system for GDB data, which includes a report system database building unit, a logical operation data obtaining unit, and a logical operation data presenting unit; the report system database establishing unit is used for establishing a report system database corresponding to the GDB database by selecting a development mode; wherein the report system database comprises a GDB database table and a data table corresponding to the GDB database table; the development mode comprises a selection mode of a GDB summary processor total interface, a calling mode of a calling data table and a calling mode of a stored procedure; a logic operation data acquisition unit, configured to call, by the report system database, data of the GDB database in units of the data table based on the development mode, and acquire logic operation data by the called data of the GDB database; and the logic operation data presentation unit is used for presenting the acquired logic operation data on the terminal interface. Further, preferably, the logic operation data acquisition unit includes a data calling module and a logic operation data acquisition module of the GDB database; the data calling module of the GDB database is used for calling the data of the GDB database by taking the data table as a unit based on the development mode through the report system database; the logic operation data acquisition module is used for acquiring logic operation data through the data of the called GDB database. Further, preferably, the data calling module of the GDB database includes a stored procedure storing sub-module, a stored procedure corresponding sub-module, and a stored procedure calling sub-module; the storage process storage sub-module is used for storing the storage process corresponding sub-module of the storage process according to the index requirement of the report system through the report system database, and is used for carrying out one-to-one correspondence on the implementation class of the GDB summarization processor interface, the data table and the storage process through a method of the GDB summarization processor total interface based on the development mode; and the storage process calling sub-module is used for calling the corresponding storage process according to the implementation class through the report system database.

To achieve the above object, the present invention provides an electronic device including: the GDB data dynamic expansion program is stored in the memory, and the GDB data dynamic expansion program realizes the following steps when being executed by the processor: s110, establishing a report system database corresponding to a GDB database through selecting a development mode, wherein the report system database comprises a GDB database table and a data table corresponding to the GDB database table; the development mode comprises a selection mode of a GDB summary processor total interface, a calling mode of a data table and a calling mode of a storage process; s120, the report system database calls the data of the GDB database by taking the data table as a unit based on the development mode, and obtains logic operation data through the called data of the GDB database; s130, presenting the acquired logic operation data on a terminal interface.

In addition, in order to achieve the above object, the present invention also provides a computer readable storage medium having stored therein a computer program comprising a GDB data dynamic expansion program which, when executed by a processor, implements the steps of the above-described GDB data dynamic expansion method.

The GDB data dynamic expansion method, the electronic device and the computer readable storage medium provided by the invention are characterized in that a report system database is established through a custom factory proxy mode, then the data of the GDB database is called by the report system database, logic calculation data is acquired, and finally the acquired logic calculation data is presented at a terminal interface; the beneficial effects are as follows:

(1) According to the invention, data interaction is not needed through an API interface, and the data directly enter a system database, so that the development flow is simplified;

(2) The logical operation of the data reduces the JAVA code processing link and the API interface interaction link, the logical operation directly occurs in the database, the server pressure is reduced, the code quantity is reduced, and the reasonable use of the server resources is realized;

(3) When a new service module is needed, only the data is needed to be inserted into the database, so that the development links of the API interface are reduced.

Drawings

FIG. 1 is a flow chart of a dynamic expansion method for GDB data according to a preferred embodiment of the present invention;

FIG. 2 is a flow chart of a preferred embodiment of the reporting system database calling GDB database data according to the present invention;

FIG. 3 is a schematic diagram of the dynamic expansion method of GDB data according to the present invention;

FIG. 4 is a schematic diagram of the GDB data dynamic expansion system of the present invention;

FIG. 5 is a schematic diagram of an electronic device according to a preferred embodiment of the present invention;

the achievement of the objects, functional features and advantages of the present invention will be further described with reference to the accompanying drawings, in conjunction with the embodiments.

Detailed Description

It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.

The report system database is established through a custom factory proxy mode, then the data of the GDB database is called by the report system database, logic calculation data are obtained, and finally the obtained logic calculation data are presented at a terminal interface; the data interaction is not needed through the API interface, and only new business data is needed to be inserted into the database table corresponding to the report system database, and GDB data directly enters the system database (namely the report system database), so that the development flow is simplified, and the pressure of a server is reduced.

The invention provides a GDB data dynamic expansion method. FIG. 1 shows a flow chart of a preferred embodiment of the GDB data dynamic expansion method according to the present invention. Referring to fig. 1, the method may be performed by an apparatus, which may be implemented in software and/or hardware.

In this embodiment, the dynamic expansion method of GDB data includes: step S110-step 130.

S110, establishing a report system database corresponding to the GDB database through selecting a development mode, wherein the report system database comprises a GDB database table and a data table corresponding to the GDB database table.

Specifically, the development modes include a selection mode of the GDB summary processor total interface, a call mode of a database table, a call mode of a storage procedure, a front-end operation method, and a rear-end operation method. The development mode in the application is a factory agent mode, and can also be other development modes; wherein the factory agent mode includes selecting a GDB summary processor interface and a GDB processor factory, and then adding a stored procedure method that invokes the GDB summary.

S120, the report system database calls the data of the GDB database by taking the data table as a unit based on the development mode, and obtains logic operation data through the called data of the GDB database.

The specific process of obtaining the logic operation data through the called GDB database comprises the steps that after the GDB database receives a data request sent by the report system database, the GDB database generates a database script for needed data, and then the report system database is called remotely and executed to realize that the logic operation data are stored in the report system database.

In a specific embodiment, if the timing task (data request) of the report system database fails to be executed, the GDB database manually initiates a data processing task, then generates a corresponding database script, remotely calls the report system database, and executes the database script to store logical operation data into the report system database.

It should be further noted that authorization of the GDB database for writable permissions is required before invoking the storage process of the GDB database. That is, by creating a database new user with "add-drop-check" rights on the database server for the GDB database, and granting write rights to the reporting system database to the new user.

The method of calling the GDB database data in the step S120 includes steps S210 to S230.

FIG. 2 illustrates a flow of a preferred embodiment of a reporting system database invoking GDB database data in accordance with the present invention. As shown in reference to figure 2 of the drawings,

s210, the report system database stores a storage process according to the index requirement of the report system, wherein the storage process is that the GDB database takes a database table as a unit, and the storage process containing logic operation data is written.

Where stored procedures refer broadly to programs written in a database procedural language, including program packages, stored procedures, functions, and the like. The stored procedure is an important object in the database, and in a large database system, the stored procedure is stored in the database as a set of SQL sentences for performing a specific function, and after the first compiling, the stored procedure is called again without need of compiling again, and the user executes the stored procedure by designating the name of the stored procedure and giving the parameters (if the stored procedure has parameters).

The storage process can be executed for multiple times only by compiling once, so that the performance can be improved by executing the storage process.

S220, the implementation class of the GDB summarization processor interface is in one-to-one correspondence with the data table and the storage process based on the method of the GDB summarization processor total interface of the development mode.

It should be noted that the GDB summary processor interface may correspond to a plurality of implementation classes, and then each implementation class corresponds to the data table and the storage process one by one; in other words, each implementation class corresponds to a data table and a storage procedure.

It should be noted that the storage process may be regarded as a lot, but its role is not limited to batch processing. The complex content is packaged into a unit which is easy to use in the storage process, so that complex operation is simplified; moreover, complex content in the storage process is not required to be repeatedly established, so that the integrity of the content data is ensured. That is, if all developers and applications use the same stored procedure, the code used is the same, thus avoiding the problem that the more steps are performed, the greater the probability of making an error.

The logic operation data in the storage process can be obtained only by calling the corresponding storage process by the report system database according to the implementation class. The logical operation data is obtained by calling the storage process, so that the pressure of the server is reduced, the code quantity is reduced, and the reasonable application of the server resource is realized; but also ensures the accuracy of the data.

In a word, according to the index of the report system, a storage process is required to be stored, wherein the storage process is that a GDB database writes a storage process containing logic operation data by taking a database table as a unit; the implementation class of the GDB summarizing processor interface is in one-to-one correspondence with the data table and the storage process; and the report system database calls a corresponding storage process according to the implementation class, so that logic operation data in the storage process is obtained.

S130, presenting the acquired logic operation data on a terminal interface.

Specifically, the report system database calls the data of the GDB database by taking the data table as a unit, acquires the logic operation data through the data of the called GDB database, and then writes the acquired logic operation data back into the report system database, and the report system database displays the logic operation data.

It should be noted that, the process of obtaining the logic operation data in the step S120 further includes a write-back process, where the write-back process includes: s310, writing the obtained logic operation data back into a report system database; s320, the report system database displays the logic operation data on a terminal interface.

Further, the data field which needs to be specially processed is subjected to a pre-operation or a post-operation. It should be noted that, the pre-operation and the post-operation refer to methods that are automatically invoked before and after executing a certain operation method.

In summary, the present invention establishes a reporting system database corresponding to a GDB database by defining a development schema, the reporting system database including a GDB database table and a data table corresponding to the GDB database table; the report system database calls the data of the GDB database by taking the data table as a unit; the report system database obtains logic operation data through the data of the called GDB database; and presenting the acquired logic operation data on a terminal interface.

The called storage process corresponds to the service module, so that the burden brought by the circulation traversal of the database is reduced. After GDB data is pushed to a reporting system at a designated time, a corresponding reporting system business module invokes a corresponding storage process through a factory mode to calculate, and then the calculated number is written back into a business data table to be presented on a terminal interface. API development calls between systems are reduced, and risks between interaction of the two systems are reduced.

FIG. 3 shows a schematic representation of a GDB data dynamic expansion method according to the present invention; referring to fig. 3, a report system database is established in a custom factory proxy mode, implementation classes of the GDB summary processor interface are in one-to-one correspondence with the data table and the storage process, the report system database calls the corresponding storage process according to the implementation classes, so that logic operation data in the storage process is obtained, the logic operation data is obtained through the data of the called GDB database, and then the obtained logic operation data is presented on a terminal interface. In the implementation process as shown in fig. 3, the report system database is built by the following steps:

1. defining a GDB summary processor interface; 2. defining a GDB processor factory; 3. the Service layer adds a storage process method for calling GDB summary; 4. adding a method for calling the DAO layer in the DAO layer; 5. writing call SQL in an xml file of a domain name corresponding to mybatis; 6. and the GDB summarizing interface is realized corresponding to each service field.

1. And defining a GDB summarization processor interface, and realizing by JAVA project engineering. The interface class is defined to sequentially correspond to a corresponding service module of the system, a certain table of the GDB and a certain storage process in the database; that is, a corresponding GDB data table is found according to the report field involved. Further, the method also comprises the steps of calling a front-end method before the storage process and calling a rear-end method after the storage process; it should be noted that, calling the pre-method before the storage process, that is, summarizing the pre-operation, refers to whether a certain business logic needs to be specified before calculating the data; the post method after the storage process is called is the post operation of summarizing, which means whether the calculation result is required to be packaged for a specific service after the data is calculated and processed.

2. The process of defining a GDB processor factory includes: firstly, defining and processing factory classes, and loading all implementation classes for realizing a GDBCollectHandler interface (a summary processor interface) into a List through Spring after Spring dependency injection.

Specifically, the GDB factory processor implementation class is realized by JAVA; firstly, an application ContextAware automatic assembly interface in a Spring framework is realized, the classes are serialized, the implementation classes for realizing the interface (GDB summary processor abstract interface) are loaded in an automatic assembly method, and are stored in a Map, and when GDB data needs to be processed, a GDB data table which can be corresponding corresponds to the method names of storage processes which are correspondingly processed. And defining a callback function for business processing, and finally, after the annotation of @ Component is added on the implementation class, delivering the class to a spring framework for hosting.

3. The storage process method for calling the GDB summary by the Service layer comprises the following steps: and defining a method for calling the data sql in the DAO layer of the system, and transmitting the corresponding method name of the stored process and the required parameters.

Specifically, the processing class corresponding to the GDB table is realized by JAVA; firstly, the interface defined above (namely, the abstract interface of the GDB summarizing processor) is realized, the domain of GDB table data is set, the name of the corresponding storage process is set, and a certain business logic is specially designated before summarizing and a certain business operation is specially designated after summarizing which are required by definition. Then, in the corresponding business data processing method in the report system, the callback function in the factory processing class is used to transmit the corresponding GDB data table name to be processed, and the data processing can be started.

4. Adding a method for calling the DAO layer in the DAO layer; adding a database calling interface in a project DAO layer; i.e. the method of invoking DAO layer. Specifically, this step is to implement the invocation between databases by JAVA. Firstly, when the project is established, mybatis is integrated in the Spring project, an interface for storing procedure call is defined, the interface receives parameters such as a storage method name and the like transmitted by the factory processing class, and the interface calls the storage procedure placed in the database.

It should be further noted that @ Service and @ Component notes are added to the GDB process engineering and to each implementation class.

When the server is started, the server is loaded by Spring. When the GDB data is pushed to the system database, the calculation is triggered, and then the processing factory can load all Handler realization classes to carry out operation processing of corresponding business logic and database call.

In a specific embodiment, when a new service requirement exists, a new data table of the report system database needs to be added, and an implementation class and a storage process corresponding to the new data table need to be added, so that new report data can be displayed in the foreground.

When the system is online, if the report system changes the data algorithm, the report system can be changed to the data algorithm by modifying the storage process stored in the database and further updating the report system database, so that the newly added system database is avoided, and the unstable risk caused by the online new system is avoided.

In summary, the dynamic expansion method for GDB data provided by the invention establishes a report system database through a custom factory proxy mode, then calls the data of the GDB database by using the report system database and obtains logic calculation data, and then writes the obtained logic calculation data back into the report system database, and the report system database presents the obtained logic calculation data at a terminal interface. According to the invention, data interaction is not required to be carried out through an API interface, and the data directly enter a system database, so that the development flow is simplified; the logical operation of the data reduces the JAVA code processing link and the API interface interaction link, the logical operation directly occurs in the database, the server pressure is reduced, the code quantity is reduced, and the reasonable use of the server resources is realized; when a new service module is needed, only the data is needed to be inserted into the database, so that the development links of the API interface are reduced.

The invention provides a GDB data dynamic expansion system. FIG. 4 shows the structure of a preferred embodiment of the GDB data dynamic expansion system according to the present invention.

Referring to fig. 4, in order to achieve the above object, the present invention provides a GDB data dynamic expansion system, which includes a reporting system database creation unit 41, a logical operation data acquisition unit 42, and a logical operation data presentation unit 43.

The report system database creation unit 41 is configured to create a report system database corresponding to the GDB database by selecting a development mode; wherein the report system database comprises a GDB database table and a data table corresponding to the GDB database table; the development mode comprises a selection mode of a GDB summary processor total interface, a calling mode of a calling data table and a calling mode of a stored procedure;

and a logic operation data obtaining unit 42, configured to call, by the reporting system database, the data of the GDB database in units of the data table based on the development mode, and obtain the logic operation data by the called data of the GDB database.

And a logic operation data presenting unit 43 for presenting the acquired logic operation data at the terminal interface.

The logical operation data obtaining unit 42 includes a data calling module 421 and a logical operation data obtaining module 422 of the GDB database; a data calling module 421 of the GDB database, configured to call, by the reporting system database, data of the GDB database in units of the data table based on the development mode; the logical operation data obtaining module 422 is configured to obtain logical operation data through the data of the called GDB database.

The data calling module 421 of the GDB database includes a stored procedure storing sub-module, a stored procedure corresponding sub-module, and a stored procedure calling sub-module.

The storage process storage sub-module is used for storing the storage process corresponding sub-module of the storage process according to the index requirement of the report system through the report system database, and is used for carrying out one-to-one correspondence on the implementation class of the GDB summarization processor interface, the data table and the storage process through a method of the GDB summarization processor total interface based on the development mode; and the storage process calling sub-module is used for calling the corresponding storage process according to the implementation class through the report system database.

The invention provides a GDB data dynamic expansion method which is applied to an electronic device 5. Fig. 5 shows an application environment of a preferred embodiment of the GDB data dynamic expansion method according to the present invention.

Referring to fig. 5, in the present embodiment, the electronic device 5 may be a terminal device having an operation function, such as a server, a smart phone, a tablet computer, a portable computer, a desktop computer, or the like.

The electronic device 5 includes: processor 52, memory 51, communication bus 53, and network interface 54.

The memory 51 includes at least one type of readable storage medium. The at least one type of readable storage medium may be a non-volatile storage medium such as flash memory, a hard disk, a multimedia card, a card memory 51, etc. In some embodiments, the readable storage medium may be an internal storage unit of the electronic device 5, such as a hard disk of the electronic device 5. In other embodiments, the readable storage medium may also be an external memory 51 of the electronic device 5, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash Card (Flash Card) or the like, which are provided on the electronic device 5.

In the present embodiment, the readable storage medium of the memory 51 is generally used for storing the GDB data dynamic expansion program 50 and the like installed in the electronic device 5. The memory 51 may also be used to temporarily store data that has been output or is to be output.

The processor 52 may in some embodiments be a central processing unit (Central Processing Unit, CPU), microprocessor or other data processing chip for executing program code or processing data stored in the memory 51, such as executing the GDB data dynamic expansion program 50, etc.

The communication bus 53 is used to enable connection communication between these components.

The network interface 54 may optionally comprise a standard wired interface, a wireless interface (e.g., WI-FI interface), typically used to establish a communication connection between the electronic apparatus 5 and other electronic devices.

Fig. 5 shows only an electronic device 5 having components 51-54, but it is understood that not all of the illustrated components are required to be implemented and that more or fewer components may be implemented instead.

Optionally, the electronic device 5 may further comprise a user interface, which may comprise an input unit such as a Keyboard (Keyboard), a voice input device such as a microphone or the like with voice recognition function, a voice output device such as a sound box, a headset or the like, and optionally a standard wired interface, a wireless interface.

Optionally, the electronic device 5 may also comprise a display, which may also be referred to as a display screen or display unit. In some embodiments, the display may be an LED display, a liquid crystal display, a touch-control liquid crystal display, an Organic Light-Emitting Diode (OLED) touch device, or the like. The display is used for displaying information processed in the electronic device 5 and for displaying a visualized user interface.

Optionally, the electronic device 5 may further include a Radio Frequency (RF) circuit, a sensor, an audio circuit, etc., which are not described herein.

In the embodiment of the apparatus shown in fig. 5, an operating system, and a GDB data dynamic expansion program 50 may be included in a memory 51, which is a computer storage medium; the processor 52, when executing the GDB data dynamic expansion program 50 stored in the memory 51, performs the steps of: s110, establishing a report system database corresponding to a GDB database through defining a development mode, wherein the report system database comprises a GDB database table and a data table corresponding to the GDB database table; the development mode comprises a selection mode of a GDB summary processor total interface, a calling mode of a database table and a calling mode of a storage process; s120, the report system database calls the data of the GDB database by taking the data table as a unit based on the development mode, and obtains logic operation data through the called data of the GDB database; s130, presenting the acquired logic operation data on a terminal interface.

In other embodiments, the GDB data dynamic expansion program 50 may also be partitioned into one or more modules, which are stored in memory 51 and executed by a processor 52 to accomplish the present invention. The invention may refer to a series of computer program instruction segments capable of performing a specified function. The GDB data dynamic expansion program 50 may be divided into a reporting system database creation unit, a logical operation data acquisition unit, and a logical operation data presentation unit.

In addition, the invention also provides a computer readable storage medium, wherein the computer readable storage medium comprises a GDB data dynamic expansion program, and the GDB data dynamic expansion program realizes the following operations when being executed by a processor: s110, establishing a report system database corresponding to a GDB database through defining a development mode, wherein the report system database comprises a GDB database table and a data table corresponding to the GDB database table; the development mode comprises a selection mode of a GDB summary processor total interface, a calling mode of a database table and a calling mode of a storage process; s120, the report system database calls the data of the GDB database by taking the data table as a unit based on the development mode, and obtains logic operation data through the called data of the GDB database; s130, presenting the acquired logic operation data on a terminal interface.

The embodiment of the computer readable storage medium of the present invention is substantially the same as the embodiment of the GDB data dynamic expansion method and the electronic device, and will not be described herein.

In general, the GDB data dynamic expansion method of the invention establishes a report system database through a self-defined factory proxy mode, then invokes the data of the GDB database by using the report system database and obtains logic calculation data, and finally presents the obtained logic calculation data at a terminal interface; according to the invention, data interaction is not required to be carried out through an API interface, and the data directly enter a system database, so that the development flow is simplified; the logical operation of the data reduces the JAVA code processing link and the API interface interaction link, the logical operation directly occurs in the database, the server pressure is reduced, the code quantity is reduced, and the reasonable use of the server resources is realized; when a new service module is needed, only the data is needed to be inserted into the database, so that the development links of the API interface are reduced.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, apparatus, article, or method that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, apparatus, article, or method. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, apparatus, article or method that comprises the element.

The foregoing embodiment numbers of the present invention are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments. From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) as described above, comprising instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the method according to the embodiments of the present invention.

The foregoing description is only of the preferred embodiments of the present invention, and is not intended to limit the scope of the invention, but rather is intended to cover any equivalents of the structures or equivalent processes disclosed herein or in the alternative, which may be employed directly or indirectly in other related arts.

Claims

1. A method for dynamically expanding GDB data, applied to an electronic device, the method comprising:

s110, establishing a report system database corresponding to a GDB database through selecting a development mode, wherein the report system database comprises a GDB database table and a data table corresponding to the GDB database table; the development mode comprises a selection mode of a GDB summary processor total interface, a calling mode of a calling data table and a calling mode of a stored procedure;

s120, the report system database calls the data of the GDB database by taking the data table as a unit based on the development mode, and obtains logic operation data through the called data of the GDB database; the method for calling the GDB database data in step S120 includes:

s230, the report system database calls a corresponding storage process according to the implementation class;

the process of obtaining the logical operation data in the step S120 further includes a write-back process, where the write-back process includes:

s320, the report system database displays the logic operation data on a terminal interface;

s130, presenting the acquired logic operation data on a terminal interface.

2. The GDB data dynamic expansion method of claim 1, wherein the storage process is writing an SQL statement set containing logical operation data in a database table unit for a GDB database.

3. The GDB data dynamic expansion method of claim 1, wherein writing rights to a reporting system database are granted to a new user by creating the new user on a database server for the GDB database.

4. The GDB data dynamic expansion system is characterized by comprising a report system database establishing unit, a logic operation data acquiring unit and a logic operation data presenting unit; wherein,,

the report system database establishing unit is used for establishing a report system database corresponding to the GDB database by selecting a development mode; wherein the report system database comprises a GDB database table and a data table corresponding to the GDB database table; the development mode comprises a selection mode of a GDB summary processor total interface, a calling mode of a calling data table and a calling mode of a stored procedure;

a logic operation data acquisition unit, configured to call, by the report system database, data of the GDB database in units of the data table based on the development mode, and acquire logic operation data by the called data of the GDB database;

the logic operation data acquisition unit comprises a data calling module and a logic operation data acquisition module of the GDB database;

the data calling module of the GDB database is used for calling the data of the GDB database by taking the data table as a unit based on the development mode through the report system database; the data calling module of the GDB database comprises a stored procedure storage sub-module, a stored procedure corresponding sub-module and a stored procedure calling sub-module; the storage process storage submodule is used for storing the storage process according to the index requirement of the report system through the report system database; the storage process corresponding submodule is used for carrying out one-to-one correspondence on the implementation class of the GDB summarization processor interface, the data table and the storage process by a method of the GDB summarization processor total interface based on the development mode; the storage process calling sub-module is used for calling the corresponding storage process according to the implementation class through the report system database;

the logic operation data acquisition module is used for acquiring logic operation data through the data of the called GDB database;

the process of obtaining the logical operation data further comprises a write-back process, and the write-back process comprises the following steps:

writing the obtained logic operation data back to the report system database;

the report system database displays the logic operation data on a terminal interface;

and the logic operation data presentation unit is used for presenting the acquired logic operation data on the terminal interface.

5. An electronic device, comprising: the GDB data dynamic expansion program is stored in the memory, and the GDB data dynamic expansion program realizes the following steps when being executed by the processor:

s130, presenting the acquired logic operation data on a terminal interface.

6. A computer readable storage medium, wherein a computer program is stored in the computer readable storage medium, the computer program comprising a GDB data dynamic expansion program, which when executed by a processor, implements the steps of the GDB data dynamic expansion method according to any of claims 1 to 3.