Database construction method, database construction device, and readable storage medium

Abstract

The application discloses a database construction method, a database construction device and a computer readable storage medium. The method comprises the following steps: acquiring a data stream, and extracting entity data contained in the data stream; determining a corresponding basic table according to the data type of the entity data, adding the entity data to the basic table to generate node data; determining a sub-node type, a sub-node and a main node of the node data; and sequentially associating the main node, the sub-node, the sub-node type and the node data with the main node as a first level. The technical problem that a new entity relationship needs to be established and the development cost is increased when the entity relationship type of a graph database increases in the related art is solved, and the technical effect that the development cost is reduced by only adjusting data and specifying the type when a new entity or relationship is added without adding a new field is achieved.

Description

Technical Field

[0001] This application relates to the field of database management, and more particularly to a database construction method, a database construction device, and a computer-readable storage medium. Background Technology

[0002] Graph databases are data management systems based on vertices and edges as the basic storage units, designed for efficient storage and retrieval of graph data. In graph databases, the relationships between data are just as important as the data itself; they are stored as part of the overall data structure.

[0003] Currently, before storing entity relationships using a graph database, it is necessary to pre-create an entity definition model, an entity attribute model, an associated entity model, and a relationship definition model for each type of data. An entity identifier must be set for each entity in the data to be stored; at least one entity's entity attributes and entity identifier must be stored in the entity definition model and entity attribute model respectively; based on the relationship definition model, the entity relationship data corresponding to the entity is determined, and the entity relationship data is stored in the associated entity model.

[0004] However, as the types of entity relationships in the knowledge graph stored in the graph database increase, it is usually necessary to create new entity relationships, which increases the additional development cost. Summary of the Invention

[0005] This application provides a database construction method, a database construction device, and a computer-readable storage medium, which solves the technical problem in related technologies that new entity relationships need to be established when the number of entity relationship types in a graph database increases, thus increasing development costs. It also achieves the technical effect of reducing development costs by simply adjusting the data and specifying the type when adding new entities or relationships, without adding new fields.

[0006] This application provides a database construction method, which includes:

[0007] Acquire the data stream and extract the entity data contained in the data stream;

[0008] The corresponding base table is determined based on the data type of the entity data, and the entity data is added to the base table to generate node data;

[0009] Determine the child node types, child nodes, and master node of the node data;

[0010] With the master node as the first level, the master node, the child nodes, the child node types, and the node data are sequentially associated.

[0011] Optionally, the step of acquiring the data stream and extracting entity data contained in the data stream includes:

[0012] Acquire the data stream to be processed, and determine the nouns and strings in the data stream based on semantic recognition;

[0013] The noun and the string are used as the entity data.

[0014] Optionally, the step of determining the corresponding base table based on the data type of the entity data and adding the entity data to the base table to generate node data includes:

[0015] Obtain a preset base table, wherein the base table is divided into a string table and an integer table;

[0016] Based on the data type of the entity data, the entity value of the entity data is stored in the base table;

[0017] The identifier of the base table is defined based on the higher-level attributes of the entity data to generate the node data.

[0018] Optionally, the step of storing the entity value of the entity data into the base table according to the data type of the entity data includes:

[0019] Determine the data value of the entity data;

[0020] When the data value is a number, the entity data is stored in the integer table;

[0021] When the data value is not a number or is not entirely a number, the entity data is stored in the string table.

[0022] Optionally, the step of determining the child node type and the master node of the node data includes:

[0023] The higher-level attribute of the node data is used as the node type of the node data;

[0024] The parent attribute of the node type is used as the child node type;

[0025] The child node is defined by the parent attribute of the child node type.

[0026] The parent node is defined by the parent attribute of the child node.

[0027] Optionally, the step of sequentially associating the master node, the child nodes, the child node types, and the node data with the master node as the first level includes:

[0028] The main node, child node, child node type, node data, and node type are treated as entities, and the relationships between these entities are determined.

[0029] Based on the aforementioned association, with the main node as the first level and the child node as the second level, the main node, the child node, the child node type, the node data, and the node type are sequentially associated.

[0030] Optionally, after the step of sequentially associating the master node, child nodes, child node types, and node data with the master node as the first level, the method further includes:

[0031] After all the entity data in the data stream is associated, the main node, child node, child node type, node data, and node type of the entity data are determined.

[0032] An entity display diagram is generated based on the main node, the child node, the child node type, the node data, and the node type.

[0033] Optionally, after the step of generating an entity representation diagram based on the master node, the child node, the child node type, the node data, and the node type is completed, the method further includes:

[0034] Determine the graph identifier of the entity display graph;

[0035] The graph identifier and the entity display graph are stored in the storage brain.

[0036] Furthermore, this application also proposes a database construction device, which includes a memory, a processor, and a database construction program stored in the memory and executable on the processor. When the processor executes the database construction program, it implements the steps of the database construction method described above.

[0037] In addition, this application also proposes a computer-readable storage medium storing a database construction program, which, when executed by a processor, implements the steps of the database construction method as described above.

[0038] One or more technical solutions provided in the embodiments of this application have at least the following technical effects or advantages:

[0039] 1. By adopting a technology that solves the problem of needing to create new entity relationships when the number of entity relationship types in graph databases increases, thus increasing development costs, it achieves the effect of reducing development costs by simply adjusting the data and specifying the type when adding new entities or relationships, without adding new fields.

[0040] 2. By using the main node, child nodes, child node types, node data, and node types as entities to determine the relationships between each entity; and based on these relationships, with the main node as the first level and the child nodes as the second level, sequentially associating the main node, child nodes, child node types, node data, and node types, this effectively solves the technical problem in related technologies where establishing data relationships and querying data requires significant time costs when dealing with large amounts of asset data and complex relationships. Furthermore, it achieves the technical effect that when adding a new target type entity or relationship, only the stored data needs to be adjusted and the corresponding type specified, without requiring additional fields. Attached Figure Description

[0041] Figure 1 This is a flowchart illustrating an embodiment of the database construction method of this application;

[0042] Figure 2 This is a flowchart illustrating Embodiment 2 of the database construction method of this application;

[0043] Figure 3 This is an example of an entity display diagram in Embodiment 2 of the database construction method of this application;

[0044] Figure 4 A schematic diagram of the hardware structure involved in the embodiment of the database construction device of this application. Detailed Implementation

[0045] In related technologies, when a new target type entity is added, a corresponding field needs to be created for storage, resulting in relatively limited functionality. Expansion requires modifications to each corresponding module. In cases of large amounts of asset data and complex relationships, establishing data relationships and querying data requires significant effort and may lead to data omissions. The main technical solution adopted in this application is to acquire entity data from the data stream, add the entity data to the corresponding base table to generate node data, and link different node data in a hierarchical manner. This allows for the addition of a new target type entity or relationship simply by adjusting the stored data and specifying the corresponding type, without requiring additional fields, models, or processing logic, thus reducing database development and maintenance costs.

[0046] To better understand the above technical solutions, exemplary embodiments of this application will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of this application are shown in the drawings, it should be understood that this application can be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided to enable a more thorough understanding of this application and to fully convey the scope of this application to those skilled in the art.

[0047] Example 1

[0048] Embodiment 1 of this application discloses a database construction method, which is referred to... Figure 1 The database construction method includes:

[0049] Step S110: Obtain the data stream and extract the entity data contained in the data stream;

[0050] Optionally, step S110 includes:

[0051] Step S111: Obtain the data stream to be processed, and determine the nouns and strings in the data stream based on semantic recognition;

[0052] Step S112: Use the noun and the string as the entity data.

[0053] In this embodiment, the data stream comprises received entity data, relational data, and attribute data. The data stream can also be received batch field data, such as articles, emails, information tables, resumes, etc.

[0054] As an optional implementation, the data stream to be processed is acquired, the semantic recognition module is invoked, and the noun field and string field in the data stream are determined, wherein the string field is a letter or a number; the noun or string is then treated as entity data.

[0055] Step S120: Determine the corresponding base table according to the data type of the entity data, and add the entity data to the base table to generate node data;

[0056] Optionally, step S120 includes:

[0057] Step S121: Obtain a preset basic table, wherein the basic table is divided into a string table and an integer table;

[0058] Step S122: Store the entity value of the entity data into the base table according to the data type of the entity data;

[0059] Optionally, step S122 includes:

[0060] Step S1221: Determine the data value of the entity data;

[0061] Step S1222: When the data value is a number, store the entity data in the integer table;

[0062] Step S1223: When the data value is not a number or is not entirely a number, store the entity data in the string table.

[0063] Step S123: Define the identifier of the base table according to the higher-level attributes of the entity data to generate the node data.

[0064] In this embodiment, the base table is divided into a string table and an integer table. Chinese characters and letters are stored in the string table, and numbers are stored in the integer table. This means that the stored tables do not need to predefine username or password tables, and no redevelopment is required. The base table here is a general-purpose data storage table, which is called when needed based on the data type. Then, the table identifier is customized as a username, password, or other identifier, saving space occupied by the data tables. In short, there is no need to predefine various data tables; the base table is called when data needs to be stored, and a custom identifier is defined after the data is stored.

[0065] As an optional implementation, a preset base table is obtained. The base table is divided into a string table and an integer table. According to the data type of the entity data, the entity data is stored in the corresponding string table or integer table. The identifier of the base table is defined according to the superior attribute of the entity data. Node data is generated according to the base table and the corresponding identifier.

[0066] For example, if the data value of the current entity data is "Zhang San", then its superordinate attribute is "Name", and the identifier of the string table storing "Zhang San" is "Name".

[0067] Step S130: Determine the child node type, child nodes, and master node of the node data;

[0068] Optionally, step S130 includes:

[0069] Step S131: Use the higher-level attribute of the node data as the node type of the node data;

[0070] Step S132: Use the parent attribute of the node type as the child node type;

[0071] Step S133: Use the parent attribute of the child node type as the child node;

[0072] Step S134: Use the parent attribute of the child node as the parent node.

[0073] In this embodiment, the superior attribute is the type value to which the current data belongs. That is, the master node is the highest-level data type, the child nodes are the subordinate type values ​​of the master node, the child node type is the subordinate type value of the child node, and the node type is the attribute value of the node data, or the subordinate type value of the child node type.

[0074] As an optional implementation, after determining the data value of the node data, the attribute value of the data value or a preset superior attribute is used as the node type of the node data. The superior attribute value of the node type value is then determined, and the superior attribute value is used as the child node type. This process is repeated until the main node is finally determined. The superior attribute can be the attribute value of the current data value or a preset attribute value.

[0075] For example, the data value of the node data is "67928634", with its parent attribute "QQ number" as the node type; the parent attribute "virtual account" of "QQ number" as the child node type; the parent attribute "personnel information" of "virtual account" as the child node; and the parent attribute "cyberspace" of "personnel information" as the master node.

[0076] Step S140: Using the master node as the first level, sequentially associate the master node, the child nodes, the child node types, and the node data.

[0077] As an optional implementation, after determining the master node, child nodes, child node types, node data, and node types, the master node, child nodes, child node types, node data, and node types are sequentially associated into a chain relationship.

[0078] The technical solutions described in the embodiments of this application above have at least the following technical effects or advantages:

[0079] By employing a technique that addresses the technical problem of needing to establish new entity relationships when the number of entity relationship types in graph databases increases, thereby increasing development costs, the technique effectively solves the technical problem of needing to establish new entity relationships when the number of entity relationship types in graph databases increases, thereby increasing development costs. This allows for adding new entities or relationships by simply adjusting the data and specifying the type, without adding new fields, thus reducing development costs.

[0080] Example 2

[0081] Based on Embodiment 1, Embodiment 2 of this application proposes a database construction method, referring to... Figure 2 Step S140 includes:

[0082] Step S210: Treat the main node, child node, child node type, node data, and node type as entities, and determine the association relationship between each entity;

[0083] Step S220: Based on the association relationship, with the main node as the first level and the child node as the second level, the main node, the child node, the child node type, the node data, and the node type are sequentially associated.

[0084] In this embodiment, the main node, child node, child node type, node data, and node type data value are treated as entities, and the relationship between each entity is determined. Based on the determined relationship, the main node is taken as the first level, and the main node, child node, child node type, node data, and node type are sequentially linked as a chain.

[0085] Optionally, after step S140, the method further includes:

[0086] Step S230: After all the entity data in the data stream is associated, determine the main node, child node, child node type, node data, and node type of the entity data.

[0087] Step S240: Generate an entity display diagram based on the main node, the child node, the child node type, the node data, and the node type.

[0088] In this embodiment, a chain association represents the information of one entity data. After determining all the chain associations of entity data, all chain associations are integrated into an entity display diagram in a pattern of master node to master node, with the remaining nodes corresponding sequentially. (Refer to...) Figure 3 , Figure 3 Here is an example of a diagram showing an entity.

[0089] Optionally, after step S240, the following steps may also be included:

[0090] Step S250: Determine the graph identifier of the entity display graph;

[0091] Step S260: Store the graph identifier and the entity display graph in the storage brain.

[0092] In this embodiment, the storage brain is used to store all entity display diagrams. The system can call the corresponding entity display diagram for querying according to the business type, and determine the corresponding entity display diagram according to the diagram identifier corresponding to the query command.

[0093] As an optional implementation, a graph identifier for the entity display diagram is generated based on a preset encryption method, combined with the storage path and the business type and scenario type of the entity display diagram, and the graph identifier and the entity display diagram are stored in the storage brain.

[0094] The technical solutions described in the embodiments of this application above have at least the following technical effects or advantages:

[0095] By using the main node, child nodes, child node types, node data, and node types as entities to determine the relationships between these entities, and then, based on these relationships, sequentially associating the main node, child nodes, child node types, node data, and node types with the main node as the first level and the child nodes as the second level, this effectively solves the technical problem in related technologies where establishing data relationships and querying data requires significant time investment when dealing with large amounts of asset data and complex relationships. Furthermore, it achieves the technical effect that when adding a new target type entity or relationship, only the stored data needs to be adjusted and the corresponding type specified, without requiring additional fields.

[0096] This application also proposes a database construction device, referring to... Figure 4 , Figure 4 This is a schematic diagram of the database construction device structure of the hardware operating environment involved in the embodiments of this application.

[0097] like Figure 4As shown, the database construction device may include: a processor 1001, such as a central processing unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. The communication bus 1002 is used to enable communication between these components. The user interface 1003 may include a display screen or an input unit such as a keyboard; optionally, the user interface 1003 may also include a standard wired interface or a wireless interface. The network interface 1004 may optionally include a standard wired interface or a wireless interface (such as a Wi-Fi interface). The memory 1005 may be a high-speed random access memory (RAM) or a stable non-volatile memory (NVM), such as a disk drive. The memory 1005 may also optionally be a storage device independent of the aforementioned processor 1001.

[0098] Those skilled in the art will understand that Figure 4 The structure shown does not constitute a limitation on the database building device and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0099] Optionally, the memory 1005 is electrically connected to the processor 1001. The processor 1001 can be used to control the operation of the memory 1005 and can also read data in the memory 1005 to realize database construction.

[0100] Optionally, such as Figure 4 As shown, the memory 1005, which serves as a storage medium, may include an operating system, a data storage module, a network communication module, a user interface module, and a database construction program.

[0101] Optionally, in Figure 4 In the database construction device shown, the network interface 1004 is mainly used for data communication with other devices; the user interface 1003 is mainly used for data interaction with users; the processor 1001 and memory 1005 in the database construction device of this application can be set in the database construction device.

[0102] like Figure 4 As shown, the database construction device calls the database construction program stored in the memory 1005 through the processor 1001 and executes the relevant steps of the database construction method provided in this application embodiment:

[0103] Acquire the data stream and extract the entity data contained in the data stream;

[0104] The corresponding base table is determined based on the data type of the entity data, and the entity data is added to the base table to generate node data;

[0105] Determine the child node types, child nodes, and master node of the node data;

[0106] With the master node as the first level, the master node, the child nodes, the child node types, and the node data are sequentially associated.

[0107] Optionally, the processor 1001 may call the database construction program stored in the memory 1005 and also perform the following operations:

[0108] Acquire the data stream to be processed, and determine the nouns and strings in the data stream based on semantic recognition;

[0109] The noun and the string are used as the entity data.

[0110] Optionally, the processor 1001 may call the database construction program stored in the memory 1005 and also perform the following operations:

[0111] Obtain a preset base table, wherein the base table is divided into a string table and an integer table;

[0112] Based on the data type of the entity data, the entity value of the entity data is stored in the base table;

[0113] The identifier of the base table is defined based on the higher-level attributes of the entity data to generate the node data.

[0114] Optionally, the processor 1001 may call the database construction program stored in the memory 1005 and also perform the following operations:

[0115] Determine the data value of the entity data;

[0116] When the data value is a number, the entity data is stored in the integer table;

[0117] When the data value is not a number or is not entirely a number, the entity data is stored in the string table.

[0118] Optionally, the processor 1001 may call the database construction program stored in the memory 1005 and also perform the following operations:

[0119] The higher-level attribute of the node data is used as the node type of the node data;

[0120] The parent attribute of the node type is used as the child node type;

[0121] The child node is defined by the parent attribute of the child node type.

[0122] The parent node is defined by the parent attribute of the child node.

[0123] Optionally, the processor 1001 may call the database construction program stored in the memory 1005 and also perform the following operations:

[0124] The main node, child node, child node type, node data, and node type are treated as entities, and the relationships between these entities are determined.

[0125] Based on the aforementioned association, with the main node as the first level and the child node as the second level, the main node, the child node, the child node type, the node data, and the node type are sequentially associated.

[0126] Optionally, the processor 1001 may call the database construction program stored in the memory 1005 and also perform the following operations:

[0127] After all the entity data in the data stream is associated, the main node, child node, child node type, node data, and node type of the entity data are determined.

[0128] An entity display diagram is generated based on the main node, the child node, the child node type, the node data, and the node type.

[0129] Optionally, the processor 1001 may call the database construction program stored in the memory 1005 and also perform the following operations:

[0130] Determine the graph identifier of the entity display graph;

[0131] The graph identifier and the entity display graph are stored in the storage brain.

[0132] Furthermore, embodiments of this application also propose a computer-readable storage medium storing a database construction program, which, when executed by a processor, implements the relevant steps of any embodiment of the database construction method described above.

[0133] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0134] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0135] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0136] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0137] It should be noted that any reference signs placed between parentheses in the claims should not be construed as limiting the claims. The word "comprising" does not exclude the presence of components or steps not listed in the claims. The word "a" or "an" preceding a component does not exclude the presence of a plurality of such components. This application can be implemented by means of hardware comprising several different components and by means of a suitably programmed computer. In a unit claim enumerating several means, several of these means may be embodied by the same item of hardware. The use of the words first, second, and third, etc., does not indicate any order. These words can be interpreted as names.

[0138] Although preferred embodiments of this application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of this application.

[0139] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A database construction method, characterized in that, The database construction method includes: Obtain the data stream to be processed, and determine the nouns and strings in the data stream based on semantic recognition. The data stream consists of received entity data, relation data, and attribute data. The nouns and the strings are included as entity data in the data stream; Obtain a preset base table, wherein the base table is divided into a string table and an integer table; Based on the data type of the entity data, the entity value of the entity data is stored in the base table; The identifier of the base table is defined based on the higher-level attributes of the entity data to generate node data; The higher-level attribute of the node data is used as the node type of the node data; Use the parent attribute of the node type as the child node type; Use the parent attribute of the child node type as the child node; The parent node is defined by the parent attribute of the child node. With the master node as the first level, the master node, the child nodes, the child node types, and the node data are sequentially associated. The step of sequentially associating the master node, child nodes, child node types, and node data with the master node as the first level includes: The main node, child node, child node type, node data, and node type are treated as entities, and the relationships between these entities are determined. Based on the aforementioned association, with the main node as the first level and the child node as the second level, the main node, the child node, the child node type, the node data, and the node type are sequentially linked as a chain association, with each chain association representing the information of an entity data. After determining the chain relationships of all entity data, the chain relationships are integrated into an entity display diagram in a pattern of master node to master node and the remaining nodes corresponding to each other in sequence.

2. The database construction method as described in claim 1, characterized in that, The step of storing the entity value of the entity data into the base table according to the data type of the entity data includes: Determine the data value of the entity data; When the data value is a number, the entity data is stored in the integer table; When the data value is not a number or is not entirely a number, the entity data is stored in the string table.

3. The database construction method as described in claim 1, characterized in that, Following the step of sequentially associating the master node, child nodes, child node types, and node data with the master node as the first level, the method further includes: After all the entity data in the data stream is associated, the main node, child node, child node type, node data, and node type of the entity data are determined. An entity display diagram is generated based on the main node, the child node, the child node type, the node data, and the node type.

4. The database construction method as described in claim 3, characterized in that, After the step of generating an entity representation diagram based on the master node, the child node, the child node type, the node data, and the node type is completed, the method further includes: Determine the graph identifier of the entity display graph; The graph identifier and the entity display graph are stored in the storage brain.

5. A database construction device, characterized in that, The system includes a memory, a processor, and a database construction program stored in the memory and executable on the processor, wherein the processor, when executing the database construction program, implements the steps of the database construction method as described in any one of claims 1 to 4.

6. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a database construction program, which, when executed by a processor, implements the steps of the database construction method as described in any one of claims 1 to 4.

Images