CN110674200A - Data query method based on annotation, data query equipment and storage medium - Google Patents
Data query method based on annotation, data query equipment and storage medium Download PDFInfo
- Publication number
- CN110674200A CN110674200A CN201910876893.9A CN201910876893A CN110674200A CN 110674200 A CN110674200 A CN 110674200A CN 201910876893 A CN201910876893 A CN 201910876893A CN 110674200 A CN110674200 A CN 110674200A
- Authority
- CN
- China
- Prior art keywords
- query
- annotation
- sql
- value
- statement
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/242—Query formulation
- G06F16/2433—Query languages
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computational Linguistics (AREA)
- Mathematical Physics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention relates to a data query method, data query equipment and a storage medium based on annotation, wherein the method comprises the following steps: acquiring a get method list of the VO object; obtaining the values in the list; judging whether the @ Where annotation is used or not after judging that the value is not null; if yes, continuing to judge whether the equivalence query or the non-equivalence query is carried out; if the query is equivalent, obtaining a return value through Java reflection, and carrying out SQL dynamic assembly; if the query is a non-equivalent query, replacing the question mark in the attribute after the @ Where in the query statement is annotated with the acquired value, and carrying out SQL splicing; and carrying out data query according to the dynamically assembled SQL query statement or the spliced SQL query statement. The annotation-based data query method provided by the invention enables developers to concentrate on the logic of the current condition when processing query logic, and the annotation-based data query method is not coupled with other query logics, thereby reducing the development and maintenance difficulty.
Description
Technical Field
The invention relates to the technical field of data centers, in particular to a data query method based on annotation, data query equipment and a storage medium.
Background
The database is an important component in the management system, and managers generally have four types of operations of adding, deleting, modifying and checking on the database, wherein the proportion of the query operation is usually about 70%, and the query operation is one of the most important services in the whole management system.
After a management system is preliminarily determined, in order to provide more diversified query services based on the preliminary determination, the general implementation manner is as follows: adding an entry in the form, acquiring a value in the entry by the back-end code, then dynamically assembling SQL (Structured Query Language) according to the acquired value, and finally executing the statement to acquire the data set. The operation of adding the input items in the form is basically unavoidable, but the change difficulty is not large, so that the part of the operation can be ignored. However, the back-end codes are different, a large amount of logic judgment and SQL assembly are needed, and once the query conditions are more, the system maintenance is difficult due to the existence of a large amount of if/else statements.
Therefore, the prior art has yet to be improved.
Disclosure of Invention
Therefore, it is necessary to provide a data query method, a data query device and a storage medium based on annotation to solve the problem of difficult system maintenance caused by the use of a large number of logic judgments and SQL assemblies in the prior art when query services are added to the management system.
The technical scheme of the invention is as follows:
an annotation based data query method, comprising:
acquiring a get method list of the VO object;
traversing the get method list, and executing the get method to obtain the value in the get method list;
judging whether the obtained value is empty or not, and if not, continuously judging whether the value uses the @ Where annotation or not; if the value uses the @ Where annotation, continuing to judge whether an attribute is set after the @ Where annotation, if not, the query request corresponding to the value is an equivalent query, and if so, the query request corresponding to the value is a non-equivalent query;
when the query is judged to be equivalent, acquiring a return value of the get method through Java reflection, and dynamically assembling SQL query statements according to the return value;
when non-equivalence query is judged, replacing the question mark in the attribute after the @ Where in query statement is annotated with the obtained value, and carrying out SQL splicing after in query conditions and like query conditions are processed;
and carrying out data query according to the dynamically assembled SQL query statement or the spliced SQL query statement.
In a further preferred embodiment, the process of dynamically assembling the SQL query statement specifically includes: and acquiring the value of the name attribute of the @ column annotation as the left part of the SQL query statement, and acquiring the return value of the get method through Java reflection as the right part of the SQL query statement.
In a further preferred embodiment, the step of obtaining the value of the name attribute of the @ column annotation as the left part of the SQL query statement and obtaining the return value of the get method through Java reflection, and the step of obtaining the return value of the get method as the right part of the SQL query statement further includes: and determining whether the right part of the SQL query statement needs to be enclosed by a single quotation mark or not according to the type of the acquired return value.
In a further preferred approach, the non-equivalence query comprises: and (3) carrying out unequal value query, wherein an sql attribute is attached to the @ Where annotation in a query statement of the unequal value query.
In a further preferred approach, the non-equivalence query comprises: and (3) direct in query, wherein an isarrayString attribute is added after the @ Where annotation in the query statement of the direct in query.
In a further preferred approach, the non-equivalence query comprises: and (2) indirect in query, wherein logic query annotation is added after @ Where annotation in a query statement of the indirect in query.
In a further preferred approach, the non-equivalence query comprises: and (3) single logic mapping query, wherein query statements of the single logic mapping query are converted into an SQL (structured query language) segment for subsequent splicing processing.
In a further preferred approach, the non-equivalence query comprises: and (3) multi-logic mapping query, wherein a query statement of the multi-logic mapping query selects one of a plurality of logics for query according to a front-end condition value, and is converted into a conditional SQL segment for subsequent splicing processing.
A data querying device comprising a memory, and one or more programs, wherein the one or more programs are stored in the memory, and being configured for execution by one or more processors the one or more programs including for performing the method as described above.
A storage medium having stored thereon a computer program, wherein the computer program, when executed by a processor, implements the steps of the annotation based data query method according to any of the preceding claims.
Compared with the prior art, the annotation-based data query method provided by the invention comprises the following steps: acquiring a get method list of the VO object; traversing the get method list, and executing the get method to obtain the value in the get method list; judging whether the obtained value is empty or not, and if not, continuously judging whether the value uses the @ Where annotation or not; if the value uses the @ Where annotation, continuing to judge whether an attribute is set after the @ Where annotation, if not, the query request corresponding to the value is an equivalent query, and if so, the query request corresponding to the value is a non-equivalent query; when the query is judged to be equivalent, acquiring a return value of the get method through Java reflection, and dynamically assembling SQL query statements according to the return value; when non-equivalence query is judged, replacing the question mark in the attribute after the @ Where in query statement is annotated with the obtained value, and carrying out SQL splicing after in query conditions and like query conditions are processed; and carrying out data query according to the dynamically assembled SQL query statement or the spliced SQL query statement. Based on the above, the annotation-based data query method provided by the invention declares the key query conditions in an annotation manner, extracts and assembles annotation information and VO object information into an SQL query statement for query through Java reflection in the unified query interface, thereby realizing dynamic assembly of conditions, enabling developers to concentrate on the logic of the current conditions when processing query logic, not coupling with other query logics, and reducing development and maintenance difficulty.
Drawings
FIG. 1 is a flow chart of an annotation based data query method in a preferred embodiment of the invention.
Fig. 2 is a functional block diagram of a data query device in a preferred embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
In the prior art, if/else statements are used, by acquiring values of input items from back-end codes, then dynamically assembling SQL query statements according to the values, and finally executing the SQL query statements to perform queries. If the query conditions are more, more if/else statements are in the corresponding back-end code, as shown in the following code:
for developers, not only the development difficulty is large, but also the later maintenance difficulty is large.
The invention provides an annotation-based data query method, as shown in fig. 1, comprising the steps of:
s100, obtaining a get method list of the VO object.
S200, traversing the get method list, and executing the get method to obtain the value in the get method list.
S300, judging whether the obtained value is empty or not, if not, continuously judging whether the value uses the @ Where annotation or not, and if not, judging the next value.
If a value is null, it indicates that the user does not input the query condition in the input field corresponding to the value, and the value is not processed and the query condition is not recorded; if the value is not the last value in the VO list, continuing to acquire the next value; if the value is the last value in the VO list, the next step is continued.
By analyzing the query scene appearing in the service, the query is divided into simple query and complex query, and whether the simple query (namely equivalent query) or the complex query (except the equivalent query, other query requests are all regarded as the complex query) can be judged by judging whether the attribute is set after the @ Where annotation.
That is, if the value uses the @ Where annotation and no attribute is set, the query request corresponding to the value is an equivalent query; if the value uses the @ Where annotation and is provided with the attribute, the query request corresponding to the value is a non-equivalent query.
Simple query: i.e., an equivalent query, generally of the form: field ═ value'.
Complex query: queries other than the equivalence query are defined as complex queries. The types of queries that are generally likely to occur are: field > 'v1', field like '% value%', field in ('v1', 'v2'), and the like.
S400, when the query is judged to be equivalent, obtaining a return value of the get method through Java reflection, and carrying out dynamic assembly on the SQL query statement according to the return value.
Preferably, the process of dynamically assembling the SQL query statement specifically includes: and acquiring the value of the name attribute of the @ column annotation (or other annotations with the same function, or adding an attribute directly after the @ Wherer annotation) as the left part of the SQL query statement, and acquiring the return value of the get method through Java reflection as the right part of the SQL query statement.
Further, the step of obtaining the value of the name attribute of the @ column annotation as the left part of the SQL query statement and obtaining the return value of the get method through Java reflection, and the step of obtaining the return value of the get method as the right part of the SQL query statement further includes: and determining whether the right part of the SQL query statement needs to be enclosed by a single quotation mark or not according to the type of the acquired return value.
For simple queries, the invention directly provides an @ Where annotation at development time, and if a certain field in VO is used as a condition, the invention adds an @ Where declaration to its get method, as shown in the following example code (see line 5 of the following code in detail):
assuming that the returned value of get () is Zhang III, the final SQL segment obtained by the processing of the invention is: and 3. userid is Zhang III.
S500, when the non-equivalence query is judged, replacing the question mark in the attribute after the @ Where annotation in the query statement with the obtained value, and carrying out SQL splicing after the in query condition and the like query condition are processed.
For the processing of complex queries, it is obviously not enough to have the @ Where annotation, the invention is also realized by way of annotation identification plus attribute, the key attribute of annotation is sql, isArrayString, isLike, and the expression is as follows: @ Where (sql ═ isArrayString ═ isLike @, ", isLike ═ is").
As a preferred embodiment of the present invention, the non-equivalence query includes: an inequality query (specially processing like, >, | >, <, | < operator logic), in which the @ Where in the query statement of the inequality query is annotated and then added with an sql attribute (specifically, there are at least two cases: 1, greater than or not equal to the connected sql: e.g. field > 'v1', which only needs to configure the sql attribute; 2, like statement, needs to match with the isLike attribute, specifies what match pattern is, needs to configure the sql attribute and the isLike attribute), and the second case is exemplified by the following codes:
it can be seen that the like logic adds an islike attribute to identify what matches (classified as perfect, left, right, and fuzzy), and 11 in the code represents fuzzy matches.
Preferably, the non-equivalence queries include: direct in query, wherein an isarrayString attribute is appended to the @ Where annotation in the query statement of the direct in query, and example codes are as follows:
@Where(sql＝"type in？",isArrayString＝"")
public List<String>getType(){
}
the isArrayString is used for processing the condition that front-end and back-end reference types are not consistent, and the field for displaying the indication value needs to be enclosed by using a single quotation mark.
Preferably, the non-equivalence queries include: indirect in query, wherein logic query annotation is added after @ Where annotation in query statement of the indirect in query, and example codes are as follows:
in such cases, the range of in is generally not from the front-end condition selection, but is directly obtained through logical queries. The above example is an annotation to "query the employee's leave bar for a given department".
Preferably, the non-equivalence queries include: a single logical mapping query, the query statement of which is to be converted into an SQL segment for subsequent concatenation, example code being:
@Where(sql＝"(userid like？OR name like？)",isLike＝"11")
public String getKeyword(){
}
the above example shows that the user is queried according to keywords, which may match the user name or username.
Preferably, the non-equivalence queries include: and a query statement of the multi-logic mapping query selects one of a plurality of logics to be used for query according to a front-end condition value, and is converted into a conditional SQL segment for subsequent splicing processing, wherein example codes are as follows:
the above example shows that whether the employee information list of the employee photo exists is inquired according to the yes/no front-end selection condition. Wherein? 1 represents.
In a complex query, if there are SQL fragments represented by the annotated SQL attribute? And carrying out value replacement in the unified query interface, and then obtaining a SQL segment which can be used as a condition and is connected with other segments.
S600, data query is carried out according to the SQL query statement after dynamic assembly or the spliced SQL query statement.
In addition, the invention also provides a sequencing annotation (which is an auxiliary annotation), and one field can be declared to be in an AES or DESC sequencing mode through the sequencing annotation.
By operating the database query in an annotation mode, developers can concentrate on the logic of the current condition when processing the query logic and cannot be coupled with other query logics, the development difficulty is reduced, and meanwhile, the maintainability is improved.
In summary, the core of the technical scheme of the invention is as follows: through self-defined annotation, the incidence relation between the query logic and the VO object attribute value is established, the object and annotation information are automatically analyzed through a uniform query interface, the attribute value and the annotation information value of the object are combined into a single SQL condition segment through judgment of various conditions, the query condition is automatically analyzed and automatically assembled, development is simpler, maintenance is more convenient, development efficiency is improved, and maintenance difficulty is reduced.
As shown in FIG. 2, the present invention also provides a data query device comprising a memory 10, and one or more programs, wherein the one or more programs are stored in the memory 10, and configured to be executed by the one or more processors 20 comprises means for performing the annotation based data query method as described above.
The invention also provides a storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, performs the steps of the annotation based data query method as described above.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, databases, or other media used in embodiments provided herein may include non-volatile and/or volatile memory. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), synchronous Link (SyNchlinNk) DRAM (SLDRAM), Rambus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present invention, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. An annotation based data query method, comprising:
acquiring a get method list of the VO object;
traversing the get method list, and executing the get method to obtain the value in the get method list;
judging whether the obtained value is empty or not, and if not, continuously judging whether the value uses the @ Where annotation or not; if the value uses the @ Where annotation, continuing to judge whether an attribute is set after the @ Where annotation, if not, the query request corresponding to the value is an equivalent query, and if so, the query request corresponding to the value is a non-equivalent query;
when the query is judged to be equivalent, acquiring a return value of the get method through Java reflection, and dynamically assembling SQL query statements according to the return value;
when non-equivalence query is judged, replacing the question mark in the attribute after the @ Where in query statement is annotated with the obtained value, and carrying out SQL splicing after in query conditions and like query conditions are processed;
and carrying out data query according to the dynamically assembled SQL query statement or the spliced SQL query statement.
2. The annotation-based data query method according to claim 1, wherein the process of dynamically assembling the SQL query statement specifically comprises: and acquiring the value of the name attribute of the @ column annotation as the left part of the SQL query statement, and acquiring the return value of the get method through Java reflection as the right part of the SQL query statement.
3. The annotation based data query method of claim 2, wherein the step of obtaining the value of the name attribute of the @ column annotation as the left part of the SQL query statement and obtaining the return value of the get method by Java reflection, as the right part of the SQL query statement further comprises: and determining whether the right part of the SQL query statement needs to be enclosed by a single quotation mark or not according to the type of the acquired return value.
4. The annotation based data query method of claim 1, wherein the non-equivalence query comprises: and (3) carrying out unequal value query, wherein an sql attribute is attached to the @ Where annotation in a query statement of the unequal value query.
5. The annotation based data query method of claim 1, wherein the non-equivalence query comprises: and (3) direct in query, wherein an isarrayString attribute is added after the @ Where annotation in the query statement of the direct in query.
6. The annotation based data query method of claim 1, wherein the non-equivalence query comprises: and (2) indirect in query, wherein logic query annotation is added after @ Where annotation in a query statement of the indirect in query.
7. The annotation based data query method of claim 1, wherein the non-equivalence query comprises: and (3) single logic mapping query, wherein query statements of the single logic mapping query are converted into an SQL (structured query language) segment for subsequent splicing processing.
8. The annotation based data query method of claim 1, wherein the non-equivalence query comprises: and (3) multi-logic mapping query, wherein a query statement of the multi-logic mapping query selects one of a plurality of logics for query according to a front-end condition value, and is converted into a conditional SQL segment for subsequent splicing processing.
9. A data query device comprising a memory, and one or more programs, wherein the one or more programs are stored in the memory, and wherein the one or more programs being configured to be executed by the one or more processors comprises instructions for performing the method of any one of claims 1 to 8.
10. A storage medium having stored thereon a computer program, wherein the computer program, when executed by a processor, performs the steps of the annotation based data query method according to any of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910876893.9A CN110674200A (en) | 2019-09-17 | 2019-09-17 | Data query method based on annotation, data query equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910876893.9A CN110674200A (en) | 2019-09-17 | 2019-09-17 | Data query method based on annotation, data query equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110674200A true CN110674200A (en) | 2020-01-10 |
Family
ID=69078074
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910876893.9A Pending CN110674200A (en) | 2019-09-17 | 2019-09-17 | Data query method based on annotation, data query equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110674200A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111782195A (en) * | 2020-06-30 | 2020-10-16 | 广州云徙科技有限公司 | Query method based on adding annotation on request parameter and splicing into SQL |
| CN112507067A (en) * | 2020-11-30 | 2021-03-16 | 厦门海西医药交易中心有限公司 | Cache plug-in annotating device and annotation method |
| CN115858594A (en) * | 2023-02-22 | 2023-03-28 | 北方健康医疗大数据科技有限公司 | Data query method and device, electronic equipment and storage medium |
| CN116303565A (en) * | 2023-02-10 | 2023-06-23 | 广州市玄武无线科技股份有限公司 | Data mapping method, device and medium based on Mybatis-Plus complex query |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103020064A (en) * | 2011-09-20 | 2013-04-03 | 佳都新太科技股份有限公司 | Method and configuration for generating query condition in annotation way |
| CN103870555A (en) * | 2014-03-04 | 2014-06-18 | 赛特斯信息科技股份有限公司 | Spring data JPA dynamic query realization method |
| CN108415834A (en) * | 2018-02-12 | 2018-08-17 | 平安科技（深圳）有限公司 | Explain rear end method of calibration, device, computer equipment and storage medium |
| CN109063056A (en) * | 2018-07-20 | 2018-12-21 | 阿里巴巴集团控股有限公司 | A kind of data query method, system and terminal device |
-
2019
- 2019-09-17 CN CN201910876893.9A patent/CN110674200A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103020064A (en) * | 2011-09-20 | 2013-04-03 | 佳都新太科技股份有限公司 | Method and configuration for generating query condition in annotation way |
| CN103870555A (en) * | 2014-03-04 | 2014-06-18 | 赛特斯信息科技股份有限公司 | Spring data JPA dynamic query realization method |
| CN108415834A (en) * | 2018-02-12 | 2018-08-17 | 平安科技（深圳）有限公司 | Explain rear end method of calibration, device, computer equipment and storage medium |
| CN109063056A (en) * | 2018-07-20 | 2018-12-21 | 阿里巴巴集团控股有限公司 | A kind of data query method, system and terminal device |
Non-Patent Citations (1)
| Title |
|---|
| 全国计算机等级考试命题研究组: "《全国计算机等级考试指定教材辅导 三级数据库技术应试指导及模拟试题集 2005年版》", 30 June 2005 * |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111782195A (en) * | 2020-06-30 | 2020-10-16 | 广州云徙科技有限公司 | Query method based on adding annotation on request parameter and splicing into SQL |
| CN111782195B (en) * | 2020-06-30 | 2024-05-03 | 广州云徙科技有限公司 | Query method for splicing SQL based on adding notes on request parameters |
| CN112507067A (en) * | 2020-11-30 | 2021-03-16 | 厦门海西医药交易中心有限公司 | Cache plug-in annotating device and annotation method |
| CN112507067B (en) * | 2020-11-30 | 2022-08-23 | 厦门海西医药交易中心有限公司 | Cache plug-in annotating device and annotation method |
| CN116303565A (en) * | 2023-02-10 | 2023-06-23 | 广州市玄武无线科技股份有限公司 | Data mapping method, device and medium based on Mybatis-Plus complex query |
| CN115858594A (en) * | 2023-02-22 | 2023-03-28 | 北方健康医疗大数据科技有限公司 | Data query method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110674200A (en) | Data query method based on annotation, data query equipment and storage medium | |
| CN107704265B (en) | Configurable rule generation method for service flow | |
| US6668254B2 (en) | Method and system for importing data | |
| US9652513B2 (en) | Generating data pattern information | |
| JP5768063B2 (en) | Matching metadata sources using rules that characterize conformance | |
| EP2499565B1 (en) | Managing record format information | |
| CN109617646B (en) | Message conversion method and device, computer equipment and computer readable storage medium | |
| US6185583B1 (en) | Parallel rule-based processing of forms | |
| EP2354921A1 (en) | Hybrid evaluation of expressions in DBMS | |
| US6374261B1 (en) | Expert system knowledge-deficiency reduction through automated database updates from semi-structured natural language documents | |
| CN110543356A (en) | abnormal task detection method, device and equipment and computer storage medium | |
| US20190122124A1 (en) | System and method for cognitive troubleshooting assistance | |
| CN112905323A (en) | Data processing method and device, electronic equipment and storage medium | |
| CN109656947B (en) | Data query method and device, computer equipment and storage medium | |
| US7844601B2 (en) | Quality of service feedback for technology-neutral data reporting | |
| CN112069223A (en) | Data acquisition demand processing method and device, computer equipment and storage medium | |
| CN114358596A (en) | Index calculation method and device | |
| CN112579705A (en) | Metadata acquisition method and device, computer equipment and storage medium | |
| CN112784143B (en) | Data processing method, system and computer equipment based on visual computing engine | |
| CN115080596B (en) | Data processing method, device, computer equipment and storage medium | |
| CN116383777B (en) | Data management platform and data right determining method facing data management | |
| CN112925856B (en) | Entity relationship analysis method, entity relationship analysis device, entity relationship analysis equipment and computer storage medium | |
| CN109558303B (en) | Application behavior analysis method and device and electronic equipment | |
| CN112633894A (en) | Method, device, equipment and computer storage medium for pressure testing of repayment capacity | |
| CN115080596A (en) | Data processing method and device, computer 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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200110 |
|
| RJ01 | Rejection of invention patent application after publication |