CN112486714A - Database exception capture processing method and device and computer equipment - Google Patents
Database exception capture processing method and device and computer equipment Download PDFInfo
- Publication number
- CN112486714A CN112486714A CN201910865877.XA CN201910865877A CN112486714A CN 112486714 A CN112486714 A CN 112486714A CN 201910865877 A CN201910865877 A CN 201910865877A CN 112486714 A CN112486714 A CN 112486714A
- Authority
- CN
- China
- Prior art keywords
- function
- exception
- database
- operation function
- decorator
- 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
- 238000003672 processing method Methods 0.000 title claims abstract description 15
- 238000004806 packaging method and process Methods 0.000 claims abstract description 35
- 238000012545 processing Methods 0.000 claims abstract description 31
- 238000000034 method Methods 0.000 claims abstract description 27
- 230000002159 abnormal effect Effects 0.000 claims abstract description 26
- 238000005538 encapsulation Methods 0.000 claims abstract description 12
- 230000005856 abnormality Effects 0.000 claims abstract description 6
- 230000006870 function Effects 0.000 claims description 154
- 238000004590 computer program Methods 0.000 claims description 11
- 238000012423 maintenance Methods 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 239000000463 material Substances 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 238000011161 development Methods 0.000 description 2
- 230000008676 import Effects 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 239000012141 concentrate Substances 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000005034 decoration Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000012827 research and development Methods 0.000 description 1
- 238000004904 shortening Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0766—Error or fault reporting or storing
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a method and a device for capturing and processing database exception and computer equipment. The database exception capturing and processing method comprises the following steps: packaging the operation function in the database and generating a packaging function; when the operation function calls the database, judging whether the abnormality occurs by using the encapsulation function; and if the exception occurs, performing corresponding exception processing on the operation function. According to the method, the device and the computer equipment for capturing and processing the database exception, the operation function in the database is packaged, the packaging function is generated, when the operation function calls the database, whether the data base is abnormal or not is judged by using the packaging function, if the data base is abnormal, the corresponding exception processing is carried out on the operation function, the redundancy quantity of codes is reduced, the logic is clear, the compiling and maintaining of the codes are facilitated, and the uniqueness and the integrity of the data are ensured.
Description
Technical Field
The invention relates to the technical field of databases, in particular to a method and a device for capturing and processing database exceptions and computer equipment.
Background
In a large distributed service system, when a Redis node or a client calls an interface function to establish a connection with a Redis database, the interface function does not check the availability of the connection, and even if the connection is unavailable, a code layer can normally run. Therefore, if an exception occurs in the Redis client, the storage service of the Redis database can be unavailable, so that the operation of the service logic of the whole system is blocked. Currently, every time an interface function is called, a try/catch mechanism is used to catch exceptions, in addition to executing the code of the business logic itself. However, in a cooperative development mode, partial business logic is repeatedly executed, data superposition is caused, data uniqueness and integrity cannot be guaranteed, codes are bloated, and logic is complex.
Disclosure of Invention
The object of the present invention is to solve at least to some extent one of the above mentioned technical problems.
Therefore, the first purpose of the present invention is to provide a method for capturing and processing database exceptions, which can reduce the redundancy of codes, has clear logic, facilitates the writing and maintenance of codes, and ensures the uniqueness and integrity of data.
The second purpose of the invention is to provide a database exception capture processing device.
A third object of the invention is to propose a computer device.
A fourth object of the invention is to propose a non-transitory computer-readable storage medium.
In order to achieve the above object, an embodiment of a first aspect of the present invention provides a database exception capture processing method, where the method includes:
packaging the operation function in the database and generating a packaging function;
when the operation function calls the database, judging whether an abnormality occurs by using the encapsulation function;
and if the exception occurs, carrying out corresponding exception processing on the operation function.
Optionally, encapsulating the operation function in the database and generating an encapsulation function, including:
defining a decorator function;
decorating the operation function with a function name of the decorator function.
Optionally, defining the decorator function includes:
initializing the decorator function;
importing the function name of the operation function and the corresponding parameter thereof into the decorator function;
an exception capture operation of the decorator function is defined.
Optionally, the corresponding exception handling is performed on the operation function, and includes:
and determining an exception type, and performing corresponding exception processing on the operation function according to the exception type.
Optionally, the exception type includes at least one of a database connection exception, a data format error, a function execution error, and a database write error.
Optionally, performing corresponding exception handling on the operation function according to the exception type includes:
when the abnormal type is abnormal database connection, reestablishing connection with the database; or
When the abnormal type is a data format error, outputting an error log; or
When the exception type is a function execution error, re-executing the operation function; or
And when the abnormal type is a database write error, executing data write operation to the database again.
Optionally, after the connection with the database is reestablished, the method further includes:
the availability of the connection is detected.
The method for capturing and processing the database exception comprises the steps of packaging an operation function in a database, generating a packaging function, judging whether the operation function is abnormal or not by using the packaging function when the operation function calls the database, and if the operation function is abnormal, carrying out corresponding exception processing on the operation function, so that the code redundancy is reduced, the logic is clear, the code writing and maintenance are facilitated, and the uniqueness and the integrity of data are ensured.
In order to achieve the above object, a second aspect of the present invention provides a database exception capture processing apparatus, including:
the packaging module is used for packaging the operation function in the database and generating a packaging function;
the judging module is used for judging whether the abnormality occurs by utilizing the packaging function when the operation function calls the database;
and the exception handling module is used for carrying out corresponding exception handling on the operation function if an exception occurs.
Optionally, the encapsulation module is configured to:
defining a decorator function;
decorating the operation function with a function name of the decorator function.
Optionally, the encapsulation module is specifically configured to:
initializing the decorator function;
importing the function name of the operation function and the corresponding parameter thereof into the decorator function;
an exception capture operation of the decorator function is defined.
Optionally, the exception handling module is configured to:
and determining an exception type, and performing corresponding exception processing on the operation function according to the exception type.
Optionally, the exception type includes at least one of a database connection exception, a data format error, a function execution error, and a database write error.
Optionally, the exception handling module is specifically configured to:
when the abnormal type is abnormal database connection, reestablishing connection with the database; or
When the abnormal type is a data format error, outputting an error log; or
When the exception type is a function execution error, re-executing the operation function; or
And when the abnormal type is a database write error, executing data write operation to the database again.
Optionally, the exception handling module is further configured to:
the availability of the connection is detected.
The data base abnormity capture processing device provided by the embodiment of the invention generates the packaging function by packaging the operation function in the data base, judges whether abnormity occurs by using the packaging function when the operation function calls the data base, and performs corresponding abnormity processing on the operation function if abnormity occurs, thereby reducing the code redundancy, having clear logic, being convenient for code writing and maintenance and ensuring the uniqueness and integrity of data.
In order to achieve the above object, an embodiment of a third aspect of the present invention provides a computer device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor executes the computer program to implement the database exception capture processing method according to the embodiment of the first aspect.
In order to achieve the above object, a non-transitory computer-readable storage medium is further provided in an embodiment of a fourth aspect of the present invention, where a computer program is stored on the non-transitory computer-readable storage medium, and when executed by a processor, the computer program implements the database exception capture processing method according to the embodiment of the first aspect.
Additional aspects and advantages of the invention will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the invention.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, are included to provide a further understanding of the invention, and are incorporated in and constitute a part of this specification, illustrate exemplary embodiments of the invention and together with the description serve to explain the invention and not to limit the invention. In the drawings:
FIG. 1 is a flow diagram of a database exception capture processing method according to one embodiment of the invention;
FIG. 2 is a flow diagram of defining a decorator function according to one embodiment of the present invention;
fig. 3 is a schematic structural diagram of a database exception capture processing apparatus according to an embodiment of the present invention.
Detailed Description
It should be noted that the embodiments and features of the embodiments may be combined with each other without conflict. The present invention will be described in detail below with reference to the embodiments with reference to the attached drawings.
The present invention is described in further detail below with reference to specific examples, which are not to be construed as limiting the scope of the invention as claimed.
The following describes a database exception capture processing method, apparatus, and computer device according to an embodiment of the present invention with reference to the accompanying drawings.
Fig. 1 is a flowchart of a database exception capture processing method according to an embodiment of the present invention, as shown in fig. 1, the method includes the following steps:
s1, the operation function in the database is packaged, and a packaging function is generated.
First, a decorator function may be defined, and then an operation function may be decorated with a function name of the decorator function, thereby generating a wrapper function.
Specifically, as shown in fig. 2, defining the decorator function may further include the steps of:
s11, initializing the decorator function.
Wherein initializing the decoration function may include initializing a server address variable.
S12, the function name of the operation function and the corresponding parameter are imported into the decorator function.
S13, defining abnormal capture operation of the decorator function.
For example, a Class Redis client () may be first defined and the decorator function may be initialized. Then, a decorator function, def auto _ catch (incoming operation function name func), def wrapper () (incoming operation function parameter) is defined. Thereafter, an exception capture operation for the decorator function may be defined.
Defining an exception capture operation of a decorator function, specifically comprising the steps of:
executing the operation function circularly by utilizing try until the execution is successful, and having no exception; capturing connection abnormity by using catch, reestablishing connection with a database, and detecting connection availability by using ping (); and capturing other exceptions by using catch, and executing corresponding processing.
S2, when the operation function calls the database, the package function is used to judge whether the abnormity happens.
And judging whether the abnormity occurs by using the packaging function, namely calling the generated packaging function and executing the abnormity capturing operation defined in the decorator function.
S3, if the exception occurs, the corresponding exception handling is carried out on the operation function.
Specifically, the exception type may be determined first, and then corresponding exception handling may be performed on the operation function according to the exception type. The exception type comprises at least one of database connection exception, data format error, function execution error and database writing error.
In this embodiment, several common exception type processing methods are listed:
the first method comprises the following steps: and when the abnormal type is abnormal database connection, reestablishing the connection with the database. After re-establishing the connection with the database, the availability of the connection may be detected by ping. When not available, reconnect at intervals.
And the second method comprises the following steps: and when the exception type is a data format error, outputting an error log.
And the third is that: and when the exception type is a function execution error, re-executing the operation function.
And fourthly: and when the exception type is a database write error, executing the data write operation to the database again.
The details are described below with reference to the Redis database as an example:
redis is a key-value in-memory database, which is mainly different from other non-relational databases in that: the type of values in Redis is not limited to strings, but supports the following abstract data types: 1. a list of character strings; 2. a set of strings that are unordered and non-repeating; 3. orderly and unrepeated character string sets; 4. the key and the value are hash tables of character strings. Redis supports different unordered and ordered lists, and intersection, union and other high-level server-side atomic operations among unordered and ordered sets. In a large-scale service system, a large number of Redis interfaces are called for operation, and besides service codes of the calling interfaces, try/catch is used for capturing abnormity every time, so that the codes are bloated, and the logic is complex.
Aiming at the situation, the invention uses the decorator technology to encapsulate each operation function of Redis and monitor the operation function. The abnormal capture is automatically carried out during each data operation, corresponding processing is carried out, any business logic outside a data operation link is not influenced, business codes related to other data are not repeatedly executed due to abnormality, and data are not lost or increased. And the method is beneficial to shortening codes, saving a large amount of repeated codes, highlighting main business logic codes, and making the architecture clearer, so that cooperative research and development personnel can concentrate on business development.
The specific codes are as follows:
performing a redis native function 1 (parameter) that requires exception capture
Use of the # class
# import Module
import RedisClient
Example of class # New construction
Redisdb＝RedisClient()
# Call encapsulation function with automatic exception Capture 1
Redistb. encapsulation function 1 (parameter)
Through the mode, when the redis connection is established, the unavailability of the connection can be found in time, and the connection is reestablished. In each operation function in the redis database, automatic exception capture is realized, and corresponding processing is carried out, so that the main service logic is clear and organized, code redundancy is reduced, other service codes are prevented from being repeatedly executed, and the normal operation of a service system and the uniqueness and integrity of data are ensured.
The method for capturing and processing the database exception comprises the steps of packaging an operation function in a database, generating a packaging function, judging whether the operation function is abnormal or not by using the packaging function when the operation function calls the database, and if the operation function is abnormal, carrying out corresponding exception processing on the operation function, so that the code redundancy is reduced, the logic is clear, the code writing and maintenance are facilitated, and the uniqueness and the integrity of data are ensured.
In order to implement the above embodiment, the present invention further provides a device for capturing and processing database exceptions.
Fig. 3 is a schematic structural diagram of a database exception capture processing apparatus according to an embodiment of the present invention.
As shown in fig. 3, the apparatus includes a packaging module 31, a determining module 32, and an exception handling module 33.
And the packaging module 31 is used for packaging the operation functions in the database and generating packaging functions.
The judging module 32 is configured to judge whether an exception occurs by using the encapsulation function when the operation function calls the database.
And the exception handling module 33 is configured to, if an exception occurs, perform corresponding exception handling on the operation function.
It should be understood that the database exception capture processing apparatus in this embodiment is consistent with the description of the database exception capture processing method in the first aspect, and is not described herein again.
The data base abnormity capture processing device provided by the embodiment of the invention generates the packaging function by packaging the operation function in the data base, judges whether abnormity occurs by using the packaging function when the operation function calls the data base, and performs corresponding abnormity processing on the operation function if abnormity occurs, thereby reducing the code redundancy, having clear logic, being convenient for code writing and maintenance and ensuring the uniqueness and integrity of data.
In order to implement the above embodiments, the present invention further provides a computer device.
The computer device comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, and when the processor executes the computer program, the method for processing the database exception capture as the embodiment of the first aspect is implemented.
In order to implement the above embodiments, the present invention also provides a non-transitory computer-readable storage medium.
The non-transitory computer-readable storage medium has stored thereon a computer program, which when executed by a processor implements a database exception capture processing method as an embodiment of the first aspect.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The logic and/or steps represented in the flowcharts or otherwise described herein, e.g., an ordered listing of executable instructions that can be considered to implement logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic device) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Additionally, the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.
It should be understood that portions of the present invention may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.
It should be noted that in the description of the present specification, reference to the description of the term "one embodiment", "some embodiments", "an example", "a specific example", or "some examples", etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present invention. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.
In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.
Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention, and that variations, modifications, substitutions and alterations can be made to the above embodiments by those of ordinary skill in the art within the scope of the present invention.
Claims (16)
1. A database exception capture processing method is characterized by comprising the following steps:
packaging the operation function in the database and generating a packaging function;
when the operation function calls the database, judging whether an abnormality occurs by using the encapsulation function;
and if the exception occurs, carrying out corresponding exception processing on the operation function.
2. The method of claim 1, wherein encapsulating the operational functions in the database and generating an encapsulation function comprises:
defining a decorator function;
decorating the operation function with a function name of the decorator function.
3. The method of claim 2, wherein defining the decorator function comprises:
initializing the decorator function;
importing the function name of the operation function and the corresponding parameter thereof into the decorator function;
an exception capture operation of the decorator function is defined.
4. The method of claim 1, wherein performing corresponding exception handling on the operation function comprises:
and determining an exception type, and performing corresponding exception processing on the operation function according to the exception type.
5. The method of claim 4, wherein the exception type includes at least one of a database connection exception, a data format error, a function execution error, and a database write error.
6. The method of claim 5, wherein performing corresponding exception handling on the operation function according to the exception type comprises:
when the abnormal type is abnormal database connection, reestablishing connection with the database; or
When the abnormal type is a data format error, outputting an error log; or
When the exception type is a function execution error, re-executing the operation function; or
And when the abnormal type is a database write error, executing data write operation to the database again.
7. The method of claim 6, after reestablishing the connection with the database, further comprising:
the availability of the connection is detected.
8. A database exception capture processing apparatus, comprising:
the packaging module is used for packaging the operation function in the database and generating a packaging function;
the judging module is used for judging whether the abnormality occurs by utilizing the packaging function when the operation function calls the database;
and the exception handling module is used for carrying out corresponding exception handling on the operation function if an exception occurs.
9. The apparatus of claim 8, wherein the encapsulation module is to:
defining a decorator function;
decorating the operation function with a function name of the decorator function.
10. The apparatus of claim 9, wherein the encapsulation module is specifically configured to:
initializing the decorator function;
importing the function name of the operation function and the corresponding parameter thereof into the decorator function;
an exception capture operation of the decorator function is defined.
11. The apparatus of claim 8, wherein the exception handling module is to:
and determining an exception type, and performing corresponding exception processing on the operation function according to the exception type.
12. The apparatus of claim 11, in which the exception types comprise at least one of a database connection exception, a data format error, a function execution error, and a database write error.
13. The apparatus of claim 12, wherein the exception handling module is specifically configured to:
when the abnormal type is abnormal database connection, reestablishing connection with the database; or
When the abnormal type is a data format error, outputting an error log; or
When the exception type is a function execution error, re-executing the operation function; or
And when the abnormal type is a database write error, executing data write operation to the database again.
14. The apparatus of claim 13, wherein the exception handling module is further to:
the availability of the connection is detected.
15. A computer device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor implements the database exception capture processing method according to any one of claims 1 to 7 when executing the computer program.
16. A non-transitory computer-readable storage medium having stored thereon a computer program, wherein the computer program, when executed by a processor, implements the database exception capture processing method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910865877.XA CN112486714A (en) | 2019-09-12 | 2019-09-12 | Database exception capture processing method and device and computer equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910865877.XA CN112486714A (en) | 2019-09-12 | 2019-09-12 | Database exception capture processing method and device and computer equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112486714A true CN112486714A (en) | 2021-03-12 |
Family
ID=74920570
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910865877.XA Pending CN112486714A (en) | 2019-09-12 | 2019-09-12 | Database exception capture processing method and device and computer equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112486714A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114510398A (en) * | 2022-02-17 | 2022-05-17 | 中国农业银行股份有限公司 | Anomaly monitoring method, apparatus, device, system and medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106202535A (en) * | 2016-07-25 | 2016-12-07 | 浪潮(北京)电子信息产业有限公司 | A kind of method and system of the detection of RRD data base |
| CN107168822A (en) * | 2017-05-08 | 2017-09-15 | 山大地纬软件股份有限公司 | Oracle streams abnormal repair system and method |
| CN108845915A (en) * | 2018-07-02 | 2018-11-20 | 山东浪潮商用系统有限公司 | A kind of database data monitoring method |
| CN110187993A (en) * | 2019-05-14 | 2019-08-30 | 广州欧科信息技术股份有限公司 | A kind of processing method of misoperation, system, electronic equipment and storage medium |
-
2019
- 2019-09-12 CN CN201910865877.XA patent/CN112486714A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106202535A (en) * | 2016-07-25 | 2016-12-07 | 浪潮(北京)电子信息产业有限公司 | A kind of method and system of the detection of RRD data base |
| CN107168822A (en) * | 2017-05-08 | 2017-09-15 | 山大地纬软件股份有限公司 | Oracle streams abnormal repair system and method |
| CN108845915A (en) * | 2018-07-02 | 2018-11-20 | 山东浪潮商用系统有限公司 | A kind of database data monitoring method |
| CN110187993A (en) * | 2019-05-14 | 2019-08-30 | 广州欧科信息技术股份有限公司 | A kind of processing method of misoperation, system, electronic equipment and storage medium |
Non-Patent Citations (4)
| Title |
|---|
| BILL_XIANG_: "OpenStack公共组件oslo之九——oslo.db", Retrieved from the Internet <URL:https://blog.csdn.net/Bill_Xiang_/article/details/78592389> * |
| MICHAEL OTEY，PAUL CONTE: "《SQL Server 7 Developer\'s Guide开发人员指南》", 华南理工大学出版社, pages: 159 * |
| UREY_PP: "Django View使用装饰器捕获数据库连接异常", Retrieved from the Internet <URL:https://blog.51cto.com/dgd2010/1872599> * |
| 琴水玉: "python使用装饰器捕获异常", Retrieved from the Internet <URL:https://www.cnblogs.com/lovesqcc/p/4060277.html> * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114510398A (en) * | 2022-02-17 | 2022-05-17 | 中国农业银行股份有限公司 | Anomaly monitoring method, apparatus, device, system and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP1582985A2 (en) | Test case inheritance controlled via attributes | |
| CN108255708B (en) | Method, device, storage medium and equipment for accessing production file in test environment | |
| US6895575B2 (en) | Generic Java rule engine framework | |
| CN109933350B (en) | Method and device for embedding codes in application and electronic equipment | |
| CN110209520B (en) | Method and device for improving SSD (solid State disk) testing efficiency, computer equipment and storage medium | |
| CN109117172A (en) | A kind of method and device of the terminal versions number identification of target terminal | |
| US11909640B2 (en) | Creating endpoints | |
| CN105760196A (en) | Detection method and system for pluggable plug-in program | |
| CN111240892A (en) | Data backup method and device | |
| CN110069247A (en) | A kind of development approach and device, application method and device of application program | |
| CN107122203B (en) | Configuration file setting method and device | |
| CN112486714A (en) | Database exception capture processing method and device and computer equipment | |
| CN112579099A (en) | Code deployment method and device, storage medium and electronic equipment | |
| CN105630672A (en) | Automatic application monitoring method and device | |
| US10795650B2 (en) | Code lineage tool | |
| CN111352631A (en) | Interface compatibility detection method and device | |
| JP2004094374A (en) | Logging system | |
| US7010454B1 (en) | Test services provider | |
| CN114791884A (en) | Test environment construction method and device, storage medium and electronic equipment | |
| CN103914304A (en) | Method for converting different structure type parameters on basis of SAP (service access point) platforms | |
| CN110275710B (en) | Java local interface consistency checking method and system, storage medium and terminal | |
| CN109683994B (en) | Method and device for determining view construction time, storage medium and electronic equipment | |
| CN111367796A (en) | Application program debugging method and device | |
| US20150248453A1 (en) | Automated Logging for Object-Oriented Environments | |
| CN114168227B (en) | Program call processing method, electronic device and computer 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 | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20211012 Address after: 100193 No. 36 Building, No. 8 Hospital, Wangxi Road, Haidian District, Beijing Applicant after: Dawning Information Industry (Beijing) Co.,Ltd. Applicant after: ZHONGKE SUGON INFORMATION INDUSTRY CHENGDU Co.,Ltd. Address before: 100193 No. 36 Building, No. 8 Hospital, Wangxi Road, Haidian District, Beijing Applicant before: Dawning Information Industry (Beijing) Co.,Ltd. |