CN113094401A - Target source data generation method, device, equipment and storage medium - Google Patents

Target source data generation method, device, equipment and storage medium Download PDF

Info

Publication number
CN113094401A
CN113094401A CN202110495418.4A CN202110495418A CN113094401A CN 113094401 A CN113094401 A CN 113094401A CN 202110495418 A CN202110495418 A CN 202110495418A CN 113094401 A CN113094401 A CN 113094401A
Authority
CN
China
Prior art keywords
data
field
header
layer
target source
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202110495418.4A
Other languages
Chinese (zh)
Other versions
CN113094401B (en
Inventor
刘小龙
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Jingdong Zhenshi Information Technology Co Ltd
Original Assignee
Beijing Jingdong Zhenshi Information Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Jingdong Zhenshi Information Technology Co Ltd filed Critical Beijing Jingdong Zhenshi Information Technology Co Ltd
Priority to CN202110495418.4A priority Critical patent/CN113094401B/en
Publication of CN113094401A publication Critical patent/CN113094401A/en
Application granted granted Critical
Publication of CN113094401B publication Critical patent/CN113094401B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24Querying
    • G06F16/245Query processing
    • G06F16/2455Query execution
    • G06F16/24553Query execution of query operations
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/22Indexing; Data structures therefor; Storage structures
    • G06F16/2282Tablespace storage structures; Management thereof
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computational Linguistics (AREA)
  • Software Systems (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The invention discloses a target source data generation method, a target source data generation device, target source data generation equipment and a storage medium. Relates to the technical field of computers, and the method comprises the following steps: acquiring data of at least two tables in a database according to the query request; determining a table header basic field and a table header data domain field according to the query request, and determining a data layer basic field and a data layer data domain field according to the data of the at least two tables and the query request, wherein the table header basic field comprises: a query field, the data layer base field comprising: inquiring data corresponding to the field; according to the data layer basic field, the data layer data domain field, the header layer basic field and the header layer data domain field, target source data are generated.

Description

Target source data generation method, device, equipment and storage medium
Technical Field
The embodiment of the invention relates to the technical field of computers, in particular to a target source data generation method, a target source data generation device, target source data generation equipment and a storage medium.
Background
In the prior art, different data details are externally displayed by a data service platform, and because the analysis dimensions are different, different service details need to acquire data from different tables. For example: the possible fields used for showing the logistics delay are as follows: date, planned tolls, actual tolls, waybill number and waybill type, etc., and the fields that may be used to show physical complaint rates are: date, number of the delivery order, customer complaint initiation time, customer complaint person information, customer complaint reason, current resolution person and customer complaint responsibility network point and the like. As shown in fig. 1a, the data application layer displays data details corresponding to different services, and the report needs to configure different underlying data tables, so that the maintenance cost is high, and the development cost is high.
In the process of implementing the invention, at least the following technical problems are found in the prior art:
1. the method comprises the steps that a plurality of detail tables are established according to different business requirements, each detail table corresponds to a different detail field, if the business is increased once, the maintenance cost is high, and the front-end display of the service platform needs to be configured according to the different business detail tables, so that the workload is large, the fault tolerance is poor, and the required iteration efficiency is low.
2. After the service is increased, the maintenance of the source data is complex, a special set of rules for collecting, organizing and maintaining the source data is needed, and additional cost is increased.
Disclosure of Invention
Embodiments of the present invention provide a method, an apparatus, a device, and a storage medium for generating target source data, so as to reduce complexity of configuring detailed data corresponding to various services at a front end and improve reusability of the data.
In a first aspect, an embodiment of the present invention provides a target source data generation method, including:
acquiring data of at least two tables in a database according to the query request;
determining a table header basic field and a table header data domain field according to the query request, and determining a data layer basic field and a data layer data domain field according to the data of the at least two tables and the query request, wherein the table header basic field comprises: a query field, the data layer base field comprising: inquiring data corresponding to a field, wherein the data domain field of the header layer of the table comprises: a service field, the data layer data field comprising: data corresponding to the service field;
and generating target source data according to the data layer basic field, the data layer data domain field, the table header basic field and the table header data domain field.
In a second aspect, an embodiment of the present invention further provides a target source data generating apparatus, where the apparatus includes:
the acquisition module is used for acquiring data of at least two tables in the database according to the query request;
a determining module, configured to determine a table header basic field and a table header data domain field according to the query request, and determine a data layer basic field and a data layer data domain field according to the data of the at least two tables and the query request, where the table header basic field includes: a query field, the data layer base field comprising: inquiring data corresponding to a field, wherein the data domain field of the header layer of the table comprises: a service field, the data layer data field comprising: data corresponding to the service field;
and the generating module is used for generating target source data according to the data layer basic field, the data layer data domain field, the table header basic field and the table header data domain field.
In a third aspect, an embodiment of the present invention further provides a computer device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor executes the computer program to implement the target source data generation method according to any one of the embodiments of the present invention.
In a fourth aspect, the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the target source data generation method according to any one of the embodiments of the present invention.
The embodiment of the invention can determine the table head layer basic field and the table head layer data domain field according to the query request, determine the data layer basic field and the data layer data domain field according to the data of at least two tables and the query request, and generate the target source data according to the data layer basic field, the data layer data domain field, the table head layer basic field and the table head layer data domain field, thereby avoiding the problems of establishing a plurality of detail tables aiming at different services, and if the services are increased once and the maintenance is complex and the maintenance cost is very high, only adding the target source data after the services are increased, and not configuring the plurality of detail tables, thereby reducing the complexity of configuring the detail data corresponding to various services at the front end, and improving the reusability of the data.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present invention and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained according to the drawings without inventive efforts.
Fig. 1a is a prior art application layer display schematic.
FIG. 1b is a flowchart of a target source data generation method according to a first embodiment of the present invention;
FIG. 2a is a flowchart of a target source data generation method according to a second embodiment of the present invention;
FIG. 2b is a diagram of a data layer structure in the second embodiment of the present invention;
FIG. 2c is a diagram of a header layer structure in the second embodiment of the present invention;
FIG. 2d is a diagram illustrating a data structure of target source data according to a second embodiment of the present invention;
FIG. 2e is a technical schematic diagram of the second embodiment of the present invention;
fig. 3 is a schematic structural diagram of a target source data generation apparatus according to a third embodiment of the present invention;
fig. 4 is a schematic structural diagram of a computer device in the fourth embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures. Meanwhile, in the description of the present invention, the terms "first", "second", and the like are used only for distinguishing the description, and are not to be construed as indicating or implying relative importance.
Example one
Fig. 1b is a flowchart of a target source data generating method according to an embodiment of the present invention, where this embodiment is applicable to a case of generating target source data according to a query request, and the method may be executed by a target source data generating device in an embodiment of the present invention, where the device may be implemented in a software and/or hardware manner, as shown in fig. 1b, the method specifically includes the following steps:
s110, acquiring data of at least two tables in the database according to the query request.
The database may be a conventional database or a heterogeneous database. Each component of the heterogeneous database has autonomy, and each database system still has application characteristics, integrity control and security control of the database while realizing data sharing.
At least two tables are pre-stored in the database, where the at least two tables may be tables collected in advance and stored in the database, and for example, the database may store: table1, table2, table3 and table 4.
The data in the table is data purchased from a table, and may be, for example: table1 is a student score table, and the data in table1 is the scores of the students in various departments (mathematics, Chinese and english), for example, the data in table1 is: the math score, the Chinese score and the English score of student A, the math score, the Chinese score and the English score of student B, and the math score, the Chinese score and the English score of student C.
The query request may be a query request generated according to a query field input by a user, or a query request generated according to voice information input by a user, or a query request generated according to gesture information input by a user.
The query request may carry a query field, may also carry a service field, may also carry identification information of the query field, or may carry identification information of the service field.
For example, the manner of obtaining the data of the at least two tables in the database according to the query request may be: acquiring data of at least two tables in the database according to the service field carried by the query request, for example, querying all tables in the database according to the service field carried by the query request, and acquiring the data of at least two tables having the service field if the table has the service field; the manner of obtaining the data of the at least two tables in the database according to the query request may also be: acquiring data of at least two tables in the database according to the query field carried by the query request, for example, querying all tables in the database according to the query field carried by the query request, and acquiring the data of at least two tables having the query field if the query field exists in the tables; the manner of obtaining the data of the at least two tables in the database according to the query request may also be: determining a target field according to the query request, and acquiring data of at least two tables in the database according to the target field, for example, determining the target field according to the query request, querying all tables in the database according to the target field, and acquiring data of at least two tables in which the target field exists if the target field exists in the tables.
And S120, determining a table header basic field and a table header data domain field according to the query request, and determining a data layer basic field and a data layer data domain field according to the data of the at least two tables and the query request.
Wherein the header layer base field includes: a query field, the data layer base field comprising: inquiring data corresponding to a field, wherein the data domain field of the header layer of the table comprises: a service field, the data layer data field comprising: and data corresponding to the service field.
The query field is a field used for querying, the query field may be a query field carried by the query request, the query field may also be a query field determined according to the query request, for example, the query field may be extracted from the query request, and the query field may be: region, city, province, etc., and may be: waybill number, network point, index name, etc. The embodiments of the present invention are not limited in this regard.
The service field may be a service field determined according to the query request, for example, the service field may be a database a that is pre-established with respect to a correspondence between the service field and the query request, and the database a is queried according to the query request q to obtain a service field p, or the service field may be a service field that is determined according to the query request, and for example, the service field may be a database B that is pre-established with respect to a correspondence between the service information and the query request, and the database B is queried according to the query request q to obtain service information W, and the service field p is extracted from the service information W. The service field may be: the waybill type, the waybill status, the ex-warehouse time, the time for the due trip, and the like, which are not limited in the embodiment of the present invention.
The data corresponding to the query field is determined according to the query field, and for example, if the query field is an invoice number, the data corresponding to the query field may be: the IDVA12, if the query field is a date, the data corresponding to the query field may be 2021.4.7.
The data corresponding to the service field is determined according to the service field, and for example, if the service field is warehouse-out time, the data corresponding to the service field may be: 2021.01.01, respectively; if the service field is due time, the data corresponding to the service field may be: 2021.01.02.
for example, the manner of determining the header base field and the header data field according to the query request may be: determining a query field and a service field according to the query request, determining a header basic field according to the query field, and determining a header data domain field according to the service field; the method for determining the table header basic field and the table header data domain field according to the query request may further include: determining a service field according to the query request, determining at least one table header according to the service field, wherein the table header is the table header of at least one table in a database, splicing the at least one table header to obtain a table header data domain field, determining a query field according to the query request, and generating a table header layer basic field according to the query field.
For example, the determining the data layer base field and the data layer data field according to the data of the at least two tables and the query request may be: determining a query field according to the query request, querying the data of the at least two tables according to the query field to obtain data corresponding to the query field, determining a data layer basic field according to the data corresponding to the query field, determining a service field according to the query request, querying the data of the at least two tables according to the service field to obtain data corresponding to the service field, and determining a data layer data domain field according to the data corresponding to the service field.
And S130, generating target source data according to the data layer basic field, the data layer data domain field, the table header basic field and the table header data domain field.
Wherein the target source data comprises: a base field of target source data and a data field of the target source data, the base field of the target source data comprising: a header layer base field of the target source data and a data layer base field of the target source data, the data field of the target source data including: a table header data field of the target source data and a data layer data field of the target source data.
For example, the manner of generating the target source data according to the data layer base field, the data layer data field, the header layer base field, and the header layer data field may be: generating a basic field of target source data according to a data layer basic field and a table header basic field, generating a data field of the target source data according to a data layer data field and a table header data field, and generating the target source data according to the basic field of the target source data and the data field of the target source data. The method for generating the target source data according to the data layer basic field, the data layer data domain field, the header layer basic field and the header layer data domain field may further include: and pre-constructing a data structure of the target source data, and filling the data structure according to the data layer basic field, the data layer data domain field, the table header basic field and the table header data domain field to obtain the target source data.
Optionally, determining the header data field according to the query request includes:
determining a service field according to the query request;
determining at least one header according to the service field;
and splicing the at least one header to obtain a header data domain field.
For example, the method for determining the service field according to the query request may be: determining a service field according to a service identifier carried by the query request; the mode of determining the service field according to the query request may also be: determining service information according to the query request, and determining a service field according to the service information; the mode of determining the service field according to the query request may also be: the query identifier is determined according to the query request, and the service field is determined according to the query identifier.
Wherein the table header data field includes: at least one header.
For example, the manner of determining at least one header according to the service field may be: a database about the corresponding relation between the table headers and the service fields is established in advance, and the database is inquired according to the service fields to obtain at least one table header; the manner of determining at least one header according to the service field may further be: and determining a service identifier according to the service field, and inquiring to obtain at least one header according to the service identifier.
Illustratively, at least one header is spliced to obtain a header data field. For example, at least one header may be spliced by using chinese characters to obtain a header data field.
Optionally, determining the data layer data domain field according to the data of the at least two tables and the query request includes:
acquiring data corresponding to the service fields according to the service fields and the data of the at least two tables;
and splicing the data corresponding to the service field to obtain a data domain field of the data layer.
For example, the manner of obtaining the data corresponding to the service field according to the service field and the data of the at least two tables may be: and querying the data of the at least two tables according to the service field to obtain the data corresponding to the service field, or determining a target keyword according to the service field and querying the data of the at least two tables according to the target keyword to obtain the data corresponding to the service field.
Exemplarily, a service field is determined according to the query request, data corresponding to the service field is obtained according to the service field and data of at least two tables, and the data corresponding to the service field is spliced to obtain a data domain field of the data layer. For example, the fields may be linked by a concat function with fixed delimiters, and when the fields contain the fixed delimiters, the fields may be replaced by a replacement function, which may be a regexp _ place function.
Optionally, determining a table header basic field according to the query request includes:
determining a query field according to the query request;
and generating a table header basic field according to the query field.
The method for determining the query field according to the query request can be that the query field is directly obtained if the query request carries the query field; the mode of determining the query field according to the query request can also be that a target keyword is determined according to the query request, and the query field is determined according to the target keyword; the query field may be determined according to the query request, where the query request carries a query identifier, a target table related to a corresponding relationship between the query identifier and the query field is pre-established, and the target table is searched according to the query identifier to obtain the query field corresponding to the query identifier.
For example, the way of generating the header layer base field according to the query field may be: if the query field comprises at least one field, splicing the at least one field, determining the spliced field as the query field, and generating a table header basic field according to the query field; the way of generating the header layer base field according to the query field may also be: and storing the query field to a corresponding position of a table header basic field. For example, a data structure of the target source data may be pre-constructed, and the data structure of the target source data includes: a base field and a data field, wherein the base field comprises: and generating the table header basic field according to the query field and storing the table header basic field to a corresponding position.
Optionally, determining a data layer basic field according to the data of the at least two tables and the query request includes:
determining a query field according to the query request;
acquiring data corresponding to the query field according to the query field and the data of the at least two tables;
and generating a data layer basic field according to the data corresponding to the query field.
For example, the manner of obtaining the data corresponding to the query field according to the query field and the data of the at least two tables may be that a target keyword is determined according to the query field, and the data of the at least two tables is queried according to the target keyword to obtain the data corresponding to the query field; the manner of obtaining the data corresponding to the query field according to the query field and the data of the at least two tables may also be that the data of the at least two tables are queried according to the query field, and if a target field identical to the query field exists in the at least two tables, the data related to the target field is obtained.
For example, the manner of generating the data layer base field according to the data corresponding to the query field may be: if the query field comprises at least one field, the data corresponding to the query field also comprises at least one group of data, and the at least one group of data is spliced to obtain a data layer basic field; the manner of generating the data layer basic field according to the data corresponding to the query field may also be: and pre-constructing a data structure of the target source data, and generating a data layer basic field according to the data structure of the target source data and the data corresponding to the query field.
Optionally, the obtaining data of at least two tables corresponding to the query request in the database includes:
when an application layer receives a query request, acquiring a service field corresponding to the query request;
acquiring data of at least two tables corresponding to the service fields in a database;
the query request can be generated in a manner that a user inputs a query field in an application layer; the query request generation method can also be used for generating a query request according to the voice information after the user inputs the voice information in the application layer; the query request generation method may also be configured to generate the query request according to the gesture information after the user inputs the gesture information in the application layer, which is not limited in the embodiment of the present invention.
For example, when the application layer receives the query request, the manner of obtaining the service field corresponding to the query request may be: when an application layer receives a query request, acquiring a service field carried by the query request; when the application layer receives the query request, the manner of obtaining the service field corresponding to the query request may also be: when an application layer receives an inquiry request, acquiring identification information carried by the inquiry request, and inquiring to obtain a service field according to the identification information; when the application layer receives the query request, the manner of obtaining the service field corresponding to the query request may also be: when the application layer receives the query request, the service type corresponding to the query request is obtained, and the service field is determined according to the service type.
It should be noted that, in the prior art, after the application layer receives the query request, multiple tables in the database need to be queried, because the analysis dimensions of each table are different, different business details need to obtain data from different tables, the data application layer displays different details, different underlying data tables need to be configured, maintenance cost is high, development cost is high, and fields corresponding to different tables are different, therefore, different tables have different interfaces, and multiple interfaces need to be configured. The technical scheme of the embodiment of the invention is to establish a table according to the query request, and only one interface is needed, thereby reducing the maintainable cost and the development cost.
Correspondingly, after generating the target source data according to the data layer basic field, the data layer data domain field, the table header basic field and the table header data domain field, the method further includes:
and displaying the target source data.
The target source data may be displayed in a table form, or may be displayed in other forms, which is not limited in this embodiment of the present invention.
The display position of the target source data may be a blank area of the current interface or a preset area, which is not limited in this embodiment of the present invention.
Optionally, after generating the target source data according to the data layer basic field, the data layer data field, the table header basic field, and the table header data field, the method further includes:
acquiring a data domain field of a header layer to be added;
adding the to-be-added header data domain field into the header data domain field of the target source data to obtain first target source data;
and displaying the first target source data.
The method for acquiring the header data field of the table to be added may be that a query request is generated according to a query field input by a user, a database is queried according to the query request, data of at least two tables are obtained, if the data of the at least two tables are empty, a target data field is determined according to the query request input by the user, and if the data field of the target source data does not include the target data field, the target data field is determined as the header data field of the table to be added. The obtaining mode of the data domain field of the header of the table to be added can also be that the data domain field of the header of the table to be added is determined by obtaining the key words input by the user.
For example, the to-be-added header data field is added to the header data field of the target source data to obtain a header data field of the first target source data, and the first target source data is generated according to the header data field of the first target source data, where for example, if the to-be-added header data field is physical, the header data field of the target source data includes: mathematics, language and foreign language, then add physics to the table header data domain field of the target source data to obtain the table header data domain field of the first target source data, the table header data domain field of the first target source data includes: mathematics, language, foreign language, and physics.
It should be noted that, in the prior art, if a table header data field needs to be added, the table header data field needs to be added to all tables in the database, so that maintenance cost is increased.
Optionally, after generating the target source data according to the data layer basic field, the data layer data field, the table header basic field, and the table header data field, the method further includes:
acquiring a data domain field of a data layer to be offline;
and hiding the data layer data domain field of the target source data according to the data layer data domain field to be offline.
For example, the data field of the data layer to be downloaded may be obtained in a manner that the data field of the data layer to be downloaded is determined according to a delete field input by a user at the application layer.
For example, according to a manner of hiding the data layer data field of the target source data by the data layer data field to be downloaded, a field in the data layer data field of the target source data, which is the same as the data layer data field to be downloaded, may be set to be null.
Optionally, after generating the target source data according to the data layer basic field, the data layer data field, the table header basic field, and the table header data field, the method further includes:
acquiring a header data domain field of a to-be-offline table;
and hiding the data domain field of the header of the target source data and the data domain field of the data layer according to the data domain field of the header of the to-be-offline table.
Illustratively, the method for hiding the data field of the header layer and the data field of the target source data according to the data field of the header layer of the to-be-offline table may be: hiding a field in a data layer data domain field of the target source data, which is the same as the data domain field of the data layer to be downloaded, and hiding a field in a table header data domain field of the target source data, which corresponds to the data domain field of the data layer to be downloaded. For example, a field in a data layer data field of the target source data, which is the same as the data field of the data layer to be downloaded, may be set to be null, and a field in a header data field of the table of the target source data, which corresponds to the data field of the data layer to be downloaded, may be set to be null. Optionally, after generating the target source data according to the data layer basic field, the data layer data field, the table header basic field, and the table header data field, the method further includes:
acquiring a data domain field of a header layer of a to-be-offline table and a data domain field of a data domain of the to-be-offline table;
hiding a header data domain field of the target source data according to the header data domain field of the to-be-offline table;
and hiding the data layer data domain field of the target source data according to the data layer data domain field to be offline.
For example, according to a manner of hiding the header data field of the target source data by the header data field of the table to be downlinked, a field in the header data field of the target source data, which is the same as the header data field of the table to be downlinked, may be hidden, for example, a field in the header data field of the target source data, which is the same as the header data field of the table to be downlinked, may be set to be null.
For example, according to a manner of hiding the data layer data field of the target source data by the data layer data field to be downloaded, a field in the data layer data field of the target source data, which is the same as the data layer data field to be downloaded, is hidden, for example, a field in the data layer data field of the target source data, which is the same as the data layer data field to be downloaded, is set to be null.
According to the technical scheme, the table header basic field and the table header data domain field can be determined according to the query request, the data layer basic field and the data layer data domain field are determined according to the data of at least two tables and the query request, the target source data are generated according to the data layer basic field, the data layer data domain field, the table header basic field and the table header data domain field, the problem that a plurality of detail tables are established for different services is avoided, if the services are increased once and the maintenance is complex, the maintenance cost is high, only the target source data can be added after the services are increased, the plurality of detail tables do not need to be configured, the complexity of configuring the detail data corresponding to various services at the front end is reduced, and the reusability of the data is improved.
Example two
Fig. 2a is a flowchart of a target source data generation method according to a second embodiment of the present invention, and the second embodiment of the present invention performs further optimization based on the first embodiment of the present invention. As shown in fig. 2a, the method comprises:
s210, acquiring data of at least two tables in the database according to the query request.
And S220, determining a table header basic field and a table header data domain field according to the query request, and determining a data layer basic field and a data layer data domain field according to the data of the at least two tables and the query request.
Wherein the header layer base field includes: a query field, the data layer base field comprising: inquiring data corresponding to a field, wherein the data domain field of the header layer of the table comprises: a service field, the data layer data field comprising: and data corresponding to the service field.
Illustratively, the data layer base field and the data layer data field are determined from the data of the at least two tables and the query request. As shown in fig. 2b, according to the query request, data of at least two tables are obtained from Table1, Table2, Table3, Table …, and Table-N stored in the database, and a data layer basic field and a data layer data field are determined according to the query request and the data of the at least two tables, where the data layer basic field includes: data corresponding to date, data corresponding to waybill number, data corresponding to network node, data corresponding to table type, data corresponding to service code, data corresponding to service type and data corresponding to service name. And the data field is obtained by splicing the customized field through symbols after the customized field is determined according to the service field.
Illustratively, a header base field and a header data field are determined from the query request. As shown in fig. 2c, when the application layer receives the query request, the application layer obtains a query field corresponding to the query request, determines a header layer basic field according to the query field, obtains data corresponding to the query field, and after determining a header according to the data corresponding to the query field, concatenates the header by using chinese characters to obtain a header layer data domain field, where the header layer basic field includes: date, waybill number, network point, table type, service code, service name, service type, etc.
And S230, generating a basic field of the target source data according to the data layer basic field, the header layer basic field, the at least one service code and the at least one service name.
Illustratively, the at least one service code and the at least one service name in the base field are intended to be exposed along with data at the header layer when the front end accesses a particular service. For example, the basic fields of the target source data may include: a header layer base field of the target source data and a data layer base field of the target source data. The header base field of the target source data includes: a header base field, at least one service code, and at least one service name; the data layer base field of the target source data comprises: a data layer base field, at least one service code and at least one service name; it should be noted that, if the header basic field of the target source data includes: two service codes and two service names, the data layer basic field of the target source data also includes: two service codes and two service names. For example, the header base field of the target source data may include: the system comprises an invoice number, network points, service codes, A-001, service names, a proper delivery rate and a service code number 1, wherein the service name is the service name A, the proper delivery rate is the service name B, the service codes are the service codes A, and the A-001 is the service codes B. The data layer base field of the target source data comprises: JDVA12, Temple sites, A001, A-001, a proper delivery rate and 2, wherein the first proper delivery rate is a service name A, the second proper delivery rate is a service name B, A001 is a service code A, and A-001 is a service code B.
S240, generating a data domain field of the target source data according to the data domain field and the header data domain field.
For example, the manner of generating the data field of the target source data according to the data field and the header data field may be: and generating a data domain field of the target source data according to the corresponding relation between the data domain field of the header data and the data domain field of the data, the data domain field of the header data and the data domain field of the data.
And S250, generating target source data according to the basic field of the target source data and the data field of the target source data.
Illustratively, the target source data is generated according to the corresponding relationship between the basic field of the target source data and the data field of the target source data, the basic field of the target source data and the data field of the target source data.
Illustratively, as shown in FIG. 2d, bill _ code is a single sign; index _ code _ a is a service code a: the table head displays the service coding Chinese characters and the data displays the service coding; index _ code _ B is a service code B: existing service coding; index _ name _ a is a service name a: the table header displays the service name Chinese character, and the data displays the service name; index _ name _ B is a service name B: a service name; date _ type is data type 1: gauge outfit, 2: data; stat _ value is a data field: the concat link data value separator uses comma, and the related field value with comma is replaced by regexp _ replace function, and the header data is the same. In addition to the above fields, the method may further include a business _ type _ a, a business _ type _ b, a node _ code, a node _ name, create _ tm, and a use _ case, where the business _ type _ a is a business line: a header is written into a service line, and the data type is written into a specific code KD; business _ type _ b is a business line: all express is written into KD; node _ code is the screen point code-if the data type is 1 then assign: the net point code, if 2, the real net point code is selected; node _ name is the mesh point name-if data type is 1 then assign: if the net point name is 2, the real net point name is taken; create _ tm is data time with dt; use _ case is a usage scenario: business department, sorting center, warehouse, etc. The data structure of the target source data includes: table header layer foundation field, table header layer data field, data layer foundation field and data layer data field, table header layer foundation field includes: the system comprises an invoice number, network points, service codes, A-001, service names, a proper delivery rate and 1, wherein 1 is a data type, A-001 is a service code B, and the service code is a service code A. The data layer base field includes: JDVA12, Temple sites, A001, A-001, the appropriate delivery rate and 2, wherein 2 is a data type, A-001 is a service code B, and A001 is a service code A. The table header data field includes: the waybill type, the waybill state, the ex-warehouse time, the time of the proper delivery and the like, and data field fields of the data layer comprise: bin matching, tut-dose, 2021.01.01, 2021.01.02, etc.
In a specific example, as shown in fig. 2e, Table1, Table2, Table3, …, and Table-N are stored in the database, and when the application layer receives the query request, the application layer determines the data layer basic field, the data layer data field, the header layer basic field, and the header layer data field according to the query request and Table1, Table2, Table3, …, and Table-N stored in the database, and generates the target source data according to the data layer basic field, the data layer data field, the header layer basic field, and the header layer data field.
The technical solution of this embodiment can determine a table header basic field and a table header data domain field according to a query request, determine a data layer basic field and a data layer data domain field according to data of at least two tables and the query request, generate a basic field of target source data according to the data layer basic field, the table header basic field, at least one service code and at least one service name, generate a data domain field of the target source data according to the data layer basic field and the table header data domain field, generate target source data according to the basic field of the target source data and the data domain field of the target source data, avoid creating multiple detail tables for different services, and if a service is increased once and maintenance is complicated and maintenance cost is high, only add the target source data after the service is increased without configuring the multiple detail tables, the complexity of configuring detailed data corresponding to various services by the front end is reduced, and the reusability of the data is improved.
EXAMPLE III
Fig. 3 is a schematic structural diagram of a target source data generating apparatus according to a third embodiment of the present invention. The present embodiment may be applicable to a case of generating target source data according to a query request, where the apparatus may be implemented in a software and/or hardware manner, and the apparatus may be integrated in any device providing a target source data generation function, as shown in fig. 3, where the target source data generation apparatus specifically includes: a first acquisition module 310, a determination module 320, and a generation module 330.
The first obtaining module 310 is configured to obtain data of at least two tables in the database according to the query request;
a determining module 320, configured to determine a table header basic field and a table header data field according to the query request, and determine a data layer basic field and a data layer data field according to the data of the at least two tables and the query request, where the table header basic field includes: a query field, the data layer base field comprising: inquiring data corresponding to a field, wherein the data domain field of the header layer of the table comprises: a service field, the data layer data field comprising: data corresponding to the service field;
the generating module 330 is configured to generate the target source data according to the data layer basic field, the data layer data domain field, the table header basic field, and the table header data domain field.
Optionally, the determining module is specifically configured to:
determining a service field according to the query request;
determining at least one header according to the service field;
and splicing the at least one header to obtain a header data domain field.
Optionally, the determining module is specifically configured to:
acquiring data corresponding to the service fields according to the service fields and the data of the at least two tables;
and splicing the data corresponding to the service field to obtain a data domain field of the data layer.
Optionally, the determining module is specifically configured to:
determining a query field according to the query request;
and generating a table header basic field according to the query field.
Optionally, the determining module is specifically configured to:
determining a query field according to the query request;
acquiring data corresponding to the query field according to the query field and the data of the at least two tables;
and generating a data layer basic field according to the data corresponding to the query field.
Optionally, the generating module is specifically configured to:
generating a basic field of target source data according to the data layer basic field, the table header basic field, at least one service code and at least one service name;
generating a data domain field of the target source data according to the data domain field of the data layer and the data domain field of the header layer;
and generating target source data according to the basic field of the target source data and the data field of the target source data.
Optionally, the first obtaining module is specifically configured to:
when an application layer receives a query request, acquiring a service field corresponding to the query request;
acquiring data of at least two tables corresponding to the service fields in a database;
correspondingly, the method also comprises the following steps:
and the first display module is used for displaying the target source data.
Optionally, the method further includes:
the second acquisition module is used for acquiring a data domain field of the header layer to be added after target source data is generated according to the data layer basic field, the data domain field of the data layer, the data domain field of the header layer and the data domain field of the header layer;
the adding module is used for adding the to-be-added header data domain field into the header data domain field of the target source data to obtain first target source data;
and the second display module is used for displaying the first target source data.
Optionally, the method further includes:
the third obtaining module is used for obtaining the data domain field of the data layer to be offline after the target source data is generated according to the data layer basic field, the data layer data domain field, the header basic field and the header data domain field;
and the first hiding module is used for hiding the data layer data domain field of the target source data according to the data layer data domain field to be downloaded.
Optionally, the method further includes:
a fourth obtaining module, configured to obtain a header data field of the to-be-offline table after generating target source data according to the data layer basic field, the data layer data field, the header basic field, and the header data field;
and the second hiding module is used for hiding the data domain field of the header layer of the target source data and the data domain field of the data layer according to the data domain field of the header layer of the to-be-offline header layer.
Optionally, the method further includes:
a fifth obtaining module, configured to obtain a data field of a data layer to be offline and a data field of a data layer to be offline after generating target source data according to the data layer basic field, the data field of the data layer header basic field, and the data field of the data layer header;
a third hiding module, configured to hide a header data field of the target source data according to the header data field of the to-be-offline header;
and the fourth hiding module is used for hiding the data layer data domain field of the target source data according to the data layer data domain field to be downloaded.
The product can execute the method provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method.
According to the technical scheme, the table header basic field and the table header data domain field can be determined according to the query request, the data layer basic field and the data layer data domain field are determined according to the data of at least two tables and the query request, the target source data are generated according to the data layer basic field, the data layer data domain field, the table header basic field and the table header data domain field, the problem that a plurality of detail tables are established for different services is avoided, if the services are increased once and the maintenance is complex, the maintenance cost is high, only the target source data can be added after the services are increased, the plurality of detail tables do not need to be configured, the complexity of configuring the detail data corresponding to various services at the front end is reduced, and the reusability of the data is improved.
Example four
Fig. 4 is a schematic structural diagram of a computer device in the fourth embodiment of the present invention. FIG. 4 illustrates a block diagram of an exemplary computer device 12 suitable for use in implementing embodiments of the present invention. The computer device 12 shown in FIG. 4 is only one example and should not bring any limitations to the functionality or scope of use of embodiments of the present invention.
As shown in FIG. 4, computer device 12 is in the form of a general purpose computing device. The components of computer device 12 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, and a bus 18 that couples various system components including the system memory 28 and the processing unit 16.
Bus 18 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, such architectures include, but are not limited to, an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MCA) bus, an enhanced ISA bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnect (PCI) bus.
Computer device 12 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by computer device 12 and includes both volatile and nonvolatile media, removable and non-removable media.
The system Memory 28 may include computer system readable media in the form of volatile Memory, such as Random Access Memory (RAM) 30 and/or cache Memory 32. Computer device 12 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 34 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 4, and commonly referred to as a "hard drive"). Although not shown in FIG. 4, a disk drive for reading from and writing to a removable, nonvolatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable, nonvolatile optical disk (a Compact disk-Read Only Memory (CD-ROM)), Digital Video disk (DVD-ROM), or other optical media may be provided. In these cases, each drive may be connected to bus 18 by one or more data media interfaces. System memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.
A program/utility 40 having a set (at least one) of program modules 42 may be stored, for example, in system memory 28, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which examples or some combination thereof may comprise an implementation of a network environment. Program modules 42 generally carry out the functions and/or methodologies of the described embodiments of the invention.
Computer device 12 may also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), with one or more devices that enable a user to interact with computer device 12, and/or with any devices (e.g., network card, modem, etc.) that enable computer device 12 to communicate with one or more other computing devices. Such communication may be through an input/output (I/O) interface 22. In the computer device 12 of the present embodiment, the display 24 is not provided as a separate body but is embedded in the mirror surface, and when the display surface of the display 24 is not displayed, the display surface of the display 24 and the mirror surface are visually integrated. Moreover, computer device 12 may also communicate with one or more networks (e.g., a Local Area Network (LAN), Wide Area Network (WAN)) and/or a public Network (e.g., the Internet) via Network adapter 20. As shown, network adapter 20 communicates with the other modules of computer device 12 via bus 18. It should be understood that although not shown in the figures, other hardware and/or software modules may be used in conjunction with computer device 12, including but not limited to: microcode, device drivers, Redundant processing units, external disk drive Arrays, disk array (RAID) systems, tape drives, and data backup storage systems, to name a few.
The processing unit 16 executes various functional applications and data processing by executing programs stored in the system memory 28, for example, to implement the target source data generation method provided by the embodiment of the present invention:
acquiring data of at least two tables in a database according to the query request;
determining a table header basic field and a table header data domain field according to the query request, and determining a data layer basic field and a data layer data domain field according to the data of the at least two tables and the query request, wherein the table header basic field comprises: a query field, the data layer base field comprising: inquiring data corresponding to a field, wherein the data domain field of the header layer of the table comprises: a service field, the data layer data field comprising: data corresponding to the service field;
and generating target source data according to the data layer basic field, the data layer data domain field, the table header basic field and the table header data domain field.
EXAMPLE five
An embodiment five of the present invention provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements a target source data generating method according to any embodiment of the present invention:
acquiring data of at least two tables in a database according to the query request;
determining a table header basic field and a table header data domain field according to the query request, and determining a data layer basic field and a data layer data domain field according to the data of the at least two tables and the query request, wherein the table header basic field comprises: a query field, the data layer base field comprising: inquiring data corresponding to a field, wherein the data domain field of the header layer of the table comprises: a service field, the data layer data field comprising: data corresponding to the service field;
and generating target source data according to the data layer basic field, the data layer data domain field, the table header basic field and the table header data domain field.
Any combination of one or more computer-readable media may be employed. The computer readable medium may be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
In some embodiments, the clients, servers may communicate using any currently known or future developed network Protocol, such as HTTP (Hyper Text Transfer Protocol), and may interconnect with any form or medium of digital data communication (e.g., a communications network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the Internet (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed network.
The computer readable medium may be embodied in the electronic device; or may exist separately without being assembled into the electronic device.
Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + +, or the like, as well as conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units described in the embodiments of the present disclosure may be implemented by software or hardware. Where the name of an element does not in some cases constitute a limitation on the element itself.
The functions described herein above may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), systems on a chip (SOCs), Complex Programmable Logic Devices (CPLDs), and the like.
In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims (14)

1. A target source data generation method, comprising:
acquiring data of at least two tables in a database according to the query request;
determining a table header basic field and a table header data domain field according to the query request, and determining a data layer basic field and a data layer data domain field according to the data of the at least two tables and the query request, wherein the table header basic field comprises: a query field, the data layer base field comprising: inquiring data corresponding to a field, wherein the data domain field of the header layer of the table comprises: a service field, the data layer data field comprising: data corresponding to the service field;
and generating target source data according to the data layer basic field, the data layer data domain field, the table header basic field and the table header data domain field.
2. The method of claim 1, wherein determining a table header data field from the query request comprises:
determining a service field according to the query request;
determining at least one header according to the service field;
and splicing the at least one header to obtain a header data domain field.
3. The method of claim 2, wherein determining a data layer data field from the data of the at least two tables and the query request comprises:
acquiring data corresponding to the service fields according to the service fields and the data of the at least two tables;
and splicing the data corresponding to the service field to obtain a data domain field of the data layer.
4. The method of claim 1, wherein determining a header base field according to the query request comprises:
determining a query field according to the query request;
and generating a table header basic field according to the query field.
5. The method of claim 1, wherein determining a data layer base field from the data of the at least two tables and the query request comprises:
determining a query field according to the query request;
acquiring data corresponding to the query field according to the query field and the data of the at least two tables;
and generating a data layer basic field according to the data corresponding to the query field.
6. The method according to any one of claims 1-5, wherein generating target source data from the data layer base field, the data layer data field, the header base field, and the header data field comprises:
generating a basic field of target source data according to the data layer basic field, the table header basic field, at least one service code and at least one service name;
generating a data domain field of the target source data according to the data domain field of the data layer and the data domain field of the header layer;
and generating target source data according to the basic field of the target source data and the data field of the target source data.
7. The method of claim 1, wherein obtaining data for at least two tables corresponding to query requests in a database comprises:
when an application layer receives a query request, acquiring a service field corresponding to the query request;
acquiring data of at least two tables corresponding to the service fields in a database;
correspondingly, after generating the target source data according to the data layer basic field, the data layer data domain field, the table header basic field and the table header data domain field, the method further includes:
and displaying the target source data.
8. The method of claim 1, further comprising, after generating the target source data from the data layer base field, the data layer data field, the header base field, and the header data field:
acquiring a data domain field of a header layer to be added;
adding the to-be-added header data domain field into the header data domain field of the target source data to obtain first target source data;
and displaying the first target source data.
9. The method of claim 1, further comprising, after generating the target source data from the data layer base field, the data layer data field, the header base field, and the header data field:
acquiring a data domain field of a data layer to be offline;
and hiding the data layer data domain field of the target source data according to the data layer data domain field to be offline.
10. The method of claim 1, further comprising, after generating the target source data from the data layer base field, the data layer data field, the header base field, and the header data field:
acquiring a header data domain field of a to-be-offline table;
and hiding the data domain field of the header of the target source data and the data domain field of the data layer according to the data domain field of the header of the to-be-offline table.
11. The method of claim 1, further comprising, after generating the target source data from the data layer base field, the data layer data field, the header base field, and the header data field:
acquiring a data domain field of a header layer of a to-be-offline table and a data domain field of a data domain of the to-be-offline table;
hiding a header data domain field of the target source data according to the header data domain field of the to-be-offline table;
and hiding the data layer data domain field of the target source data according to the data layer data domain field to be offline.
12. A target source data generation apparatus, comprising:
the first acquisition module is used for acquiring data of at least two tables in the database according to the query request;
a determining module, configured to determine a table header basic field and a table header data domain field according to the query request, and determine a data layer basic field and a data layer data domain field according to the data of the at least two tables and the query request, where the table header basic field includes: a query field, the data layer base field comprising: inquiring data corresponding to a field, wherein the data domain field of the header layer of the table comprises: a service field, the data layer data field comprising: data corresponding to the service field;
and the generating module is used for generating target source data according to the data layer basic field, the data layer data domain field, the table header basic field and the table header data domain field.
13. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method according to any of claims 1-11 when executing the program.
14. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1-11.
CN202110495418.4A 2021-05-07 2021-05-07 Target source data generation method, device, equipment and storage medium Active CN113094401B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110495418.4A CN113094401B (en) 2021-05-07 2021-05-07 Target source data generation method, device, equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110495418.4A CN113094401B (en) 2021-05-07 2021-05-07 Target source data generation method, device, equipment and storage medium

Publications (2)

Publication Number Publication Date
CN113094401A true CN113094401A (en) 2021-07-09
CN113094401B CN113094401B (en) 2023-08-08

Family

ID=76681615

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110495418.4A Active CN113094401B (en) 2021-05-07 2021-05-07 Target source data generation method, device, equipment and storage medium

Country Status (1)

Country Link
CN (1) CN113094401B (en)

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150278276A1 (en) * 2014-03-26 2015-10-01 International Business Machines Corporation Autonomic regulation of a volatile database table attribute
CN109558440A (en) * 2018-10-18 2019-04-02 平安科技(深圳)有限公司 Batch data processing method, device, computer equipment and storage medium
CN109815228A (en) * 2018-12-14 2019-05-28 深圳壹账通智能科技有限公司 Creation method, device, computer equipment and the readable storage medium storing program for executing of database table
CN110888939A (en) * 2018-09-06 2020-03-17 北京京东尚科信息技术有限公司 Data management method and device
CN111143355A (en) * 2019-12-10 2020-05-12 北京字节跳动网络技术有限公司 Data processing method and device
CN111782923A (en) * 2020-06-24 2020-10-16 平安科技(深圳)有限公司 Data query method and device, electronic equipment and storage medium
WO2021017694A1 (en) * 2019-07-31 2021-02-04 苏宁云计算有限公司 Method and device for generating accounting document based on sap system
CN112506946A (en) * 2020-12-03 2021-03-16 平安科技(深圳)有限公司 Service data query method, device, equipment and storage medium

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150278276A1 (en) * 2014-03-26 2015-10-01 International Business Machines Corporation Autonomic regulation of a volatile database table attribute
CN110888939A (en) * 2018-09-06 2020-03-17 北京京东尚科信息技术有限公司 Data management method and device
CN109558440A (en) * 2018-10-18 2019-04-02 平安科技(深圳)有限公司 Batch data processing method, device, computer equipment and storage medium
CN109815228A (en) * 2018-12-14 2019-05-28 深圳壹账通智能科技有限公司 Creation method, device, computer equipment and the readable storage medium storing program for executing of database table
WO2021017694A1 (en) * 2019-07-31 2021-02-04 苏宁云计算有限公司 Method and device for generating accounting document based on sap system
CN111143355A (en) * 2019-12-10 2020-05-12 北京字节跳动网络技术有限公司 Data processing method and device
CN111782923A (en) * 2020-06-24 2020-10-16 平安科技(深圳)有限公司 Data query method and device, electronic equipment and storage medium
CN112506946A (en) * 2020-12-03 2021-03-16 平安科技(深圳)有限公司 Service data query method, device, equipment and storage medium

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
张鹏伟,陈桦,王建文: "基于耦合关系的数据库多维表头的开发与应用", 陕西科技大学学报, no. 02 *
李恒;: "建立内存机制保证海量数据实时性系统的运行", 科学技术与工程, no. 08 *
王战英;王占宏;: "基于元数据的分布式通用查询系统研究与实现", 微型电脑应用, no. 08 *

Also Published As

Publication number Publication date
CN113094401B (en) 2023-08-08

Similar Documents

Publication Publication Date Title
CN111177231A (en) Report generation method and report generation device
CN109034988B (en) Accounting entry generation method and device
CN110750654A (en) Knowledge graph acquisition method, device, equipment and medium
CN111309760A (en) Data retrieval method, system, device and storage medium
JP2018533126A (en) Method, system, and computer program product for a natural language interface to a database
US20150310050A1 (en) Managing a table of a database
CN108776696B (en) Node configuration method and device, storage medium and electronic equipment
CN110399448B (en) Chinese place name address searching and matching method, terminal and computer readable storage medium
US11487801B2 (en) Dynamic data visualization from factual statements in text
CN110795697A (en) Logic expression obtaining method and device, storage medium and electronic device
CN116594683A (en) Code annotation information generation method, device, equipment and storage medium
CN113760839A (en) Log data compression processing method and device, electronic equipment and storage medium
CN114490723A (en) Unified retrieval method, device, electronic equipment and storage medium
CN111026931A (en) Data query method, device, equipment and medium
EP3822818A1 (en) Method, apparatus, device and storage medium for intelligent response
CN109284452A (en) The online methods of exhibiting of electronic protocol, device, electronic equipment, storage medium
CN110309442B (en) Mapping method, device, equipment and medium for displaying end data
CN113094401A (en) Target source data generation method, device, equipment and storage medium
CN113641633B (en) File processing method, apparatus, electronic device, medium, and computer program
WO2022111148A1 (en) Metadata indexing for information management
CN114238475A (en) Data processing method of data warehouse
CN110704481A (en) Method and device for displaying data
CN105518671A (en) Managing multiple data models over data storage system
CN113393288A (en) Order processing information generation method, device, equipment and computer readable medium
CN113468207A (en) Query method, device, equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant