A method, device, computer equipment and storage medium for querying engineering list

Abstract

The present invention discloses a method for querying a project list, which can solve the technical problems of the prior art that directly querying a project list based on a database results in a low query speed and a high database query pressure. The method comprises: obtaining a project list query request; parsing out a first regional keyword and a first text keyword in the project list query request; determining a target index shard associated with the first regional keyword and the first text keyword; and determining a target project list belonging to the region pointed to by the first regional keyword and containing the first text keyword according to the target index shard. The present invention also discloses a project list query device, a computer device, and a computer-readable storage medium.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a project list query method, device, computer equipment and computer-readable storage medium. Background Art

[0002] Generally speaking, companies in the construction field store their own project lists in internal databases for internal query or processing. However, as the number of project lists increases, improving the query speed and matching accuracy of project lists has become a major bottleneck.

[0003] The inventors have found that due to the overly complex data organization in the database, when directly querying the project list based on the database, the query speed is low and the database query pressure is high.

[0004] With regard to the technical problems that the existing technology directly queries the engineering list based on the database, resulting in low query speed and high database query pressure, no effective solution has been provided so far. Summary of the invention

[0005] The purpose of the present invention is to provide a project list query method, device, computer equipment and computer-readable storage medium, which can solve the technical problems of the prior art that directly querying the project list based on the database results in low query speed and high database query pressure.

[0006] One aspect of the present invention provides a method for querying a project list, the method comprising: obtaining a project list query request; parsing out a first regional keyword and a first text keyword in the project list query request; determining a target index slice associated with the first regional keyword and the first text keyword; and determining a target project list that belongs to the region pointed to by the first regional keyword and contains the first text keyword based on the target index slice.

[0007] Optionally, determining a target project list that belongs to the region pointed to by the first regional keyword and contains the first text keyword according to the target index segment includes: running the target index segment to determine a target project list that belongs to the region pointed to by the first regional keyword and contains the first text keyword in the list content; and / or running the target index segment to determine a target project list that belongs to the region pointed to by the first regional keyword and contains the first text keyword in the list attributes.

[0008] Optionally, before obtaining the project list query request, the method also includes: obtaining the project list; determining the region to which the project list belongs as a second regional keyword; obtaining an index configuration file, the index configuration file defining a first field for creating an index; matching the first field of the index configuration file with a second text keyword of the project list; and creating an index of the project list based on the second regional keyword and the second text keyword matching the first field.

[0009] Optionally, the first field includes a second field for creating an index and for word segmentation processing, and matching the first field of the index configuration file with the second text keyword of the project list includes: determining the second field from the index configuration file; matching the second field with the second text keyword of the project list; creating an index of the project list based on the second regional keyword and the second text keyword matching the first field includes: performing word segmentation processing on the second text keyword matching the second field; and creating an index of the project list based on the second regional keyword and the second text keyword after word segmentation processing.

[0010] Optionally, obtaining the project list includes: obtaining a project cost accounting file; identifying a file format of the project cost accounting file; inputting the project cost accounting file into a parser that matches the file format for parsing to obtain parameter items representing project information contained in the project cost accounting file and dependencies between the parameter items, wherein the parameter items include a project list; storing different parameter items in different data tables of a basic database, wherein the dependencies between the data tables are the same as the dependencies between the parameter items stored in the data tables; and obtaining the project list from a data table of the basic database for storing project lists.

[0011] Optionally, the step of inputting the engineering cost accounting file into a parser that matches the file format for parsing includes: when the file format is a first format, converting the engineering cost accounting file into a second format, and inputting the format-converted engineering cost accounting file into a parser for parsing the second format for parsing; when the file format is a third format, directly inputting the engineering cost accounting file into a parser for parsing the third format for parsing.

[0012] Optionally, the parameter items included in the project cost accounting file include a first parameter item for defining project attributes and a second parameter item for determining project indicators, the second parameter item includes the project list, and after determining the target project list belonging to the region pointed to by the first regional keyword and containing the first text keyword according to the target index segment, the method further includes: determining a first parameter item that has a dependency relationship with the target project list; and / or determining a second parameter item that has a dependency relationship with the target project list.

[0013] Another aspect of the present invention provides a project list query device, which includes: a first acquisition module, used to obtain a project list query request; a parsing module, used to parse out a first regional keyword and a first text keyword in the project list query request; a first determination module, used to determine a target index segment associated with the first regional keyword and the first text keyword; and a second determination module, used to determine a target project list that belongs to the region pointed to by the first regional keyword and contains the first text keyword based on the target index segment.

[0014] Another aspect of the present invention provides a computer device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the computer program, the engineering list query method described in any of the above embodiments is implemented.

[0015] Another aspect of the present invention provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the method for querying the engineering list described in any of the above embodiments is implemented.

[0016] The project list query method provided by the present invention does not directly search for the project list in the database as in the prior art, but is based on a distributed query mechanism, pre-creates an index for the project list and slices the index, and after receiving the project list query request, parses the first regional keyword and the first text keyword carried in the query request, further locates the target index slice associated with the first regional keyword and the first text keyword, and queries the target project list belonging to the region pointed to by the first regional keyword and containing the second text keyword by running the target index slice. Due to the particularity of the construction engineering field, the engineering standards or engineering formats of different regions may be different, so the data in the construction engineering field should be divided by region. In view of this, the present embodiment should consider the regional factor when querying the project list, so the keywords carried in the query request should include the first regional keyword. This embodiment applies the distributed query mechanism to the special field of construction engineering, and searches for the project list in combination with regional characteristics, while improving the query speed and liberating the query pressure of the basic database, and solves the technical problem that the prior art directly queries the project list based on the database, resulting in low query speed and high database query pressure. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Various other advantages and benefits will become apparent to those of ordinary skill in the art by reading the detailed description of the preferred embodiments below. The accompanying drawings are only for the purpose of illustrating the preferred embodiments and are not to be considered as limiting the present invention. Moreover, the same reference symbols are used throughout the accompanying drawings to represent the same components. In the accompanying drawings:

[0018] Figure 1 A flowchart of a method for querying a project list provided in Embodiment 1 of the present invention is shown;

[0019] Figure 2 A flowchart of a method for querying a project list provided in Embodiment 2 of the present invention is shown;

[0020] Figure 3 A flowchart of a method for querying a project list provided in Embodiment 3 of the present invention is shown;

[0021] Figure 4 A block diagram of a project list query device provided by a fourth embodiment of the present invention is shown;

[0022] Figure 5 A block diagram of a computer device suitable for implementing a project list query method provided in a fifth embodiment of the present invention is shown. DETAILED DESCRIPTION

[0023] In order to make the purpose, technical scheme and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0024] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0025] Embodiment 1

[0026] The first embodiment of the present invention can be applied to a Solr cluster, and provide a distributed query service for a project list through SolrCloud and Zookeeper, wherein SolrCloud can be deployed through multiple Solr nodes and a Zookeeper, and Zookeeper is a cluster management software used to manage and coordinate Solr nodes. Specifically, the present embodiment can create an index for the project list in advance, and then store the index shards on each Solr node. When a project list query request is received, the first regional keyword and the first text keyword carried by the query request can be parsed, and then the shard information associated with the two keywords can be determined, and the Solr node where the corresponding target index shard is located can be located through the shard information. The located Solr node can query the target project list by running the target index shard. Specifically, Figure 1 FIG. 1 is a flowchart of a method for querying a project list provided in Embodiment 1 of the present invention. Figure 1 As shown, the project list query method may include steps S11 to S14, wherein:

[0027] Step S11, obtaining a project list query request.

[0028] Among them, the user can enter the keyword for querying the project list in the front end corresponding to the Solr cluster. The front end packages the keyword into the format of an HTTP request and sends it to the Solr cluster, and then the master node of the Solr cluster receives the request.

[0029] Step S12, parsing out the first regional keyword and the first text keyword in the project list query request.

[0030] Due to the particularity of the construction engineering field, the engineering standards or engineering formats in different regions may be different. Therefore, the data in the construction engineering field should be divided by region. In view of this, this embodiment should also consider regional factors when querying the project list, so the keywords carried in the query request should include regional keywords, that is, the first regional keywords. In addition, when querying the project list, it is often necessary to query the project list with a certain feature, so the keywords carried in the query request should also include text keywords, that is, the first text keyword. Further, this embodiment can obtain the first regional keyword and the first text keyword by parsing the project list query request.

[0031] For example, after the master node of the Solr cluster receives a project list query request, the first regional keyword "Beijing" and the first text keyword "concrete" can be obtained by parsing the request.

[0032] Step S13: determining a target index fragment associated with the first regional keyword and the first text keyword.

[0033] In the Solr cluster, an index is created for the project list in advance, and the created index is sharded, and then the index shards are stored in different Solr nodes, wherein each index shard corresponds to a shard information, and the shard information records the location where the index shard is currently stored. In this embodiment, the shard information associated with the first regional keyword and the first text keyword is first determined, and then the target index shard and the location of the target index shard are determined by the content recorded in the shard information.

[0034] Step S14: determining a target project list that belongs to the region pointed to by the first regional keyword and contains the first text keyword according to the target index segment.

[0035] The Solr node storing the target index shard can directly run the target index shard, and then query to obtain the target project list that belongs to the region pointed to by the first regional keyword and contains the first text keyword. Among them, the target project list obtained by the query can be displayed in the form of a list, and the content displayed for each target project list includes: list name, list code, sub-items to which the list belongs, unit projects to which the sub-items belong, list rules, list feature descriptions, and list prices and other list attributes, among which the list feature description is a supplement to the project list. By clicking on any displayed content, you can enter the detailed page of the corresponding target project list. In addition, this embodiment can also perform a secondary search based on the query results of this time, such as screening a list of projects within a certain price range.

[0036] The following is an explanation of the query results using a specific example. For example, when querying the list of projects related to "concrete" in Beijing, the query results are: a total of 2,817 items, the list codes are list 08, list 13 and house repair, the sub-items are concrete piles including cast-in-place concrete piles, foundation and slope treatment including anchor support and soil nail support, the unit projects are decoration and renovation projects, installation projects, municipal projects, landscaping projects and mining projects, etc.

[0037] It should be noted that the “include” in step S4 may be included in the list content itself or in the list attributes. Specifically, step S14 includes step A1 and / or step A2, wherein:

[0038] Step A1, running the target index shard to determine a target project list that belongs to the region pointed to by the first regional keyword and contains the first text keyword in the list content; and / or

[0039] Step A2: Run the target index shard to determine a target project list that belongs to the region pointed to by the first regional keyword and contains the first text keyword in the list attributes.

[0040] For example, when the list content of a certain project list does not contain the first text keyword but the list description feature contains the first text keyword, and the region to which the project list belongs is consistent with the region pointed to by the first regional keyword, the project list can still be determined as the target project list.

[0041] The project list query method provided by the present invention does not directly search for the project list in the database as in the prior art, but is based on a distributed query mechanism, pre-creates an index for the project list and slices the index, and after receiving the project list query request, parses the first regional keyword and the first text keyword carried in the query request, further locates the target index slice associated with the first regional keyword and the first text keyword, and queries the target project list belonging to the region pointed to by the first regional keyword and containing the second text keyword by running the target index slice. Due to the particularity of the construction engineering field, the engineering standards or engineering formats of different regions may be different, so the data in the construction engineering field should be divided by region. In view of this, the present embodiment should consider the regional factor when querying the project list, so the keywords carried in the query request should include the first regional keyword. This embodiment applies the distributed query mechanism to the special field of construction engineering, and searches for the project list in combination with regional characteristics, while improving the query speed and liberating the query pressure of the basic database, and solves the technical problem that the prior art directly queries the project list based on the database, resulting in low query speed and high database query pressure.

[0042] Embodiment 2

[0043] The second embodiment of the present invention provides a method for querying a project list. Before implementing a distributed query of a project list, it is necessary to first create an index for the project list. Through the automated index creation mechanism, the overall time efficiency is improved and labor consumption is saved. Among them, some steps of the project list query method are the same as those in the above embodiment 1. These steps will not be repeated in this embodiment. For details, please refer to the above embodiment 1. Specifically, Figure 2 A flowchart of a method for querying a project list provided in Embodiment 2 of the present invention is shown. Figure 2 As shown, the project list query may include steps S21 to S29, wherein:

[0044] Step S21, obtaining a project list.

[0045] Among them, the project list can be parsed from the project pricing document, or it can be manually produced by cost estimators.

[0046] Optionally, after the project list is updated, if the updated project list is not imported and indexed in time, the query result when the user queries the project list may be inaccurate. Therefore, in order to ensure the accuracy of the query result and the comprehensiveness of the data coverage, the present embodiment may also set a scheduled task to import the project list regularly, and then ensure the accuracy of the query by executing the index creation step. For example, step S21 may include step B1 and step B2, wherein:

[0047] Step B2, detecting whether the current time meets the preset update time;

[0048] Step B2: when the current time meets the preset update time, obtain the project list.

[0049] Step S22, determining the region to which the project list belongs as the second region keyword.

[0050] For example, if the project list belongs to the Beijing area, the second regional keyword is Beijing.

[0051] Step S23: obtaining an index configuration file, wherein the index configuration file defines a first field for creating an index.

[0052] In this embodiment, an index configuration file is preset, and which fields need to be indexed are predefined in the index configuration file according to business requirements. These fields that need to be indexed are referred to as first fields.

[0053] Step S24, matching the first field of the index configuration file with the second text keyword of the project list.

[0054] Step S25: creating an index of the project list according to the second regional keyword and a second text keyword matching the first field.

[0055] Specifically, in this embodiment, the project list can be segmented to obtain keywords of the project list, which are called second text keywords, and then the first field can be matched with these keywords. For the second text keywords that are successfully matched, an index can be created. The second text keywords of the project list include: the second keywords included in the list content of the project list, and / or the second text keywords included in the list attributes of the project list.

[0056] Optionally, considering that some second text keywords may contain two or more words, in order to improve the index accuracy, these second text keywords can be segmented. For example, concrete column can be divided into concrete and column. By searching for concrete, column or concrete column, it can be associated with the second text keyword of concrete column. Specifically, the first field includes a second field for creating an index and for segmentation processing, and a third field for creating an index but not for segmentation processing. For the second text keyword matching the third field in the project list, an index can be directly created; and for the second field, the following steps need to be performed. Specifically, step S24 includes step C1 and step C2, wherein:

[0057] Step C1, determining the second field from the index configuration file;

[0058] Step C2, matching the second field with a second text keyword of the project list.

[0059] For example, the second field is matched with a second text keyword included in the list content of the project list, and / or the second field is matched with a second text keyword included in the list attribute of the project list.

[0060] Accordingly, step S25 may include step D1 and step D2, wherein:

[0061] Step D1, performing word segmentation processing on the second text keyword matching the second field;

[0062] Step D2, creating an index of the project list according to the second regional keyword and the second text keyword after word segmentation processing.

[0063] In this embodiment, when there are second text keywords matching the second field in the project list, it indicates that these second text keywords need to be segmented, and then the second text keyword and the segmented words corresponding to the second text keyword can be created as indexes respectively. For example, for the second text keyword "concrete column" matching the second field, after segmentation, "concrete" and "column" are obtained, and then "concrete", "column" and "concrete column" can be created as indexes respectively.

[0064] Furthermore, the created index can be sharded, and then these index shards can be stored on different Solr nodes, thereby achieving the purpose of distributed query of the project list based on the above operations. The query process is specifically described in the following steps.

[0065] Step S26, obtaining a project list query request.

[0066] Step S27, parsing out the first regional keyword and the first text keyword in the project list query request.

[0067] Step S28: determining a target index fragment associated with the first regional keyword and the first text keyword.

[0068] Step S29: determining a target project list that belongs to the region pointed to by the first regional keyword and contains the first text keyword according to the target index segment.

[0069] Embodiment 3

[0070] The project list can be parsed from the project price calculation file. Considering that there are many types of project price calculation files on the market, the parsing of project price calculation files cannot be limited to a specific format, and other types of project price calculation files should also be able to be identified and parsed. Therefore, Example 3 of the present invention provides a project list query method that can parse the project list from project price calculation files of various formats, wherein some steps of the project list query method correspond to the same steps in the above-mentioned Example 1 and Example 2, and these steps will not be repeated in this embodiment. For details, please refer to the above-mentioned Example 1 and Example 2. Specifically, Figure 3 FIG. 1 is a flowchart of a method for querying a project list provided in Embodiment 3 of the present invention. Figure 3 As shown, the project list query method may include steps S31 to S313, wherein:

[0071] Step S31, obtaining the project cost accounting file.

[0072] Step S32, identifying the file format of the engineering cost accounting file.

[0073] Step S33, inputting the engineering cost accounting file into a parser matching the file format for parsing, obtaining the parameter items representing the engineering information contained in the engineering cost accounting file and the dependency relationship between the parameter items, wherein the parameter items include the engineering list.

[0074] In this embodiment, each parameter item representing the engineering information has a meaning in engineering, such as a single project, a sub-item or a measure item. Each parameter item in the engineering price calculation file includes a first parameter item for defining engineering attributes and a second parameter item for determining engineering indicators, wherein the second parameter item includes the engineering list. Specifically, the first parameter item includes engineering projects, engineering features, parameter information, single projects and / or unit projects, and the second parameter item includes sub-items, measure items, cost summary, engineering list, list name, quota, manpower, materials and equipment and / or manpower, materials and equipment consumption, etc. In addition, there is a dependency relationship between the various parameter items in the engineering price calculation file, such as the engineering project includes single projects, the single project includes unit projects, the unit project includes sub-items and measure items, and the sub-items and measure items both include lists, etc.

[0075] In this embodiment, for engineering cost accounting files in different formats, they need to be input into the corresponding parser for parsing, but the format of the parsing results is consistent, that is, the parsing results include various parameter items and the dependency relationships between the various parameter items.

[0076] Specifically, step S33 may include step E1 and step E2, wherein:

[0077] Step E1, when the file format is the first format, converting the engineering cost accounting file into a second format, and inputting the engineering cost accounting file after the format conversion into a parser for parsing the second format for parsing;

[0078] Step E2, when the file format is the third format, directly input the engineering cost accounting file into a parser for parsing the third format for parsing.

[0079] In this embodiment, each parser is independent of each other, and the parsing of files in different formats can be implemented through the RocketMQ message mechanism to enter the corresponding parser for processing.

[0080] Among them, although the engineering cost accounting files in the first format cannot be parsed directly, these formats of engineering cost accounting files are all formulated based on national standards. For example, they can all be exported to the second format of the national standard, and then input into the parser used to parse the second format for parsing. Among them, the first format can include tbs3, TBS3, bd3, BD3, bs3, BS3, bs4, BS4, jlkz, JLKZ, jlzb, JLZB, jltb, JLTB and other formats, and the second format can be XML format. The parser used to parse the second format is called an XML parser.

[0081] The third format is a format that can be directly parsed. The third format can be an EXCEL file format or a format involved in a GBQ file. The EXCEL file is a project cost accounting file manually calculated by the user. The user can parse the manually processed data into standard project data without transferring to other formats. The formats involved in GBQ files are: gbq4, GBQ4, gbq5, GBQ5, gbg9, GBG9, gyqd, GYQD, gyde and GYDE, etc. When the project cost accounting file is an EXCEL file, the corresponding parser is called an EXCEL parser; when the project cost accounting file is a GBQ file, the corresponding parser is called a GBQ parser.

[0082] It should be noted that GBQ files store data through GSP files. The analysis of GBQ files can be achieved through decompression, data reading and data transfer. Among them, GSP files contain all data tables of engineering cost accounting files. Each type of information has a corresponding table storage. After decompression, each unit project corresponds to a GSP file, so that the engineering cost accounting file can be parsed according to the unit project to obtain the dependency relationship between each parameter item and the parameter item, and the parameter item can also be transferred to the relevant data table.

[0083] Step S34, storing different parameter items in different data tables of the basic database, wherein the dependency relationship between the data tables is the same as the dependency relationship between the parameter items stored in the data tables.

[0084] In this embodiment, each parameter item parsed can be stored in a data table. Since these parameter items have dependencies, the data tables storing the parameter items also have dependencies. In this embodiment, by transferring the parsed parameter items to a data table with a unified and stable format, subsequent processing and reference of these parameter items can be facilitated.

[0085] Step S35, obtaining the project list from a data table for storing project lists in the basic database.

[0086] Step S36, determining the region to which the project list belongs as the second region keyword.

[0087] Step S37: obtaining an index configuration file, wherein the index configuration file defines a first field for creating an index.

[0088] Step S38, matching the first field of the index configuration file with the second text keyword of the project list.

[0089] Step S39: Create an index of the project list according to the second regional keyword and a second text keyword matching the first field.

[0090] Step S310, obtaining a project list query request.

[0091] Step S311, parse out the first regional keyword and the first text keyword in the project list query request.

[0092] Step S312: determine a target index fragment associated with the first regional keyword and the first text keyword.

[0093] Step S313: determining a target project list that belongs to the region pointed to by the first regional keyword and contains the first text keyword according to the target index fragment.

[0094] Optionally, in order to provide more support for subsequent business, such as as a reference item for new construction, this embodiment can further clarify the upper and lower levels of the target project list. Specifically, after step S313, the method further includes step F1 and / or step F2:

[0095] Step F1, determining a first parameter item having a dependency relationship with the target project list; and / or

[0096] Step F2, determining a second parameter item having a dependency relationship with the target project list.

[0097] The second parameter item having a dependency relationship with the target project list described here does not include the target project list itself.

[0098] Embodiment 4

[0099] Embodiment 4 of the present invention provides a device for querying a project list, which corresponds to the method provided in the above embodiment 1. The corresponding technical features and technical effects are not described in detail in this embodiment, and the relevant parts can refer to the above embodiment 1. Specifically, Figure 4 FIG. 4 shows a block diagram of a project list query device provided by Embodiment 4 of the present invention. Figure 4As shown, the engineering list query device 400 may include a first acquisition module 401, a parsing module 402, a first determination module 403 and a second determination module 404, wherein:

[0100] The first acquisition module 401 is used to acquire a project list query request;

[0101] A parsing module 402, configured to parse out a first regional keyword and a first text keyword in the project list query request;

[0102] A first determination module 403 is used to determine a target index segment associated with the first regional keyword and the first text keyword;

[0103] The second determination module 404 is configured to determine, according to the target index segment, a target project list that belongs to the region pointed to by the first regional keyword and contains the first text keyword.

[0104] Optionally, the second determining module is further used for:

[0105] Running the target index shard to determine a target project list that belongs to the region pointed to by the first regional keyword and contains the first text keyword in the list content; and / or

[0106] The target index shard is run to determine a target project list that belongs to the region pointed to by the first regional keyword and contains the first text keyword in the list attributes.

[0107] Optionally, the device further comprises:

[0108] A second acquisition module, used for acquiring a project list before the request for obtaining a project list query;

[0109] A third determination module is used to determine the region to which the project list belongs as a second region keyword;

[0110] A third acquisition module is used to acquire an index configuration file, where the index configuration file defines a first field for creating an index;

[0111] a matching module, for matching a first field of the index configuration file with a second text keyword of the project list;

[0112] A creation module is used to create an index of the project list according to the second regional keyword and a second text keyword matching the first field.

[0113] Optionally, the first field includes a second field for creating an index and for word segmentation processing, and the matching module is further used to:

[0114] Determining the second field from the index configuration file;

[0115] matching the second field with a second text keyword of the project list;

[0116] The creation module is also used to:

[0117] Performing word segmentation processing on the second text keyword matching the second field;

[0118] An index of the project list is created based on the second regional keyword and the second text keyword after word segmentation processing.

[0119] Optionally, the second acquisition module is further used for:

[0120] Obtain engineering costing documents;

[0121] Identify the file format of the engineering cost accounting file;

[0122] Input the engineering cost accounting file into a parser matching the file format for parsing, and obtain various parameter items representing engineering information contained in the engineering cost accounting file and dependency relationships between the various parameter items, wherein the parameter items include a project list;

[0123] Storing different parameter items in different data tables of the basic database, the dependency relationship between the data tables is the same as the dependency relationship between the parameter items stored in the data tables;

[0124] The project list is obtained from a data table of the basic database for storing project lists.

[0125] Optionally, when the second acquisition module inputs the engineering cost accounting file into a parser matching the file format for parsing, it is further configured to:

[0126] When the file format is the first format, converting the engineering cost accounting file into a second format, and inputting the engineering cost accounting file after the format conversion into a parser for parsing the second format for parsing;

[0127] When the file format is the third format, the engineering cost accounting file is directly input into a parser for parsing the third format for parsing.

[0128] Optionally, each parameter item included in the engineering cost accounting file includes a first parameter item for defining engineering attributes and a second parameter item for determining engineering indicators, the second parameter item includes the engineering list, and the device further includes:

[0129] a fourth determination module, configured to determine a first parameter item having a dependency relationship with the target project list after determining the target project list belonging to the region pointed to by the first regional keyword and containing the first text keyword according to the target index segment; and / or

[0130] A fifth determination module is used to determine a second parameter item having a dependency relationship with the target project list after determining the target project list belonging to the region pointed to by the first regional keyword and containing the first text keyword according to the target index segment.

[0131] Embodiment 5

[0132] Figure 5 The block diagram of a computer device suitable for implementing the engineering list query method provided by the fifth embodiment of the present invention is shown. In this embodiment, the computer device 500 can be a smart phone, tablet computer, laptop computer, desktop computer, rack server, blade server, tower server or cabinet server (including independent servers, or server clusters composed of multiple servers) that executes a program. Figure 5 As shown, the computer device 500 of this embodiment includes at least but is not limited to: a memory 501, a processor 502, and a network interface 503 that can be interconnected through a system bus. It should be noted that Figure 5 Only computer device 500 is shown with components 501 - 503 , but it should be understood that implementing all of the components shown is not a requirement, and more or fewer components may alternatively be implemented.

[0133] In this embodiment, the memory 503 includes at least one type of computer-readable storage medium, and the readable storage medium includes flash memory, hard disk, multimedia card, card-type memory (for example, SD or DX memory, etc.), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 501 can be an internal storage unit of the computer device 500, such as a hard disk or memory of the computer device 500. In other embodiments, the memory 501 can also be an external storage device of the computer device 500, such as a plug-in hard disk equipped on the computer device 500, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. Of course, the memory 501 can also include both the internal storage unit of the computer device 500 and its external storage device. In this embodiment, the memory 501 is generally used to store an operating system and various application software installed on the computer device 500, such as program code of a project list query method, etc. The project list query method includes: obtaining a project list query request; parsing out a first regional keyword and a first text keyword in the project list query request; determining a target index segment associated with the first regional keyword and the first text keyword; and determining a target project list that belongs to the region pointed to by the first regional keyword and contains the first text keyword based on the target index segment.

[0134] In some embodiments, the processor 502 may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chips. The processor 502 is generally used to control the overall operation of the computer device 500. For example, it performs control and processing related to data interaction or communication with the computer device 500. In this embodiment, the processor 502 is used to run the program code of the steps of the engineering list query method stored in the memory 501.

[0135] In this embodiment, the engineering list query method stored in the memory 501 can also be divided into one or more program modules and executed by one or more processors (processor 502 in this embodiment) to complete the present invention.

[0136] The network interface 503 may include a wireless network interface or a wired network interface, and the network interface 503 is generally used to establish a communication link between the computer device 500 and other computer devices. For example, the network interface 503 is used to connect the computer device 500 to an external terminal through a network, and to establish a data transmission channel and a communication link between the computer device 500 and the external terminal. The network may be a wireless or wired network such as an intranet, the Internet, the Global System of Mobile communication (GSM), Wideband Code Division Multiple Access (WCDMA), 4G network, 5G network, Bluetooth, Wi-Fi, etc.

[0137] Embodiment 6

[0138] This embodiment six also provides a computer-readable storage medium, including flash memory, hard disk, multimedia card, card-type memory (for example, SD or DX memory, etc.), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, disk, optical disk, server, App application store, etc., on which a computer program is stored, and when the computer program is executed by a processor, the steps of the project list query method are implemented, and the project list query method includes: obtaining a project list query request; parsing out a first regional keyword and a first text keyword in the project list query request; determining a target index segment associated with the first regional keyword and the first text keyword; and determining a target project list belonging to the region pointed to by the first regional keyword and containing the first text keyword according to the target index segment.

[0139] Obviously, those skilled in the art should understand that the modules or steps of the above-mentioned embodiments of the present invention can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, and optionally, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order from that here, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. In this way, the embodiments of the present invention are not limited to any specific combination of hardware and software.

[0140] It should be noted that the serial numbers of the embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0141] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method.

[0142] The above are only preferred embodiments of the present invention, and are not intended to limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made using the contents of the present invention specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. A method for querying a project list, characterized in that: The method comprises: Get the project list query request; Parsing the first regional keyword and the first text keyword in the project list query request; Determining a target index shard associated with the first regional keyword and the first text keyword; Determine, according to the target index segment, a target project list that belongs to the region pointed to by the first regional keyword and contains the first text keyword; Before obtaining the engineering list query request, the method further includes: Check whether the current time meets the preset update time; When the current time meets the preset update time, obtain the project list; The obtaining of the project list includes: Obtain engineering costing documents; Identify the file format of the engineering cost accounting file; Input the engineering cost accounting file into a parser matching the file format for parsing, and obtain various parameter items representing engineering information contained in the engineering cost accounting file and dependency relationships between the various parameter items, wherein the parameter items include a project list; Storing different parameter items in different data tables of the basic database, the dependency relationship between the data tables is the same as the dependency relationship between the parameter items stored in the data tables; Acquire the project list from a data table for storing project lists in the basic database; The parameter items included in the project cost accounting file include a first parameter item for defining project attributes and a second parameter item for determining project indicators, the second parameter item includes the project list, and after determining the target project list belonging to the region pointed to by the first regional keyword and including the first text keyword according to the target index segment, the method further includes: Determining a first parameter item having a dependency relationship with the target project list; and / or A second parameter item having a dependency relationship with the target project list is determined.

2. The method according to claim 1, characterized in that The determining, according to the target index segment, a target project list belonging to the region pointed to by the first regional keyword and containing the first text keyword includes: Running the target index shard to determine a target project list that belongs to the region pointed to by the first regional keyword and contains the first text keyword in the list content; and / or The target index shard is run to determine a target project list that belongs to the region pointed to by the first regional keyword and contains the first text keyword in the list attributes.

3. The method according to claim 1, characterized in that: Before obtaining the engineering list query request and after obtaining the engineering list, the method further includes: Determine the region to which the project list belongs as a second region keyword; Obtain an index configuration file, wherein the index configuration file defines a first field for creating an index; matching a first field of the index configuration file with a second text keyword of the project list; An index of the project list is created based on the second regional keyword and a second text keyword matching the first field.

4. The method according to claim 3, characterized in that The first field includes a second field for creating an index and for word segmentation processing, and matching the first field of the index configuration file with the second text keyword of the project list includes: Determining the second field from the index configuration file; matching the second field with a second text keyword of the project list; The step of creating an index of the project list according to the second regional keyword and a second text keyword matching the first field includes: Performing word segmentation processing on the second text keyword matching the second field; An index of the project list is created based on the second regional keyword and the second text keyword after word segmentation processing.

5. The method according to claim 1, characterized in that The step of inputting the engineering cost accounting file into a parser matching the file format for parsing includes: When the file format is the first format, converting the engineering cost accounting file into a second format, and inputting the engineering cost accounting file after the format conversion into a parser for parsing the second format for parsing; When the file format is the third format, the engineering cost accounting file is directly input into a parser for parsing the third format for parsing.

6. A project list query device for implementing the method described in any one of claims 1 to 5, characterized in that: The device comprises: A first acquisition module is used to acquire a project list query request; A parsing module, used to parse out a first regional keyword and a first text keyword in the project list query request; A first determination module, configured to determine a target index segment associated with the first regional keyword and the first text keyword; The second determination module is used to determine a target project list that belongs to the region pointed to by the first regional keyword and contains the first text keyword according to the target index segment.

7. A computer device, comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method according to any one of claims 1 to 5 when executing the computer program.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 5 is implemented.

Images