CN111008123A - Database testing method and device, storage medium and electronic equipment - Google Patents
Database testing method and device, storage medium and electronic equipment Download PDFInfo
- Publication number
- CN111008123A CN111008123A CN201911010332.7A CN201911010332A CN111008123A CN 111008123 A CN111008123 A CN 111008123A CN 201911010332 A CN201911010332 A CN 201911010332A CN 111008123 A CN111008123 A CN 111008123A
- Authority
- CN
- China
- Prior art keywords
- log
- operation log
- type
- database
- preset
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 57
- 238000000034 method Methods 0.000 claims abstract description 26
- 230000015654 memory Effects 0.000 claims description 20
- 230000002159 abnormal effect Effects 0.000 abstract description 20
- 239000002699 waste material Substances 0.000 abstract description 8
- 230000001360 synchronised effect Effects 0.000 abstract description 4
- 238000005516 engineering process Methods 0.000 abstract description 2
- 238000010586 diagram Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 6
- 230000008569 process Effects 0.000 description 6
- 230000008859 change Effects 0.000 description 4
- 238000003780 insertion Methods 0.000 description 4
- 230000037431 insertion Effects 0.000 description 4
- 230000005856 abnormality Effects 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000004590 computer program Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000007599 discharging Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012552 review Methods 0.000 description 1
- 239000007787 solid Substances 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/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- 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/21—Design, administration or maintenance of databases
- G06F16/219—Managing data history or versioning
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application discloses a database testing method, a database testing device, a storage medium and electronic equipment, and relates to a database testing technology. The specific scheme comprises the following steps: obtaining at least one operation log aiming at least one database request; determining the operation type of each operation log; if so, taking the operation log as a first operation log, determining a target operation log according to the first operation log, and judging whether the target operation log contains a preset second operation type; if so, determining the operation log with the operation type being a preset second operation type as a second operation log, and judging whether the data table information contained in the second operation log and the first operation log is the same; and if so, marking the first operation log and the second operation log as risk operations. According to the method and the device, the abnormal service test of the database caused by the synchronous delay problem of the master database and the slave database can be realized by using the single database deployment mode, so that the resource waste is avoided while the test comprehensiveness is improved.
Description
Technical Field
The present disclosure relates to database testing technologies, and in particular, to a database testing method, an apparatus, a storage medium, and an electronic device.
Background
At present, a Master-Slave database (Master-Slave) deployment mode is mostly adopted for a database: wherein, the Master library (Master) is used for changing the stored data; the Slave library (Slave) is used as a backup of the master library and is also used for carrying out query operation of stored data. However, the master-slave database has a drawback in that the synchronization delay of data stored between the master database and the slave database is problematic, and for example, if a query operation is performed on the slave database within a short time after a change operation is performed on the master database, there is a possibility that the database service of the master-slave database is abnormal due to the synchronization delay of data stored between the master database and the slave database. In order to avoid the abnormal database service of the master database and the slave database, the master database and the slave database need to be tested, so that the abnormal condition is avoided in advance.
In the database testing method in the prior art, in order to reduce the testing cost and avoid resource waste, a single database deployment mode is usually adopted. In the prior art, a single database deployment mode cannot test database service abnormity caused by synchronization delay of a master database and a slave database, and the databases used for testing are deployed as the master database and the slave database, so that excessive resource waste is caused.
Disclosure of Invention
In view of this, a main object of the present application is to provide a database testing method, which can use a single database deployment manner to implement a test on abnormal database services caused by a synchronization delay problem of a master database and a slave database, thereby improving test comprehensiveness and avoiding resource waste.
In order to achieve the purpose, the technical scheme provided by the application is as follows:
in a first aspect, an embodiment of the present application provides a database testing method, including the following steps:
obtaining at least one operation log aiming at least one database request;
determining the operation type of each operation log;
when the operation type is a preset first operation type, taking the operation logs as first operation logs, determining a continuous preset number of operation logs taking the first operation logs as a starting point as target operation logs, and judging whether the operation type of the target operation logs contains a preset second operation type or not;
when the preset second operation type is included, determining an operation log with the operation type being the preset second operation type as a second operation log, and judging whether the data table information contained in the second operation log and the first operation log is the same or not;
when the included data table information is the same, marking the first operation log and the second operation log as risk operations.
In one possible embodiment, the step of obtaining at least one operation log for at least one database request includes:
and acquiring at least one operation log aiming at least one database request according to the identification information of the operation log.
In one possible embodiment, the step of obtaining at least one operation log for at least one database request includes:
and acquiring at least one operation log aiming at least one database request according to the time information of the operation logs.
In a possible implementation manner, the step of determining, for each of the operation logs, an operation type of the operation log includes:
dividing the operation log into at least one character string according to a preset separator;
acquiring an operation type character string from the at least one character string obtained by dividing;
and determining the operation type of the operation log according to the operation type character string.
In one possible embodiment, the data table information is determined according to the following steps:
and determining the data table information of the operation log according to the operation type character string.
In a possible implementation manner, the step of obtaining an operation type string from the at least one string obtained by dividing includes:
and acquiring the operation type character string from the at least one character string obtained by dividing according to the position of the operation type character string in the operation log.
In a possible implementation manner, before the step of obtaining the operation type string from the at least one string obtained by dividing, the method further includes:
obtaining a log type character string from the at least one character string obtained by dividing;
judging whether the operation log is of a preset log type or not according to the log type character string;
and when the operation log is of a preset log type, executing a step of acquiring an operation type character string from the at least one character string obtained by dividing.
In a second aspect, an embodiment of the present application further provides a database testing apparatus, including:
the log acquisition module is used for acquiring at least one operation log aiming at least one database request;
the type determining module is used for determining the operation type of each operation log;
a risk operation determining module, configured to, when the operation type is a preset first operation type, use the operation log as a first operation log, determine, as a target operation log, a preset number of continuous operation logs starting from the first operation log, and determine whether an operation type of the target operation log includes a preset second operation type; the operation log is used for determining the operation log with the operation type of the preset second operation type as a second operation log when the preset second operation type is included, and judging whether the data table information contained in the second operation log and the first operation log is the same or not; and the processor is further configured to mark the first oplog and the second oplog as risky operations when the included data table information is the same.
In a third aspect, an embodiment of the present application further provides a computer-readable storage medium. The specific scheme is as follows:
a computer readable storage medium storing computer instructions which, when executed by a processor, may implement the steps of any one of the possible embodiments of the first aspect and the first aspect.
In a fourth aspect, an embodiment of the present application further provides an electronic device. The specific scheme is as follows:
an electronic device, comprising:
a processor;
a memory for storing the processor-executable instructions;
the processor is configured to read the executable instructions from the memory and execute the instructions to implement the steps of any one of the possible implementations of the first aspect and the first aspect.
In summary, the present application provides a database testing method, an apparatus, a storage medium, and an electronic device. According to the method and the device, a single database deployment mode is used for database testing, and operation logs formed in the database testing process are analyzed. After it is determined that an operation of a preset first operation type is performed on the master library according to the operation log, it is necessary to verify whether the operation is performed on the slave library in a short time. Therefore, the operation log is used as a first operation log, a continuous preset number of operation logs starting from the first operation log are determined as a target operation log, whether a preset second operation type for operating the slave library exists in the target operation log or not is judged, if yes, the operation of the master library and the slave library in a short time occurs, and abnormal database service caused by the problem of synchronization delay of data stored between the master library and the slave library easily occurs. By utilizing the technical means, the abnormal service test of the database caused by the synchronous delay problem of the master database and the slave database can be realized by using the deployment mode of the single database, so that the test comprehensiveness is improved, and meanwhile, the resource waste is avoided.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive labor.
Fig. 1 is a schematic flowchart of a database testing method according to an embodiment of the present disclosure;
FIG. 2 is a schematic flow chart illustrating another database testing method according to an embodiment of the present disclosure;
fig. 3 is a schematic flowchart illustrating operation type determination in a database testing method according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of a database testing apparatus according to an embodiment of the present disclosure;
fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims of the present application and in the drawings described above, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are, for example, capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprising" and "having," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements explicitly listed, but may include other steps or elements not explicitly listed or inherent to such process, method, article, or apparatus.
At present, a database mostly adopts a deployment mode of a master database and a slave database: the general master library is used for changing operations of stored data, such as operations of inserting, updating, deleting and the like on the stored data; the slave library is a backup of the master library and is typically used for query operations to store data. In the master-slave database, if the operation on the master database and the slave database is executed in the request for accessing the database once, because the time interval between the operation on the master database and the operation on the slave database is short, if the synchronization delay problem is caused by various factors, the slave database may not synchronize the stored data of the master database in time, thereby causing the abnormal operation of the query database and further causing the abnormal service of the database. In order to avoid the abnormality of the master database and the slave database, the master database and the slave database are comprehensively tested, and it is very important to avoid the occurrence of the abnormal condition in advance.
In the prior art, a database testing method generally does not adopt a deployment mode of a master database and a slave database, but adopts a deployment mode of a single database. In one aspect, the purpose of the deployment mode of the master database and the slave database is to backup the stored data, so as to prevent the stored data from being damaged or lost, data backup is not necessary in a test environment, and resource waste is caused when the master database and the slave database are used in the test environment. And secondly, the occurrence of the synchronization delay problem has more influence factors, such as network jitter and hardware performance, which all influence whether and when the synchronization delay problem occurs, and even if the master database and the slave database are deployed in the test environment, the consistency with the actual use environment cannot be ensured, the online environment cannot be truly simulated, and thus the master database and the slave database cannot be truly tested comprehensively.
Once the synchronization delay problem occurs in practical applications, it generally causes a relatively serious failure. In order to avoid database service abnormality caused by synchronization delay problem of a master database and a slave database in an actual application environment as much as possible, the synchronization delay problem needs to be exposed in a test environment, so that the occurrence of the abnormal condition is avoided in advance.
In view of this, the core invention of the present application is: and performing database test by using a single database deployment mode, and analyzing an operation log formed in the database test process. After it is determined that an operation of a preset first operation type is performed on the master library according to the operation log, it is necessary to verify whether the operation is performed on the slave library in a short time. Therefore, the operation log is used as a first operation log, a continuous preset number of operation logs starting from the first operation log are determined as a target operation log, whether a preset second operation type for operating the slave library exists in the target operation log or not is judged, if yes, the operation of the master library and the slave library in a short time occurs, and abnormal database service caused by the problem of synchronization delay of data stored between the master library and the slave library easily occurs. The operation log of the database service abnormity which is easy to occur due to the synchronization delay problem is marked as the risk operation, test data for analyzing the delay synchronization problem can be provided for a tester, and whether the delay synchronization problem is caused by the risk operation or not can be tracked and confirmed. By utilizing the technical means, the abnormal service test of the database caused by the synchronous delay problem of the master database and the slave database can be realized by using the deployment mode of the single database, so that the test comprehensiveness is improved, the test efficiency is improved, and the resource waste is avoided.
In order to make the objects, technical solutions and advantages of the present invention clearer, the technical solutions of the present invention are described in detail below with specific embodiments. Several of the following embodiments may be combined with each other and some details of the same or similar concepts or processes may not be repeated in some embodiments.
Example one
Fig. 1 is a schematic flow chart of a database testing method provided in an embodiment of the present application, and as shown in fig. 1, the embodiment mainly includes:
s101: at least one oplog for at least one database request is obtained.
The database request is an operation request for the database, one database request calls one database interface, and at least one operation for the database can be performed in one database request. Since the time interval between two database requests is usually sufficient for the synchronization of stored data between the master library and the slave library, the embodiment of the present application preferably analyzes a plurality of database operations requested in one database request.
When a database is tested, an operation log is generated each time a database request is received, specifically, one operation log is generated for each operation on the database, and at least one operation on the database can be performed in one database request, so that at least one operation log can be generated for one database request.
S102: and determining the operation type of each operation log.
One operation log corresponds to one operation on the database, and the operation type of the operation log is information of the kind of the operation performed on the data, for example, the operation type may include: the operation type of the operation log is an insertion type, and the operation type represents that the operation performed on the database is an insertion operation of storing data.
S103: and when the operation type is a preset first operation type, taking the operation log as a first operation log, determining a continuous preset number of operation logs with the first operation log as a starting point as a target operation log, and judging whether the operation type of the target operation log contains a preset second operation type.
Here, the preset first operation type is an operation type for operating the master library, and when the operation type of the operation log is the preset first operation type, the operation for generating the first operation log is performed on the master library. Therefore, the preset first operation type is set in advance according to the operation that can be performed on the master library. In general, the master library is used for a change operation of the stored data, for example, an operation such as an insertion, an update, or a deletion is performed on the stored data, and therefore, the first operation type is preset as a change operation, for example, an operation such as an insertion, an update, or a deletion is performed on the stored data.
The preset second operation type is an operation type for operating the slave library, and when the operation type of the operation log is the preset second operation type, the operation for generating the second operation log is performed on the slave library. Therefore, the preset second operation type is set in advance according to the operation that can be performed on the slave library. Typically, the slave library is used for a query operation to store data, and therefore, the second operation type is preset as a query operation.
When the interval time between the operation performed on the master library and the operation performed on the slave library is short, there is a risk that a database service abnormality occurs due to a synchronization delay problem, and therefore, when the operation type of the operation log is a preset first operation type, it is verified that the operation performed on the master library at the time of generating the first operation log is performed, and it is necessary to determine whether the operation performed on the slave library is performed within a short time range from the operation of generating the operation log. Since each operation log generated by one database request is arranged according to the sequence of the operations on the database, it is necessary to determine whether a preset second operation type is included in a preset number of operation logs subsequent to the operation log. Specifically, the operation log is used as a first operation log, a preset number of continuous operation logs starting from the first operation log are determined as a target operation log, and whether a preset second operation type is included in operation types of the target operation log is judged.
S104: and when the preset second operation type is included, determining the operation log with the operation type being the preset second operation type as a second operation log, and judging whether the data table information contained in the second operation log and the first operation log is the same or not.
When the preset second operation type is included, the operation of the slave library is proved to occur, and the operation log of which the operation type is the preset second operation type is determined as the second operation log. The operation of the slave library occurs only after the operation of the master library, and the database service is not necessarily abnormal due to the synchronization delay problem. If the operation on the master library and the operation on the slave library are directed to different data tables, the stored data changed during the operation on the master library does not affect the operation on the slave library. Therefore, whether the data table information included in the second operation log is the same as the data table information included in the first operation log is judged, if the same data table information is included in the second operation log and the first operation log, it is proved that the operation for generating the second operation log and the operation for generating the first operation log are operations for the same data table, that is, the operation for the slave library and the operation for the master library are for the same data table, when the operation for the master library and the operation for the slave library occur at short intervals, and when the same data table is targeted, there is a high probability that the database service is abnormal due to the synchronization delay problem. Here, a data table is a unit for storing data in a database, the database generally stores data in the form of a table, and with the increasing scale of data that can be stored in the database, the data table is generally used for hierarchical management of stored data, and one database generally includes at least one data table. The operation log generated by one operation contains the information of the data table in which the storage data corresponding to the operation is stored, so that the data table corresponding to the operation of the database can be determined according to the data table information contained in the operation log.
S105: when the included data table information is the same, marking the first operation log and the second operation log as risk operations.
When the contained data table information is the same, the operation on the master library and the operation on the slave library are performed on the same data table in a short time, and the database service is abnormal due to the synchronization delay problem with a high probability, so that the first operation log and the second operation log are both marked as risk operations. The risk operation refers to a database operation with the possibility of abnormal database service due to synchronization delay problem. In an actual application environment, the synchronization delay problem of the database is greatly uncertain due to factors such as network states, hardware performance and the like, so that the operation on the master library and the operation on the slave library are performed aiming at the same data table in a short time, the database service abnormity is not necessarily caused by the synchronization delay problem, and the database service abnormity is caused only with a high probability, therefore, the first operation log and the second operation log are only required to be marked as risk operations, so that a tester can further analyze the risk operations to determine whether the synchronization delay problem occurs and the database service abnormity is caused.
By utilizing the technical means, the abnormal service test of the database caused by the synchronous delay problem of the master database and the slave database can be realized by using the deployment mode of the single database, so that the test comprehensiveness is improved, the test efficiency is improved, and the resource waste is avoided.
Example two
As shown in fig. 2, an embodiment of the present application further provides another database testing method, including:
s201: at least one oplog for at least one database request is obtained.
When a database is tested, an operation log is generated each time a database request is received, specifically, one operation log is generated for each operation on the database, and at least one operation on the database can be performed in one database request, so that at least one operation log can be generated for one database request. Illustratively, a segment of the oplog is as follows:
2019-07-03 20:16:41|[INFO]|db-listen|{“sql”:“select*from`agent_pages`where`agent_pages`……”}|{“memory_usage”:“16MB”,“process_id”：6869，“log_id”:“XXXXXXX”,……}
the operation log usually includes time information of the operation log, a log type of the operation log, an operation type of the operation log, detailed information of an operation for generating the operation log, identification information of the operation log, and the like. According to the information contained in the operation log, the following two possible embodiments can be adopted to obtain at least one operation log for at least one database request.
A: in one possible implementation, at least one operation log for at least one database request is obtained according to the identification information of the operation log. The operation log usually carries identification information of the database request, and the database requests for generating the operation log can be distinguished according to the identification information of the operation log. Illustratively, in the above-mentioned section of the operation log, the identification information of the operation log is "log _ id": xxxxxx ", and the content of the identification information of the operation log generated by the same database request is the same.
B: in another possible implementation, at least one operation log for at least one database request is obtained according to the time information of the operation log. In actual operation, the identification information of the operation log may not be included in the operation log, and at this time, the time information of the operation log may be obtained, for example, in the above section of operation log, the time information of the operation log is "2019-07-0320: 16: 41". Because each operation log requested by the same database has the same time information and the time information of the operation logs requested by different databases is different, at least one operation log for at least one database request can be acquired according to the time information of the operation logs.
S202: and determining the operation type of each operation log.
Specifically, the step of determining the operation type of one operation log is shown in fig. 3, and the step shown in fig. 3 is repeated for each operation log to determine the operation type of each operation log.
S301: and dividing the operation log into at least one character string according to a preset separator.
Here, the preset delimiter is related to the syntax of the operation log. Specifically, in order to clearly distinguish each field in the operation log, a preset separator is set in the general operation log, and the operation log may be divided into at least one character string according to the preset separator, where each character string generally represents one type of log information. And the preset separator is specially set and can not be repeated with the characters in the character strings obtained by division, and the operation log can be uniquely and accurately divided according to the preset separator to obtain at least one character string. Illustratively, in the above-mentioned section of operation log, the preset separator is "l", and the operation log may be divided according to the preset separator "l", to obtain 5 character strings, which are "2019-07-0320: 16: 41", "[ INFO ]", "db-list", "{" sql ": select from" agent _ pages "where" agent _ pages "… …" } "and" { "memory _ use": 16MB "and process _ id": 6869, "log _ id": XXXXXXX ", … … }". Each string is a type of log information, for example, the string "2019-07-0320: 16: 41" is time information of the operation log.
S302: and acquiring an operation type character string from the at least one character string obtained by dividing.
One of the divided character strings includes one kind of information in the operation log, and therefore, in order to obtain the operation type of the operation log, it is necessary to acquire a character string including information of the operation type, and the character string including information of the operation type of the operation log is an operation type character string.
When the operation log is generated, a certain syntax needs to be followed, and therefore, the operation type character string is acquired according to the syntax of the operation log.
In one possible embodiment, the operation log is generated according to a fixed information arrangement order, for example, when the operation log is generated, the time information is necessarily the first group of information of the operation log, and therefore the time information is necessarily included in the first character string obtained by dividing the operation log. For example, the operation type string is generally the fourth set of information of the operation log, and therefore, the operation type string may be obtained from the at least one string obtained by dividing according to the position of the operation type string in the operation log. Specifically, the operation type string may be included in a fourth string obtained by dividing the operation log. Illustratively, in the above-mentioned section of the operation log, the operation type string is "{" sql ": select from 'agent _ pages' where 'agent _ pages' … …" } ".
In another possible implementation, the operation log may not be generated according to a fixed information arrangement order. At this time, character matching may be performed from each of the character strings obtained by dividing the operation log according to the syntax of the operation type character string. Specifically, according to the grammar of the operation type character string, a preset operation type character in the operation type character string is determined, and according to the preset operation type character, character matching is performed on each character string obtained by dividing the operation log, so that the operation type character string is obtained. For example, in the above-mentioned section of the operation log, according to the syntax of the operation type character string, a preset operation type character in the operation type character string may be determined. In the exemplary operation log, the syntax of the operation type string is that the operation type is declared using "sql", and therefore, the operation type string is character-matched according to "sql" on the 5 character strings obtained by dividing the operation log, with "sql" as the preset operation type character. And determining the character string containing the preset operation type character in at least one character string obtained by dividing as an operation type character string. The 5 character strings contain a preset operation type character "sql", the character string is "{" sql "", "select from 'agent _ pages' where 'agent _ pages' … …" } ", and the operation type character string is" { "sql" ", and" select from 'agent _ pages' where 'agent _ pages' … … "}".
In a specific implementation, more than two log types of operation logs may be recorded in one file for recording the operation logs. Here, the log type is type information of the operation log, the log types of different operation logs may record information of different types and contents of the same operation on the database, and the log types of different operation logs may also record information of operations on the same database by different information demanders. Therefore, before the operation type character string is obtained, the log types can be filtered, and the operation types required by the embodiment of the application can be recorded in the operation log of the preset log type.
When the log type is distinguished in the operation log, the information of the log type is also contained in at least one character string obtained by dividing the operation log. And dividing the operation log into at least one character string, wherein the character string containing the log type information of the operation log is a log type character string. The determination of the log-type string may also include two possible implementations.
In a possible embodiment, the operation log is generated according to a fixed information arrangement order, and at this time, the log type character string is obtained from the at least one character string obtained by dividing according to the position of the log type character string in the operation log. Illustratively, in the above-mentioned section of the operation log, the log-type character string is usually the third set of information of the operation log, that is, the log-type character string is included in the third character string obtained by dividing the operation log, and the log-type character string is "db-list". And judging whether the operation log is of a preset log type or not according to the log type character string, specifically, comparing the character content of the acquired log type character string with the character content of the log type to be acquired, and when the character content of the acquired log type character string is consistent with the character content of the log type to be acquired, judging that the operation log is of the preset log type. And when the operation log is of a preset log type, executing a step of acquiring an operation type character string from the at least one character string obtained by dividing.
In another possible implementation, the operation log may not be generated according to a fixed information arrangement order. At this time, character matching may be performed from each of the character strings obtained by dividing the operation log according to the syntax of the log-type character string. For the log type character string, the log type character string can be obtained by directly performing character matching on each character string obtained by dividing the operation log according to the character content of the log type. Illustratively, in the above-mentioned section of operation log, an operation log whose log type is monitored by the database needs to be obtained, the character content of the log type is "db-list", and according to the character content of the log type, character matching is performed on 5 character strings obtained by dividing the operation log, so as to obtain a log type character string "db-list". At this time, judging whether the operation log is of a preset log type according to the log type character string, specifically, if the log type character string can be obtained from the operation log according to the character content of the log type, the operation log is of the preset log type; otherwise, the operation log is not the preset log type. And when the operation log is of a preset log type, executing a step of acquiring an operation type character string from the at least one character string obtained by dividing.
S303: and determining the operation type of the operation log according to the operation type character string.
Specifically, the operation type of the operation log is determined according to the grammar of the operation type character string. Illustratively, in the above-mentioned section of the operation log, the syntax of the operation type string is that the operation type of the operation log is declared using "sql", and therefore, the character immediately following "sql" in the operation type string is the operation type of the operation log. Since the operation type string is "{" sql ":" select from 'agent _ pages' … … "}", and the character immediately following "sql" in the operation type string is select, the operation type of the operation log is thus select, and the operation type of the operation log can be determined as a query operation on the database according to the syntax of the operation type string.
S203: and when the operation type is a preset first operation type, taking the operation log as a first operation log, and determining a continuous preset number of operation logs with the first operation log as a starting point as a target operation log.
Here, the first operation type is preset as an operation of changing the storage data of the master library. According to the database operation method provided by the embodiment of the application, the risk operation is that the operation of changing the stored data and presetting the first operation type is executed on the master library, and then the operation of inquiring the stored data and presetting the second operation type is executed on the slave library. Therefore, each operation log is analyzed in sequence, whether the operation type of the current operation log is the preset first operation type or not is judged, and when the operation type of the current operation log is the preset first operation type, the operation of generating the current operation log can be determined as the change of the stored data of the master library, and the operation log is used as the first operation log. In this case, it is necessary to determine whether or not the stored data in the slave library is queried in a short time. Each operation log generated by one database request is arranged according to the sequence of the operation on the database, so that a continuous preset number of operation logs with a first operation log as the start are obtained first, and the continuous preset number of operation logs with the first operation log as the start are determined as target operation logs.
If each operation log generated by the database request does not have a first operation log with the operation type being a preset first operation type, the database request does not have risk operation, and the step of determining a continuous preset number of operation logs starting from the first operation log as a target operation log and subsequent steps are not needed. But returning to step S201 to continuously obtain at least one operation log for the next database request, and continuously analyzing whether a first operation log with an operation type being a preset first operation type exists in the at least one operation log generated by the next database request.
Further, each operation log generated by one database request is arranged according to the sequence of the operations on the database, and the more operation logs are spaced between the operation log generated by the operation on the master library and the operation log generated by the operation on the slave library, the longer the time interval between the operation on the master library and the operation on the slave library, and vice versa. Therefore, the time interval between the operation of the master library and the operation of the slave library at the time of performing the test can be controlled by the preset number. When the synchronization speed between the master bank and the slave bank is considered to be fast, the value of the preset number may be set to be small, for example, the preset number is set to be between 1 and 5. When the synchronization speed between the master bank and the slave bank is considered to be slow, the value of the preset number may be set to be large, for example, the preset number is set to be between 5 and 10. Of course, since the execution time of one database request is usually short, each operation log after the first operation log in the same database request may also be determined as the target operation log.
S204: and judging whether the operation types of the target operation log contain a preset second operation type.
When at least one operation log generated by one database request has a first operation log with an operation type of a preset first operation type, the operation of changing the stored data of the master library is executed in the one database request, and then whether the operation of inquiring the stored data of the slave library is executed in the same database request after the operation of generating the first operation log is needed to be judged. Namely, whether the operation type of the target operation log contains the preset second operation type is judged. Here, the second operation type is preset as an operation performed on the storage data of the slave library.
When the preset second operation type is included, executing step S205; and when the preset second operation type is not included, the database request has no risk operation, and the step of determining the data table information of the operation log and the subsequent steps thereof according to the operation type character string are not required. But returning to step S201 to continue to obtain at least one operation log for the next database request, and analyzing whether a first operation log with an operation type being a preset first operation type exists in the at least one operation log generated by the next database request.
S205: and when the preset second operation type is included, determining the operation log with the operation type being the preset second operation type as the second operation log, and determining the data table information of the operation log according to the operation type character string.
Specifically, when the preset second operation type is included, the operation log of which the operation type is the preset second operation type is determined as the second operation log. Before the step of determining whether the data table information contained in the second operation log is the same as the data table information contained in the first operation log, the step of determining the data table information in the second operation log and the data table information in the first operation log, that is, the step of determining the data table information in the operation log, is needed. Specifically, the data table information in the operation log is generally included in the operation type string according to the syntax of the operation log, and thus the data table information of the operation log can be determined according to the operation type string. Illustratively, in the above-mentioned section of operation log, the operation type string obtained is determined as "{" sql ": select from agent pages 'where agent pages' … …" } ". According to the syntax of the operation log, the data table information for the operation of generating the operation log is declared by using the from key, so in the above example, the data table information for the operation of generating the operation log is 'agent _ pages', here, the data table information is the table name of the data table, and in other possible embodiments, the data table information may also be the table identifier, the label, and the like of the data table.
S206: and judging whether the data table information contained in the second operation log and the first operation log is the same or not.
And sequentially judging whether the second operation log and the first operation log contain the same data table information or not aiming at each second operation log in the target operation log. Whether the second operation log contains the same data table information as the first operation log or not represents that the operation for generating the second operation log and the operation for generating the first operation log are directed to the same data table, and there is a high probability that the database service is abnormal due to the synchronization delay problem.
When the included data table information is the same, step S207 is executed; and when the included data table information is different, returning to step S201 to continuously obtain at least one operation log for the next database request, and analyzing whether a first operation log with an operation type being a preset first operation type exists in the at least one operation log generated by the next database request.
S207: when the included data table information is the same, marking the first operation log and the second operation log as risk operations.
In addition to marking the first operation log as a risk operation, specifically, for each second operation log in the target operation log, it is sequentially determined whether the second operation log and the first operation log contain the same data table information, and the second operation log that contains the same data table information as the first operation log is marked as a risk operation.
In order to provide information as complete as possible to a tester, facilitate the tester to locate faults and eliminate hidden dangers as possible, when the included data table information is the same, both the first operation log and the target operation log can be marked as risk operations.
After marking the first oplog and the second oplog as risky operations, or marking both the first oplog and the target oplog as risky operations, a file may be generated, and each oplog marked as risky operations may be output to the file for storage, later review, and further analysis.
Further, identification information or time information of each operation log marked as a risky operation may also be acquired. When more than two operation log files are generated for the operation of the database, the operation logs which can be marked as risk operations in each operation log file are obtained according to the identification information or the time information of the operation logs marked as risk operations, so that more comprehensive test data are provided for testers. For example, in a specific implementation, a request operation on a database may generate a plurality of different types of operation logs, such as an interface request log, an Nginx log, and a Structured Query Language (SQL) log, and record different request information. At this time, each operation log that can be marked as a risk operation may be obtained from the interface request log, the Nginx log, and the SQL log according to the identification information or the time information of the operation log marked as a risk operation, and a result file may be generated. And the tester can position whether the risk operation has the synchronization delay problem or not according to the result file and causes abnormal database service.
Based on the same design concept, the embodiment of the application also provides a database testing device, a storage medium and electronic equipment.
EXAMPLE III
As shown in fig. 4, an embodiment of the present application further provides a database testing apparatus 400, including:
a log obtaining module 401, configured to obtain at least one operation log for at least one database request;
a type determining module 402, configured to determine, for each operation log, an operation type of the operation log;
a risk operation determining module 403, configured to, when the operation type is a preset first operation type, use the operation log as a first operation log, determine a preset number of continuous operation logs starting from the first operation log as a target operation log, and determine whether an operation type of the target operation log includes a preset second operation type; the operation log is used for determining the operation log with the operation type of the preset second operation type as a second operation log when the preset second operation type is included, and judging whether the data table information contained in the second operation log and the first operation log is the same or not; and the processor is further configured to mark the first oplog and the second oplog as risky operations when the included data table information is the same.
In a possible implementation, the log obtaining module 401 is further configured to:
and acquiring at least one operation log aiming at least one database request according to the identification information of the operation log.
In a possible implementation, the log obtaining module 401 is further configured to:
and acquiring at least one operation log aiming at least one database request according to the time information of the operation logs.
In a possible implementation, the type determining module 402 is further configured to:
dividing the operation log into at least one character string according to a preset separator;
acquiring an operation type character string from the at least one character string obtained by dividing;
and determining the operation type of the operation log according to the operation type character string.
In one possible embodiment, the database testing apparatus 400 further includes: a data table determination module 404 configured to:
and determining the data table information of the operation log according to the operation type character string.
In a possible implementation, the type determining module 402 is further configured to:
and acquiring the operation type character string from the at least one character string obtained by dividing according to the position of the operation type character string in the operation log.
In a possible implementation, the type determining module 402 is further configured to:
obtaining a log type character string from the at least one character string obtained by dividing;
judging whether the operation log is of a preset log type or not according to the log type character string;
and when the operation log is of a preset log type, executing a step of acquiring an operation type character string from the at least one character string obtained by dividing.
Example four
A computer readable storage medium storing instructions that, when executed by a processor, cause the processor to perform the steps of any one of the database testing methods provided by embodiments of the present application. In practical applications, the computer readable medium may be included in the apparatus/device/system described in the above embodiments, or may exist alone without being assembled into the apparatus/device/system. The computer readable storage medium carries one or more programs which, when executed, implement the steps of performing any of the database testing methods provided by the embodiments of the present application according to any of the database testing apparatuses provided by the embodiments of the present application with reference to the embodiments of the present application.
According to embodiments disclosed herein, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example and without limitation: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing, without limiting the scope of the present disclosure. In the embodiments disclosed herein, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The method steps described herein may be implemented in hardware, for example, logic gates, switches, Application Specific Integrated Circuits (ASICs), programmable logic controllers, embedded microcontrollers, etc., in addition to data processing programs. Such hardware capable of implementing the methods described herein may also constitute the present application.
EXAMPLE five
The embodiment of the present application further provides an electronic device, which may be a computer or a server, and any one of the database testing apparatuses provided in the embodiments of the present application may be integrated therein. As shown in fig. 5, an electronic device 500 provided by the embodiment of the present application is shown.
The electronic device may include one or more processors 501 of a processing core, one or more memories 502 for storing instructions executable by the processors 501. The electronic device may further include a power supply 503, an input-output unit 504. Those skilled in the art will appreciate that fig. 5 is not limiting of electronic devices and may include more or fewer components than shown, or some components may be combined, or a different arrangement of components.
Wherein:
the processor 501 is a control part of the electronic device, and is connected to various parts by using various interfaces and lines, reads the executable instructions from the memory 502, and executes or executes the instructions stored in the memory 502 to implement any of the steps of the database testing method provided by the embodiments of the present application.
The memory 502 may be used to store software programs, i.e., programs involved in any of the database testing methods provided by the embodiments of the present application.
The processor 501 executes various functional applications and data processing by executing software programs stored in the memory 502. The memory 502 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function, and the like; the storage data area may store data or the like used according to the needs of the electronic device. Further, the memory 502 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device. Accordingly, the memory 502 may also include a memory controller to provide the processor 501 with access to the memory 502.
The electronic device further comprises a power supply 503 for supplying power to each component, and preferably, the power supply 503 may be logically connected to the processor 501 through a power management system, so that functions of managing charging, discharging, power consumption, and the like are realized through the power management system. The power supply 503 may also include any component of one or more dc or ac power sources, recharging systems, power failure detection circuitry, power converters or inverters, power status indicators, and the like.
The server may also include an input-output unit 504, such as may be used to receive entered numeric or character information, and to generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control; such as various graphical user interfaces that may be used to display information entered by or provided to the user, as well as the server, which may be composed of graphics, text, icons, video, and any combination thereof.
Any database testing method, device, storage medium and electronic equipment provided by the embodiments of the present application are based on the same design concept, and the technical means in any embodiment of the present application can be freely combined, and the combined technical means is still within the protection scope of the present application.
The flowchart and block diagrams in the figures of the present application illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments disclosed herein. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
It will be appreciated by a person skilled in the art that various combinations and/or combinations of features described in the various embodiments and/or claims of the present application are possible, even if such combinations or combinations are not explicitly described in the present application. In particular, the features recited in the various embodiments and/or claims of the present application may be combined and/or coupled in various ways, all of which fall within the scope of the present disclosure, without departing from the spirit and teachings of the present application.
The principle and implementation of the present application are explained by applying specific embodiments in the present application, and the above description of the embodiments is only used to help understanding the method and the core idea of the present application, and is not used to limit the present application. It will be appreciated by those skilled in the art that changes may be made in this embodiment and its broader aspects and without departing from the principles, spirit and scope of the invention, and that all such modifications, equivalents, improvements and equivalents as may be included within the scope of the invention are intended to be protected by the claims.
Claims (10)
1. A method for testing a database, comprising:
obtaining at least one operation log aiming at least one database request;
determining the operation type of each operation log;
when the operation type is a preset first operation type, taking the operation logs as first operation logs, determining a continuous preset number of operation logs taking the first operation logs as a starting point as target operation logs, and judging whether the operation type of the target operation logs contains a preset second operation type or not;
when the preset second operation type is included, determining an operation log with the operation type being the preset second operation type as a second operation log, and judging whether the data table information contained in the second operation log and the first operation log is the same or not;
when the included data table information is the same, marking the first operation log and the second operation log as risk operations.
2. The method of claim 1, wherein the step of obtaining at least one oplog for at least one database request comprises:
and acquiring at least one operation log aiming at least one database request according to the identification information of the operation log.
3. The method of claim 1, wherein the step of obtaining at least one oplog for at least one database request comprises:
and acquiring at least one operation log aiming at least one database request according to the time information of the operation logs.
4. The method of claim 1, wherein the step of determining, for each of the oplogs, an operation type of the oplog comprises:
dividing the operation log into at least one character string according to a preset separator;
acquiring an operation type character string from the at least one character string obtained by dividing;
and determining the operation type of the operation log according to the operation type character string.
5. The method of claim 4, wherein the data table information is determined according to the following steps:
and determining the data table information of the operation log according to the operation type character string.
6. The method according to claim 4, wherein the step of obtaining the operation type string from the at least one string obtained by dividing comprises:
and acquiring the operation type character string from the at least one character string obtained by dividing according to the position of the operation type character string in the operation log.
7. The method according to claim 4, wherein before the step of obtaining the operation type string from the at least one string obtained by dividing, the method further comprises:
obtaining a log type character string from the at least one character string obtained by dividing;
judging whether the operation log is of a preset log type or not according to the log type character string;
and when the operation log is of a preset log type, executing a step of acquiring an operation type character string from the at least one character string obtained by dividing.
8. A database testing apparatus, comprising:
the log acquisition module is used for acquiring at least one operation log aiming at least one database request;
the type determining module is used for determining the operation type of each operation log;
a risk operation determining module, configured to, when the operation type is a preset first operation type, use the operation log as a first operation log, determine, as a target operation log, a preset number of continuous operation logs starting from the first operation log, and determine whether an operation type of the target operation log includes a preset second operation type; the operation log is used for determining the operation log with the operation type of the preset second operation type as a second operation log when the preset second operation type is included, and judging whether the data table information contained in the second operation log and the first operation log is the same or not; and the processor is further configured to mark the first oplog and the second oplog as risky operations when the included data table information is the same.
9. A computer readable storage medium storing computer instructions which, when executed by a processor, implement the steps of the method of any one of claims 1 to 7.
10. An electronic device, comprising:
a processor;
a memory for storing the processor-executable instructions;
the processor is configured to read the executable instructions from the memory and execute the instructions to implement the method of any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911010332.7A CN111008123B (en) | 2019-10-23 | 2019-10-23 | Database testing method and device, storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911010332.7A CN111008123B (en) | 2019-10-23 | 2019-10-23 | Database testing method and device, storage medium and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111008123A true CN111008123A (en) | 2020-04-14 |
| CN111008123B CN111008123B (en) | 2023-10-24 |
Family
ID=70111512
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911010332.7A Active CN111008123B (en) | 2019-10-23 | 2019-10-23 | Database testing method and device, storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111008123B (en) |
Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5778387A (en) * | 1995-05-19 | 1998-07-07 | Sprint Communications Co., L.P. | Database automated recovery system |
| US20030208511A1 (en) * | 2002-05-02 | 2003-11-06 | Earl Leroy D. | Database replication system |
| JP2014153742A (en) * | 2013-02-05 | 2014-08-25 | Nippon Telegr & Teleph Corp <Ntt> | Log management system, log management device and log management method |
| US20140337283A1 (en) * | 2013-05-09 | 2014-11-13 | International Business Machines Corporation | Comparing database performance without benchmark workloads |
| US9235607B1 (en) * | 2012-03-29 | 2016-01-12 | Google Inc. | Specifying a predetermined degree of inconsistency for test data |
| CN105589797A (en) * | 2015-09-17 | 2016-05-18 | 中国银联股份有限公司 | Method for synchronous data time delay detection between master database and slave database |
| CN106156318A (en) * | 2016-07-05 | 2016-11-23 | 武汉斗鱼网络科技有限公司 | A kind of system and method realizing multinode data base's High Availabitity |
| CN106844163A (en) * | 2017-03-16 | 2017-06-13 | 郑州云海信息技术有限公司 | The method and device of a kind of database master-slave synchronisation condition monitoring |
| CN107391628A (en) * | 2017-06-30 | 2017-11-24 | 北京奇虎科技有限公司 | Method of data synchronization and device |
| CN108038157A (en) * | 2017-12-05 | 2018-05-15 | 北京星河星云信息技术有限公司 | Master-slave database reading/writing method, system, storage device and server |
| CN108304308A (en) * | 2018-02-07 | 2018-07-20 | 平安普惠企业管理有限公司 | User behavior monitoring method, device, computer equipment and storage medium |
| CN108319617A (en) * | 2017-01-17 | 2018-07-24 | 阿里巴巴集团控股有限公司 | Determine the method, apparatus and method for handover control, device of database principal and subordinate's difference |
| CN109165143A (en) * | 2018-08-17 | 2019-01-08 | 张家港康得新光电材料有限公司 | Database detection method, system, server and storage medium |
| US10198346B1 (en) * | 2015-09-28 | 2019-02-05 | Amazon Technologies, Inc. | Test framework for applications using journal-based databases |
-
2019
- 2019-10-23 CN CN201911010332.7A patent/CN111008123B/en active Active
Patent Citations (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5778387A (en) * | 1995-05-19 | 1998-07-07 | Sprint Communications Co., L.P. | Database automated recovery system |
| US20030208511A1 (en) * | 2002-05-02 | 2003-11-06 | Earl Leroy D. | Database replication system |
| US9235607B1 (en) * | 2012-03-29 | 2016-01-12 | Google Inc. | Specifying a predetermined degree of inconsistency for test data |
| JP2014153742A (en) * | 2013-02-05 | 2014-08-25 | Nippon Telegr & Teleph Corp <Ntt> | Log management system, log management device and log management method |
| US20140337283A1 (en) * | 2013-05-09 | 2014-11-13 | International Business Machines Corporation | Comparing database performance without benchmark workloads |
| CN105589797A (en) * | 2015-09-17 | 2016-05-18 | 中国银联股份有限公司 | Method for synchronous data time delay detection between master database and slave database |
| US10198346B1 (en) * | 2015-09-28 | 2019-02-05 | Amazon Technologies, Inc. | Test framework for applications using journal-based databases |
| CN106156318A (en) * | 2016-07-05 | 2016-11-23 | 武汉斗鱼网络科技有限公司 | A kind of system and method realizing multinode data base's High Availabitity |
| CN108319617A (en) * | 2017-01-17 | 2018-07-24 | 阿里巴巴集团控股有限公司 | Determine the method, apparatus and method for handover control, device of database principal and subordinate's difference |
| CN106844163A (en) * | 2017-03-16 | 2017-06-13 | 郑州云海信息技术有限公司 | The method and device of a kind of database master-slave synchronisation condition monitoring |
| CN107391628A (en) * | 2017-06-30 | 2017-11-24 | 北京奇虎科技有限公司 | Method of data synchronization and device |
| CN108038157A (en) * | 2017-12-05 | 2018-05-15 | 北京星河星云信息技术有限公司 | Master-slave database reading/writing method, system, storage device and server |
| CN108304308A (en) * | 2018-02-07 | 2018-07-20 | 平安普惠企业管理有限公司 | User behavior monitoring method, device, computer equipment and storage medium |
| CN109165143A (en) * | 2018-08-17 | 2019-01-08 | 张家港康得新光电材料有限公司 | Database detection method, system, server and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 郑煜: "基于同态哈希的目录服务数据变化捕获方法", pages 2007 - 2009 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111008123B (en) | 2023-10-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10289532B2 (en) | Method and system for providing delta code coverage information | |
| CN111756575B (en) | Performance analysis method and device of storage server and electronic equipment | |
| US20160062765A1 (en) | Identifying semantic differences between source code versions | |
| US10761963B2 (en) | Object monitoring in code debugging | |
| US8370799B2 (en) | Provision of code base modification using automatic learning of code changes | |
| EP3084610A1 (en) | Process for displaying test coverage data during code reviews | |
| CN108694320B (en) | Method and system for measuring sensitive application dynamic under multiple security environments | |
| CN105205053A (en) | Method and system for analyzing database incremental logs | |
| CN106557419B (en) | Program testing method and device | |
| CN112328499A (en) | Test data generation method, device, equipment and medium | |
| CN105512276B (en) | Method and device for constructing junk file and electronic equipment | |
| KR101696694B1 (en) | Method And Apparatus For Analysing Source Code Vulnerability By Using TraceBack | |
| CN115686961A (en) | Processor testing method and device and electronic equipment | |
| CN115658452A (en) | Buried point checking method, buried point checking device, readable storage medium and electronic equipment | |
| CN113377719B (en) | System abnormal shutdown time acquisition method and system | |
| CN111625853B (en) | Snapshot processing method, device and equipment and readable storage medium | |
| CN109491882B (en) | Case data processing method and system, equipment case and readable storage medium | |
| CN111008123B (en) | Database testing method and device, storage medium and electronic equipment | |
| CN115840707A (en) | Flash test method, device and medium | |
| CN113849404A (en) | Management method, device and storage medium for interface test related information | |
| Mui et al. | Studying late propagations in code clone evolution using software repository mining | |
| CN106293897B (en) | Automatic scheduling system of subassembly | |
| CN114116291B (en) | Log detection method, log detection device, computer device and storage medium | |
| CN113886191B (en) | Real-time tracking data processing method and device for automatic driving system | |
| CN114064455A (en) | Method and device for providing mock service and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |