CN117407369B - Operation log recording method and device and electronic equipment - Google Patents
Operation log recording method and device and electronic equipment Download PDFInfo
- Publication number
- CN117407369B CN117407369B CN202311728780.7A CN202311728780A CN117407369B CN 117407369 B CN117407369 B CN 117407369B CN 202311728780 A CN202311728780 A CN 202311728780A CN 117407369 B CN117407369 B CN 117407369B
- Authority
- CN
- China
- Prior art keywords
- target
- log
- data
- data table
- interface
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 56
- 238000012986 modification Methods 0.000 claims abstract description 35
- 230000004048 modification Effects 0.000 claims abstract description 35
- 230000004044 response Effects 0.000 claims abstract description 23
- 238000007792 addition Methods 0.000 claims abstract description 20
- 230000008569 process Effects 0.000 claims abstract description 20
- 238000012217 deletion Methods 0.000 claims abstract description 18
- 230000037430 deletion Effects 0.000 claims abstract description 18
- 238000012545 processing Methods 0.000 claims description 64
- 230000008859 change Effects 0.000 claims description 3
- 238000011161 development Methods 0.000 abstract description 38
- 238000010586 diagram Methods 0.000 description 11
- 238000004590 computer program Methods 0.000 description 7
- 230000003287 optical effect Effects 0.000 description 4
- 230000006870 function Effects 0.000 description 3
- 238000012546 transfer Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/1734—Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/1805—Append-only file systems, e.g. using logs or journals to store data
- G06F16/1815—Journaling file systems
-
- 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)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application discloses an operation log recording method, an operation log recording device and electronic equipment, wherein the method comprises the following steps: acquiring an operation request, wherein the operation request comprises an operation object and an operation type for operating the operation object, and the operation type comprises addition, modification or deletion; determining an operation log according to the operation object and the operation type; selecting a target operation business interface from a plurality of operation business interfaces according to the operation object; invoking the target operation service interface to enable the target operation service interface to respond to the operation request; and under the condition that the response of the target operation business interface is successful, recording the operation log. In this embodiment, before the target operation service interface processes the data table in the database, the operation log is determined, so that the log record interface does not need to be called in each operation service interface, and development efficiency can be improved.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for recording an operation log, and an electronic device.
Background
The operation log can be used for recording an operation after a user or a system performs a new operation, a modification operation or a deletion operation on a certain object, so that a certain operation log can be queried later according to requirements. In the prior art, when the operation log of the database is recorded, the operation related service data is input into the log recording interface through the operation service interface corresponding to each operation request, so as to record the operation log.
At present, according to the method for recording the operation log, the log recording interface needs to be called in each operation service interface, and codes for calling the log recording interface need to be added in each operation service interface every time one operation service interface is added, so that the development process is complicated, and the development efficiency is low.
Disclosure of Invention
The application provides an operation log recording method, an operation log recording device and electronic equipment, which can improve development efficiency without adding codes for calling log recording interfaces in each operation service interface when recording operation logs.
In a first aspect, the present application provides an operation log recording method, including:
Acquiring an operation request, wherein the operation request comprises an operation object and an operation type for operating the operation object, and the operation type comprises addition, modification or deletion;
determining an operation log according to the operation object and the operation type;
Selecting a target operation business interface from a plurality of operation business interfaces according to the operation object;
Invoking the target operation service interface to enable the target operation service interface to respond to the operation request;
And under the condition that the response of the target operation business interface is successful, recording the operation log.
In this embodiment, before the target operation service interface processes the data table in the database, the operation log is determined, so that the log record interface does not need to be called in each operation service interface, and development efficiency can be improved.
In one embodiment of the present application, obtaining an operation request includes:
under the condition that an operation request is acquired, intercepting the operation request through a first service processing interface;
Determining an operation log according to the operation object and the operation type, wherein the operation log comprises:
and determining an operation log through a first service processing interface according to the operation object and the operation type.
In this embodiment, the operation request is intercepted by the first service processing interface, and the operation log is determined based on the operation request, so that the log recording interface does not need to be called in each operation service interface, and development efficiency is improved.
In an embodiment of the present application, the operation object includes a uniform resource identifier, and the operation service interface is used for performing data processing on one data table, and different operation service interfaces correspond to different data tables;
Selecting a target operation business interface from a plurality of operation business interfaces according to the operation object, wherein the method comprises the following steps:
And selecting a target operation business interface identified by the uniform resource identifier from the plurality of operation business interfaces.
In this embodiment, the target operation service interface may be obtained through the same resource identifier included in the operation object, and the target operation service interface performs a new, modified or deleted process on the corresponding target data table. The target operation business interface is called each time the target data table is processed, that is, only one development is needed for the target operation business interface, and the target data table can be subjected to new addition, modification or deletion operation through the target operation business interface, so that the development efficiency can be improved.
In an embodiment of the present application, the operation object further includes operation data;
Determining an operation log according to the operation object and the operation type, wherein the operation log comprises:
Acquiring a target operation business interface identified by the uniform resource identifier;
Generating a query statement according to the table name of the target data table corresponding to the target operation service interface, the operation data and the operation type;
And obtaining the operation log based on the query statement.
In this embodiment, after the operation request is obtained, before the data in the target data table is changed, the operation log is determined according to the operation object and the operation type in the operation request, so that the log record interface does not need to be called in each operation service interface, and the development efficiency can be improved.
In an embodiment of the present application, the operation type is newly added, and the operation data includes a first field name in the target data table and data corresponding to the first field name;
generating a query statement according to the table name of the target data table corresponding to the target operation service interface, the operation data and the operation type, wherein the query statement comprises:
generating a query statement according to the table name of the target data table, the first field name, the data corresponding to the first field name and the operation type;
Based on the query statement, obtaining the operation log includes:
Based on the query statement, obtaining a value corresponding to a main key of the operation data to be newly added in the target data table;
and recording the operation type, the table name of the target data table and the value corresponding to the primary key in the operation log.
In this embodiment, under the condition that the operation type is newly added, the content recorded in the operation log is determined, so that before the target operation service interface performs the new addition processing on the data table in the database, the operation log is determined, so that the log record interface is not required to be invoked in each operation service interface later, and the development efficiency can be improved.
In an embodiment of the present application, the operation type is modification, and the operation data includes a second field name in the target data table and new data corresponding to the second field name;
generating a query statement according to the table name of the target data table corresponding to the target operation service interface, the operation data and the operation type, wherein the query statement comprises:
Generating a query statement according to the table name of the target data table, the second field name, new data corresponding to the second field name and the operation type;
Based on the query statement, obtaining the operation log includes:
based on the query statement, obtaining old data corresponding to the second field name in the target data table;
and recording the operation type, the table name of the target data table, and new data and old data corresponding to the second field name in the operation log.
In this embodiment, under the condition that the operation type is modification, the content recorded in the operation log is determined, so that the operation log can be determined before the target operation service interface modifies the data table in the database, so that the log record interface is not required to be invoked in each operation service interface later, and development efficiency can be improved.
In an embodiment of the present application, the operation type is delete, and the operation data includes a third field name in the target data table and data corresponding to the third field name;
generating a query statement according to the table name of the target data table corresponding to the target operation service interface, the operation data and the operation type, wherein the query statement comprises:
Generating a query statement according to the table name of the target data table, the third field name, the data corresponding to the third field name and the operation type;
Based on the query statement, obtaining the operation log includes:
based on the query statement, obtaining a data row to be deleted in the target data table;
and recording the operation type, the table name of the target data table and the data row in the operation log.
In this embodiment, under the condition that the operation type is delete, the content recorded in the operation log is determined, so that before the target operation service interface performs delete processing on the data table in the database, the operation log is determined, so that the log record interface is not required to be invoked in each operation service interface later, and development efficiency can be improved.
In an embodiment of the present application, invoking the target operation service interface to enable the target operation service interface to respond to the operation request includes:
and calling the target operation service interface, and transmitting the query statement to the target operation service interface, so that the target operation service interface carries out data processing on the target data table according to the query statement.
In this embodiment, when the electronic device invokes the target operation service interface, the query statement is transferred to the target operation service interface, and the target operation service interface may directly perform data processing on the target data table according to the query statement.
In a second aspect, an embodiment of the present application provides an operation log recording apparatus, including:
The system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring an operation request, the operation request comprises an operation object and an operation type for operating the operation object, and the operation type comprises addition, modification or deletion;
the determining module is used for determining an operation log according to the operation object and the operation type;
The selection module is used for selecting a target operation business interface from a plurality of operation business interfaces according to the operation object;
the calling module is used for calling the target operation service interface so that the target operation service interface responds to the operation request;
and the recording module is used for recording the operation log under the condition that the response of the target operation business interface is successful.
In this embodiment, before the target operation service interface processes the data table in the database, the operation log is determined, so that the log record interface does not need to be called in each operation service interface, and development efficiency can be improved.
In an embodiment of the present application, an obtaining module is configured to intercept an operation request through a first service processing interface when the operation request is obtained;
Correspondingly, the determining module is used for determining an operation log according to the operation object and the operation type through the first service processing interface.
In this embodiment, the operation request is intercepted by the first service processing interface, and the operation log is determined based on the operation request, so that the log recording interface does not need to be called in each operation service interface, and development efficiency is improved.
In an embodiment of the present application, the operation object includes a uniform resource identifier, and the operation service interface is used for performing data processing on one data table, and different operation service interfaces correspond to different data tables;
and the selection module is used for selecting the target operation business interface identified by the uniform resource identifier from the plurality of operation business interfaces.
In this embodiment, the target operation service interface may be obtained through the same resource identifier included in the operation object, and the target operation service interface performs a new, modified or deleted process on the corresponding target data table. The target operation business interface is called each time the target data table is processed, that is, only one development is needed for the target operation business interface, and the target data table can be subjected to new addition, modification or deletion operation through the target operation business interface, so that the development efficiency can be improved.
In an embodiment of the present application, the operation object further includes operation data;
The determining module includes:
The first acquisition sub-module is used for acquiring the target operation business interface identified by the uniform resource identifier;
the generating sub-module is used for generating a query statement according to the table name of the target data table corresponding to the target operation service interface, the operation data and the operation type;
And the second acquisition sub-module is used for acquiring the operation log based on the query statement.
In this embodiment, after the operation request is obtained, before the data in the target data table is changed, the operation log is determined according to the operation object and the operation type in the operation request, so that the log record interface does not need to be called in each operation service interface, and the development efficiency can be improved.
In an embodiment of the present application, the operation type is newly added, and the operation data includes a first field name in the target data table and data corresponding to the first field name;
the generating sub-module includes:
The first generation unit is used for generating a query statement according to the table name of the target data table, the first field name, the data corresponding to the first field name and the operation type;
accordingly, the second acquisition sub-module includes:
The first acquisition unit is used for acquiring a value corresponding to a main key of the operation data to be newly added in the target data table based on the query statement;
and the first recording unit is used for recording the operation type, the table name of the target data table and the value corresponding to the primary key in the operation log.
In this embodiment, under the condition that the operation type is newly added, the content recorded in the operation log is determined, so that before the target operation service interface performs the new addition processing on the data table in the database, the operation log is determined, so that the log record interface is not required to be invoked in each operation service interface later, and the development efficiency can be improved.
In an embodiment of the present application, the operation type is modification, and the operation data includes a second field name in the target data table and new data corresponding to the second field name;
the generating sub-module includes:
the second generating unit is used for generating a query statement according to the table name of the target data table, the second field name, new data corresponding to the second field name and the operation type;
accordingly, the second acquisition sub-module includes:
The second acquisition unit is used for acquiring old data corresponding to the second field name in the target data table based on the query statement;
and a second recording unit, configured to record, in the operation log, the operation type, a table name of the target data table, and new data and old data corresponding to the second field name.
In this embodiment, under the condition that the operation type is modification, the content recorded in the operation log is determined, so that the operation log can be determined before the target operation service interface modifies the data table in the database, so that the log record interface is not required to be invoked in each operation service interface later, and development efficiency can be improved.
In an embodiment of the present application, the operation type is delete, and the operation data includes a third field name in the target data table and data corresponding to the third field name;
the generating sub-module includes:
A third generating unit, configured to generate a query statement according to a table name of the target data table, the third field name, data corresponding to the third field name, and the operation type;
accordingly, the second acquisition sub-module includes:
a third obtaining unit, configured to obtain, based on the query statement, a data row to be deleted in the target data table;
And a third recording unit, configured to record the operation type, the table name of the target data table, and the data row in the operation log.
In this embodiment, under the condition that the operation type is delete, the content recorded in the operation log is determined, so that before the target operation service interface performs delete processing on the data table in the database, the operation log is determined, so that the log record interface is not required to be invoked in each operation service interface later, and development efficiency can be improved.
In an embodiment of the present application, the calling module 304 is configured to call the target operation service interface and transmit the query statement to the target operation service interface, so that the target operation service interface performs data processing on the target data table according to the query statement.
In this embodiment, when the electronic device invokes the target operation service interface, the query statement is transferred to the target operation service interface, and the target operation service interface may directly perform data processing on the target data table according to the query statement.
In a third aspect, embodiments of the present application provide a readable storage medium having stored thereon a program or instructions which when executed by a processor implement the steps of the oplogging method as described in the first aspect.
The foregoing description is only an overview of the present application, and is intended to be implemented in accordance with the teachings of the present application in order that the same may be more clearly understood and to make the same and other objects, features and advantages of the present application more readily apparent.
Drawings
Features, advantages, and technical effects of exemplary embodiments of the present application will be described below with reference to the accompanying drawings.
FIG. 1 is a flow chart of an operation log recording method according to an embodiment of the present application;
FIG. 2 is a schematic diagram of another flow chart of the method for operation log recording according to the embodiment of the present application;
FIG. 3 is a schematic diagram of an operation log recording device according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments of the present application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs; the terminology used in the description of the application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application; the terms "comprising" and "having" and any variations thereof in the description of the application and the claims and the description of the drawings above are intended to cover a non-exclusive inclusion. The terms first, second and the like in the description and in the claims or in the above-described figures, are used for distinguishing between different objects and not necessarily for describing a particular sequential or chronological order.
Fig. 1 is a flowchart of an operation log recording method according to an embodiment of the present application, as shown in fig. 1, where the method is applicable to an electronic device, and the operation log recording method includes steps 101 to 105, where:
Step 101, obtaining an operation request, wherein the operation request comprises an operation object and an operation type for operating the operation object, and the operation type comprises adding, modifying or deleting.
The operation request may be generated based on a user operation, or may be sent by another device that interacts with the electronic device, and the operation request may be a hypertext transfer protocol (Hypertext Transfer Protocol, HTTP) request, which is not limited herein.
After the electronic equipment acquires the operation request, the operation request is analyzed to obtain an operation object and an operation type for operating the operation object. The operation object may include an identification of the operation object, such as a name of the operation object, or a uniform resource identifier (Uniform Resource Identifier, URI) of the operation object, by which the operation object may be determined, for example, if a data table is determined based on the URI, the data table is the operation object. For example. In this embodiment, the operation object may be a data table in a database, which is not limited herein.
The operation type is used for indicating that the operation object is subjected to the process of adding, modifying or deleting.
And 102, determining an operation log according to the operation object and the operation type.
For example, according to the operation object and the operation type, it may be determined which data table in the database is subjected to the new, modified or deleted processing, so as to obtain an operation log, where the operation log may refer to a processing condition record of the target data table indicated by the operation object. In this step, no modification is made to the data table in the database.
And step 103, selecting a target operation business interface from a plurality of operation business interfaces according to the operation object.
The operation object may be a data table in the database, where each data table corresponds to an operation service interface, and the operation service interface is used to perform data processing, for example, adding, modifying or deleting processing on the data table. In this step, a specific data table may be determined according to the identifier of the operation object, where the operation service interface corresponding to the data table is the target operation service interface. The operation service interface may be a data access object (DATA ACCESS Objects, DAO), which is an object-oriented interface.
Step 104, the target operation business interface is called, so that the target operation business interface responds to the operation request.
The electronic equipment calls a target operation service interface, transmits an operation request to the target operation service interface, and performs new addition, modification or deletion processing on the operation object according to the operation request by the target operation service interface.
And step 105, recording the operation log under the condition that the response of the target operation business interface is successful.
And the target operation business interface performs new adding, modifying or deleting treatment on the target data table indicated by the operation object in the database according to the operation request, and after the treatment is completed, a response result is obtained, wherein the response result comprises response success and response failure. The successful response means that the new addition, modification or deletion processing of the target data table is completed; the failure in response means that the incomplete target data table is subjected to new addition, modification or deletion processing, the reason for the incomplete is not limited, the response is overtime, or the response is wrong, the incomplete result is not limited, and the incomplete result can mean that the target data table is not modified. The target operation business interface feeds back a response result to the electronic equipment no matter whether the response is successful or failed, and the electronic equipment records the operation log under the condition that the electronic equipment receives the message of successful response sent by the target operation business interface. The operation log is generated in step 102, but is not recorded, in this step, the operation log is recorded only when the response of the target operation service interface is successful, and the modification condition of the target data table can be accurately recorded.
In this embodiment, an operation request is obtained, where the operation request includes an operation object and an operation type for operating the operation object, and the operation type includes adding, modifying, or deleting; determining an operation log according to the operation object and the operation type; selecting a target operation business interface from a plurality of operation business interfaces according to the operation object; invoking the target operation service interface to enable the target operation service interface to respond to the operation request; and under the condition that the response of the target operation business interface is successful, recording the operation log. Through the process, before the target operation business interface processes the data table in the database, the operation log is determined, so that the log record interface does not need to be called in each operation business interface, and the development efficiency can be improved.
In one embodiment of the present application, obtaining an operation request includes:
under the condition that an operation request is acquired, intercepting the operation request through a first service processing interface;
Determining an operation log according to the operation object and the operation type, wherein the operation log comprises:
and determining an operation log through a first service processing interface according to the operation object and the operation type.
In this embodiment, when the electronic device obtains the operation request, the operation request is intercepted by a first service processing interface in the electronic device, where the first service processing interface may be a tangent plane oriented programming (Aspect Oriented Programming, AOP) interface. The operation request can carry a preset identifier, the first service processing interface can analyze all operation requests acquired by the electronic equipment, and when the operation request is analyzed to carry the preset identifier, the operation request is judged to be an operation request to be intercepted, the operation request is intercepted and processed, and the processing process is to determine an operation log according to an operation object and an operation type. For example, the first service processing interface determines which data table is subjected to the new addition, modification or deletion processing according to the operation object and the operation type, so as to obtain an operation log, where the operation log may refer to a record of the processing situation of the target data table indicated by the operation object.
In this embodiment, the operation request is intercepted by the first service processing interface, and the operation log is determined based on the operation request, so that the log recording interface does not need to be called in each operation service interface, and development efficiency is improved.
In an embodiment of the present application, the operation object includes a uniform resource identifier, and the operation service interface is used for performing data processing on one data table, and different operation service interfaces correspond to different data tables;
Selecting a target operation business interface from a plurality of operation business interfaces according to the operation object, wherein the method comprises the following steps:
And selecting a target operation business interface identified by the uniform resource identifier from the plurality of operation business interfaces.
Specifically, each operation service interface is used for carrying out data processing on one data table, and different operation service interfaces correspond to different data tables. The operation object comprises a uniform resource identifier, a target operation service interface can be searched according to the uniform resource identifier, and a data table corresponding to the target operation service interface is the target data table.
In this embodiment, the target operation service interface may be obtained through the same resource identifier included in the operation object, and the target operation service interface performs a new, modified or deleted process on the corresponding target data table. The target operation business interface is called each time the target data table is processed, that is, only one development is needed for the target operation business interface, and the target data table can be subjected to new addition, modification or deletion operation through the target operation business interface, so that the development efficiency can be improved.
In an embodiment of the present application, the operation object further includes operation data;
Determining an operation log according to the operation object and the operation type, wherein the operation log comprises:
Acquiring a target operation business interface identified by the uniform resource identifier;
Generating a query statement according to the table name of the target data table corresponding to the target operation service interface, the operation data and the operation type;
And obtaining the operation log based on the query statement.
In this embodiment, the operation object further includes operation data, where the operation data may refer to a field name in the target data table and data corresponding to the field name. According to the uniform resource identifier in the operation object, a target operation service interface can be obtained, according to a target data table corresponding to the target operation service interface, a table name of the target data table can be obtained, further, according to the table name and operation data of the target data table and the operation type, a query statement is generated, and the query statement can be an SQL statement, which is not limited herein. The operation log may be a query statement, or an operation record obtained according to the query statement, which is not limited herein. The operation log is used for recording new, modified or deleted operations to the target data table. In the step of determining the operation log, the data change operation is not performed on the target data table.
In this embodiment, after the operation request is obtained, before the data in the target data table is changed, the operation log is determined according to the operation object and the operation type in the operation request, so that the log record interface does not need to be called in each operation service interface, and the development efficiency can be improved.
In an embodiment of the present application, the operation type is newly added, and the operation data includes a first field name in the target data table and data corresponding to the first field name;
generating a query statement according to the table name of the target data table corresponding to the target operation service interface, the operation data and the operation type, wherein the query statement comprises:
generating a query statement according to the table name of the target data table, the first field name, the data corresponding to the first field name and the operation type;
Based on the query statement, obtaining the operation log includes:
Based on the query statement, obtaining a value corresponding to a main key of the operation data to be newly added in the target data table;
and recording the operation type, the table name of the target data table and the value corresponding to the primary key in the operation log.
In this embodiment, when the operation type is newly added, the content recorded in the operation log is described.
The operation type is newly added, that is, information is newly added in the target data table, the newly added information includes a first field name of the target data table and data corresponding to the first field name, it should be noted that the first field name may include one or more field names, which are not limited herein, each field name needs to have corresponding data, and if a certain field name does not carry corresponding data in the operation data, default data is adopted.
For example, a row of data is newly added in the target data table, the field name of the newly added row and the data corresponding to the field name are carried in the operation data, if the value corresponding to the primary key of the row of data is not carried in the operation data, a random value can be generated based on the query statement as the primary key, only the random value is needed, or the target data table is searched based on the query statement, so that a value corresponding to the primary key is obtained, and the value is different from the value corresponding to the primary key in the target data table.
And recording an operation type, a table name of the target data table and a value corresponding to the main key in an operation log, and subsequently obtaining the newly added information through the value corresponding to the main key when the newly added information is determined.
In this embodiment, under the condition that the operation type is newly added, the content recorded in the operation log is determined, so that before the target operation service interface performs the new addition processing on the data table in the database, the operation log is determined, so that the log record interface is not required to be invoked in each operation service interface later, and the development efficiency can be improved.
In an embodiment of the present application, the operation type is modification, and the operation data includes a second field name in the target data table and new data corresponding to the second field name;
generating a query statement according to the table name of the target data table corresponding to the target operation service interface, the operation data and the operation type, wherein the query statement comprises:
Generating a query statement according to the table name of the target data table, the second field name, new data corresponding to the second field name and the operation type;
Based on the query statement, obtaining the operation log includes:
based on the query statement, obtaining old data corresponding to the second field name in the target data table;
and recording the operation type, the table name of the target data table, and new data and old data corresponding to the second field name in the operation log.
In this embodiment, the content recorded in the operation log in the case where the operation type is modification is described.
The operation type is modification, namely, existing information in the target data table is modified, and the information to be modified can be searched according to the second field name. It should be noted that, the second field name may include one or more field names, which are not limited herein, each field name needs to have corresponding new data, and if a certain field name does not carry corresponding new data in the operation data, default data is used to replace existing old data.
Since the field content corresponding to the second field name needs to be modified, in order to facilitate subsequent inquiry of information before and after modification, old data before modification and new data after modification need to be recorded in the operation log. Based on the above, after obtaining the query statement, searching the target data table according to the query statement to obtain old data corresponding to the second field name in the target data table, and recording the operation type, the table name of the target data table, and new data and old data corresponding to the second field name in the operation log.
In this embodiment, under the condition that the operation type is modification, the content recorded in the operation log is determined, so that the operation log can be determined before the target operation service interface modifies the data table in the database, so that the log record interface is not required to be invoked in each operation service interface later, and development efficiency can be improved.
In an embodiment of the present application, the operation type is delete, and the operation data includes a third field name in the target data table and data corresponding to the third field name;
generating a query statement according to the table name of the target data table corresponding to the target operation service interface, the operation data and the operation type, wherein the query statement comprises:
Generating a query statement according to the table name of the target data table, the third field name, the data corresponding to the third field name and the operation type;
Based on the query statement, obtaining the operation log includes:
based on the query statement, obtaining a data row to be deleted in the target data table;
and recording the operation type, the table name of the target data table and the data row in the operation log.
In this embodiment, when the operation type is delete, the content recorded in the operation log is described.
The operation type is deletion, that is, deleting an existing data row in the target data table, where the data row includes a third field name of the target data table and data corresponding to the third field name, where it should be noted that the third field name may include one or more field names, and not limited herein, and each field name needs to have corresponding data.
Illustratively, the data row to be deleted is obtained by searching in the target data table according to the third field name and the data corresponding to the third field name. And recording the operation type, the table name of the target data table and the data row in an operation log.
In this embodiment, under the condition that the operation type is delete, the content recorded in the operation log is determined, so that before the target operation service interface performs delete processing on the data table in the database, the operation log is determined, so that the log record interface is not required to be invoked in each operation service interface later, and development efficiency can be improved.
In an embodiment of the present application, invoking the target operation service interface to enable the target operation service interface to respond to the operation request includes:
and calling the target operation service interface, and transmitting the query statement to the target operation service interface, so that the target operation service interface carries out data processing on the target data table according to the query statement.
In this embodiment, when the electronic device invokes the target operation service interface, the query statement is transferred to the target operation service interface, and the target operation service interface may directly perform data processing on the target data table according to the query statement.
The operation log recording method provided by the application is exemplified as follows. As shown in fig. 2, the method comprises the following steps:
step 201, receiving an HTTP request through a service layer execution code, wherein the operation request comprises an operation object and an operation type for operating the operation object, and the operation type comprises adding, modifying or deleting;
And 202, executing data service through DAO to obtain SQL. Intercepting DAO by AOP intrusion, executing data service by DAO, obtaining SQL, namely determining an operation log according to the operation object and the operation type, and specifically obtaining and executing SQL according to JoinPoint and SqlSessionFactory;
according to the operation type, the method is divided into three cases of processing, namely adding, modifying and deleting.
In the new case, the operation object needs to include a URI (according to the URI, DAO can be found, and DAO is an interface for operating a data table in the database, where each DAO corresponds to one data table) and operation data, and according to the operation data and the operation type, it can be known which field in the data table is to be added, modified and deleted.
For example, adding data refers to adding a row of data in a target data table determined according to the URI, the operation data may be carried with the first field name and the data corresponding to the first field name, where the row of data has a primary key, and the value of the primary key may be carried in the operation data or may be generated by the data table, and is not limited.
According to the operation type, the operation data and the table name of the target data table, an SQL sentence is generated, and according to the SQL sentence, a row of data to be newly added in the target data table can be known, and the value corresponding to the first field name in the row of data is determined according to the operation data.
In order to determine what row of data is newly added, the name of the target data table, and the primary key of the newly added data are recorded in the operation log.
For another example, modifying data refers to modifying data of a certain field in the target data table, and the operation data may include a second field name and new data of the second field name;
according to the data type, the operation data and the table name of the target data table, an SQL statement can be generated, and according to the SQL statement, the data of the second field name of the target data table can be known to be modified, and the new data is carried in the operation data.
In order to determine to record the pre-modification data, it is necessary to take out the old data from the target data table and record the name of the target data table, the second field name, the new data and the old data in the operation log.
For example, deleting data refers to deleting a certain row of data in the target data table, and the operation data may include a third field name and data of the third field name;
according to the operation type, the operation data and the table name of the target data table, an SQL sentence can be generated, the third field name to be deleted and the data of the third field name can be known according to the SQL sentence, the row is searched, and the value of the main key of the line is obtained.
To determine which row of data is deleted, the name of the target data table is recorded in the operation log, and the deleted row of data.
In step 203, a target service operation interface is selected from the multiple service operation interfaces according to the operation object, where the target service operation interface is a DAO corresponding to the URI, and the target data table may be operated through the DAO, for example, tableName (i.e. a table name of the target data table) and a service main ID (a value of a main key) are obtained according to the DAO class annotation.
Step 204, calling the target business operation interface to make the target business operation interface respond to the operation request; and operating the target data table through the DAO, for example, adding data to the target data table, modifying the data and deleting the data.
And step 205, recording the operation log under the condition that the response of the target business operation interface is successful.
In the whole process, the AOP characteristic of the Spring framework can be utilized to cut in the DAO layer of the core operation data of the service system, so that a newly added, modified or deleted operation log is obtained, namely, the process of determining the operation log is finished outside the service operation interface, and the code for calling the log record interface is not required to be written in the service operation interface, so that the development efficiency can be saved. In addition, the process can simplify the operation log recording process, does not need to invade business module codes, reduces development complexity and improves efficiency.
Referring to fig. 3, a schematic structural diagram of an operation log recording apparatus according to an embodiment of the present application is shown in fig. 3, and the operation log recording apparatus 300 includes:
An obtaining module 301, configured to obtain an operation request, where the operation request includes an operation object, and an operation type for operating the operation object, where the operation type includes adding, modifying, or deleting;
a determining module 302, configured to determine an operation log according to the operation object and the operation type;
A selection module 303, configured to select a target operation service interface from a plurality of operation service interfaces according to the operation object;
A calling module 304, configured to call the target operation service interface, so that the target operation service interface responds to the operation request;
And the recording module 305 is configured to record the operation log if the response of the target operation service interface is successful.
In this embodiment, before the target operation service interface processes the data table in the database, the operation log is determined, so that the log record interface does not need to be called in each operation service interface, and development efficiency can be improved.
In an embodiment of the present application, an obtaining module 301 is configured to intercept an operation request through a first service processing interface when the operation request is obtained;
accordingly, the determining module 302 is configured to determine, through the first service processing interface, an operation log according to the operation object and the operation type.
In this embodiment, the operation request is intercepted by the first service processing interface, and the operation log is determined based on the operation request, so that the log recording interface does not need to be called in each operation service interface, and development efficiency is improved.
In an embodiment of the present application, the operation object includes a uniform resource identifier, and the operation service interface is used for performing data processing on one data table, and different operation service interfaces correspond to different data tables;
A selection module 303, configured to select a target operation service interface identified by the uniform resource identifier from the plurality of operation service interfaces.
In this embodiment, the target operation service interface may be obtained through the same resource identifier included in the operation object, and the target operation service interface performs a new, modified or deleted process on the corresponding target data table. The target operation business interface is called each time the target data table is processed, that is, only one development is needed for the target operation business interface, and the target data table can be subjected to new addition, modification or deletion operation through the target operation business interface, so that the development efficiency can be improved.
In an embodiment of the present application, the operation object further includes operation data;
the determining module 302 includes:
The first acquisition sub-module is used for acquiring the target operation business interface identified by the uniform resource identifier;
the generating sub-module is used for generating a query statement according to the table name of the target data table corresponding to the target operation service interface, the operation data and the operation type;
And the second acquisition sub-module is used for acquiring the operation log based on the query statement.
In this embodiment, after the operation request is obtained, before the data in the target data table is changed, the operation log is determined according to the operation object and the operation type in the operation request, so that the log record interface does not need to be called in each operation service interface, and the development efficiency can be improved.
In an embodiment of the present application, the operation type is newly added, and the operation data includes a first field name in the target data table and data corresponding to the first field name;
the generating sub-module includes:
The first generation unit is used for generating a query statement according to the table name of the target data table, the first field name, the data corresponding to the first field name and the operation type;
accordingly, the second acquisition sub-module includes:
The first acquisition unit is used for acquiring a value corresponding to a main key of the operation data to be newly added in the target data table based on the query statement;
and the first recording unit is used for recording the operation type, the table name of the target data table and the value corresponding to the primary key in the operation log.
In this embodiment, under the condition that the operation type is newly added, the content recorded in the operation log is determined, so that before the target operation service interface performs the new addition processing on the data table in the database, the operation log is determined, so that the log record interface is not required to be invoked in each operation service interface later, and the development efficiency can be improved.
In an embodiment of the present application, the operation type is modification, and the operation data includes a second field name in the target data table and new data corresponding to the second field name;
the generating sub-module includes:
the second generating unit is used for generating a query statement according to the table name of the target data table, the second field name, new data corresponding to the second field name and the operation type;
accordingly, the second acquisition sub-module includes:
The second acquisition unit is used for acquiring old data corresponding to the second field name in the target data table based on the query statement;
and a second recording unit, configured to record, in the operation log, the operation type, a table name of the target data table, and new data and old data corresponding to the second field name.
In this embodiment, under the condition that the operation type is modification, the content recorded in the operation log is determined, so that the operation log can be determined before the target operation service interface modifies the data table in the database, so that the log record interface is not required to be invoked in each operation service interface later, and development efficiency can be improved.
In an embodiment of the present application, the operation type is delete, and the operation data includes a third field name in the target data table and data corresponding to the third field name;
the generating sub-module includes:
A third generating unit, configured to generate a query statement according to a table name of the target data table, the third field name, data corresponding to the third field name, and the operation type;
accordingly, the second acquisition sub-module includes:
a third obtaining unit, configured to obtain, based on the query statement, a data row to be deleted in the target data table;
And a third recording unit, configured to record the operation type, the table name of the target data table, and the data row in the operation log.
In this embodiment, under the condition that the operation type is delete, the content recorded in the operation log is determined, so that before the target operation service interface performs delete processing on the data table in the database, the operation log is determined, so that the log record interface is not required to be invoked in each operation service interface later, and development efficiency can be improved.
In an embodiment of the present application, the calling module 304 is configured to call the target operation service interface and transmit the query statement to the target operation service interface, so that the target operation service interface performs data processing on the target data table according to the query statement.
In this embodiment, when the electronic device invokes the target operation service interface, the query statement is transferred to the target operation service interface, and the target operation service interface may directly perform data processing on the target data table according to the query statement.
Fig. 4 shows a schematic hardware structure of an electronic device according to an embodiment of the present application.
The electronic device may include a processor 501 and a memory 502 storing computer program instructions.
In particular, the processor 501 may include a central processing unit (Central Processing Unit, CPU), or Application SPECIFIC INTEGRATED Circuit (ASIC), or may be configured as one or more integrated circuits that implement embodiments of the present application.
Memory 502 may include mass storage for data or instructions. By way of example, and not limitation, memory 502 may comprise a hard disk drive (HARD DISK DRIVE, HDD), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or universal serial bus (Universal Serial Bus, USB) drive, or a combination of two or more of the foregoing. In some examples, memory 402 may include removable or non-removable (or fixed) media, or memory 502 may be a non-volatile solid state memory. In some embodiments, the memory 502 may be internal or external to the battery device.
In some examples, memory 502 may be Read Only Memory (ROM). In one example, the ROM may be mask-programmed ROM, programmable ROM (PROM), erasable PROM (EPROM), electrically Erasable PROM (EEPROM), electrically rewritable ROM (EAROM), or flash memory, or a combination of two or more of these.
Memory 502 may include Read Only Memory (ROM), random Access Memory (RAM), magnetic disk storage media devices, optical storage media devices, flash memory devices, electrical, optical, or other physical/tangible memory storage devices. Thus, in general, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software comprising computer-executable instructions and when the software is executed (e.g., by one or more processors) it is operable to perform the operations described by the oplogging method provided by embodiments of the application.
The processor 501 reads and executes the computer program instructions stored in the memory 502 to implement the operation log recording method in the embodiment shown in fig. 1, and achieves the corresponding technical effects achieved by executing the method/steps in the embodiment shown in fig. 1, which is not described herein for brevity.
In addition, embodiments of the present application may be implemented by providing a computer storage medium. The computer storage medium has stored thereon computer program instructions; the computer program instructions, when executed by a processor, implement any of the oplogging methods of the above embodiments.
It should be understood that the application is not limited to the particular arrangements and instrumentality described above and shown in the drawings. For the sake of brevity, a detailed description of known methods is omitted here. In the above embodiments, several specific steps are described and shown as examples. The method processes of the present application are not limited to the specific steps described and shown, but various changes, modifications and additions, or the order between steps may be made by those skilled in the art after appreciating the spirit of the present application.
The functional blocks shown in the above block diagrams may be implemented in hardware, software, firmware, or a combination thereof. When implemented in hardware, it may be, for example, an electronic Circuit, application SPECIFIC INTEGRATED Circuit (ASIC), appropriate firmware, plug-in, function card, or the like. When implemented in software, the elements of the application are the programs or code segments used to perform the required tasks. The program or code segments may be stored in a machine readable medium or transmitted over transmission media or communication links by a data signal carried in a carrier wave. A "machine-readable medium" may include any medium that can store or transfer information. Examples of machine-readable media include electronic circuitry, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio Frequency (RF) links, and the like. The code segments may be downloaded via computer networks such as the internet, intranets, etc.
It should also be noted that the exemplary embodiments mentioned in this disclosure describe some methods or systems based on a series of steps or devices. The present application is not limited to the order of the above-described steps, that is, the steps may be performed in the order mentioned in the embodiments, or may be performed in a different order from the order in the embodiments, or several steps may be performed simultaneously.
Aspects of the present disclosure are described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus, devices, and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions/acts specified in the flowchart and/or block diagram block or blocks. Such a processor may be, but is not limited to being, a general purpose processor, a special purpose processor, an application specific processor, or a field programmable logic circuit. It will also be understood that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware which performs the specified functions or acts, or combinations of special purpose hardware and computer instructions.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some or all of the technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the application, and are intended to be included within the scope of the appended claims and description. In particular, the technical features mentioned in the respective embodiments may be combined in any manner as long as there is no structural conflict. The present application is not limited to the specific embodiments disclosed herein, but encompasses all technical solutions falling within the scope of the claims.
Claims (9)
1. An operation log recording method, comprising:
Acquiring an operation request, wherein the operation request comprises an operation object and an operation type for operating the operation object, and the operation type comprises addition, modification or deletion;
determining an operation log according to the operation object and the operation type, wherein in the process of determining the operation log, data change operation is not performed on a target data table indicated by the operation object;
Selecting a target operation business interface from a plurality of operation business interfaces according to the operation object;
Invoking the target operation service interface to enable the target operation service interface to respond to the operation request;
recording the operation log under the condition that the response of the target operation business interface is successful, wherein the successful response means that the new addition, modification or deletion processing is completed on the target data table;
obtaining an operation request, including:
under the condition that an operation request is acquired, intercepting the operation request through a first service processing interface;
Determining an operation log according to the operation object and the operation type, wherein the operation log comprises:
and determining an operation log through a first service processing interface according to the operation object and the operation type.
2. The operation log recording method according to claim 1, wherein the operation object comprises a uniform resource identifier, the operation service interface is used for performing data processing on one data table, and different operation service interfaces correspond to different data tables;
Selecting a target operation business interface from a plurality of operation business interfaces according to the operation object, wherein the method comprises the following steps:
And selecting a target operation business interface identified by the uniform resource identifier from the plurality of operation business interfaces.
3. The operation log recording method according to claim 2, wherein the operation object further includes operation data;
Determining an operation log according to the operation object and the operation type, wherein the operation log comprises:
Acquiring a target operation business interface identified by the uniform resource identifier;
Generating a query statement according to the table name of the target data table corresponding to the target operation service interface, the operation data and the operation type;
And obtaining the operation log based on the query statement.
4. The operation log recording method according to claim 3, wherein the operation type is newly added, and the operation data includes a first field name in the target data table and data corresponding to the first field name;
generating a query statement according to the table name of the target data table corresponding to the target operation service interface, the operation data and the operation type, wherein the query statement comprises:
generating a query statement according to the table name of the target data table, the first field name, the data corresponding to the first field name and the operation type;
Based on the query statement, obtaining the operation log includes:
Based on the query statement, obtaining a value corresponding to a main key of the operation data to be newly added in the target data table;
and recording the operation type, the table name of the target data table and the value corresponding to the primary key in the operation log.
5. The oplogging method of claim 3 wherein the operation type is a modification, the operation data comprising a second field name in the target data table and new data corresponding to the second field name;
generating a query statement according to the table name of the target data table corresponding to the target operation service interface, the operation data and the operation type, wherein the query statement comprises:
Generating a query statement according to the table name of the target data table, the second field name, new data corresponding to the second field name and the operation type;
Based on the query statement, obtaining the operation log includes:
based on the query statement, obtaining old data corresponding to the second field name in the target data table;
and recording the operation type, the table name of the target data table, and new data and old data corresponding to the second field name in the operation log.
6. The operation log recording method according to claim 3, wherein the operation type is deletion, and the operation data includes a third field name in the target data table and data corresponding to the third field name;
generating a query statement according to the table name of the target data table corresponding to the target operation service interface, the operation data and the operation type, wherein the query statement comprises:
Generating a query statement according to the table name of the target data table, the third field name, the data corresponding to the third field name and the operation type;
Based on the query statement, obtaining the operation log includes:
based on the query statement, obtaining a data row to be deleted in the target data table;
and recording the operation type, the table name of the target data table and the data row in the operation log.
7. The oplogging method of claim 3, wherein invoking the target operational business interface such that the target operational business interface responds to the operational request comprises:
and calling the target operation service interface, and transmitting the query statement to the target operation service interface, so that the target operation service interface carries out data processing on the target data table according to the query statement.
8. An operation log recording apparatus, comprising:
The system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring an operation request, the operation request comprises an operation object and an operation type for operating the operation object, and the operation type comprises addition, modification or deletion;
the determining module is used for determining an operation log according to the operation object and the operation type, wherein in the process of determining the operation log, data change operation is not carried out on a target data table indicated by the operation object;
The selection module is used for selecting a target operation business interface from a plurality of operation business interfaces according to the operation object;
the calling module is used for calling the target operation service interface so that the target operation service interface responds to the operation request;
The recording module is used for recording the operation log under the condition that the response of the target operation business interface is successful, wherein the successful response means that the new addition, modification or deletion processing is completed on the target data table;
The acquiring module is specifically configured to intercept an operation request through a first service processing interface when the operation request is acquired;
The determining module is specifically configured to determine, through a first service processing interface, an operation log according to the operation object and the operation type.
9. An electronic device comprising a processor, a memory and a program or instruction stored on the memory and executable on the processor, which when executed by the processor, implements the steps of the oplogging method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311728780.7A CN117407369B (en) | 2023-12-14 | 2023-12-14 | Operation log recording method and device and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311728780.7A CN117407369B (en) | 2023-12-14 | 2023-12-14 | Operation log recording method and device and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN117407369A CN117407369A (en) | 2024-01-16 |
| CN117407369B true CN117407369B (en) | 2024-05-28 |
Family
ID=89491213
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311728780.7A Active CN117407369B (en) | 2023-12-14 | 2023-12-14 | Operation log recording method and device and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117407369B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN118503056A (en) * | 2024-07-19 | 2024-08-16 | 北京唯得科技有限公司 | Log recording method and system |
Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107704369A (en) * | 2017-08-31 | 2018-02-16 | 云宏信息科技股份有限公司 | A kind of recording method of Operation Log, electronic equipment, storage medium, system |
| CN111241125A (en) * | 2020-01-08 | 2020-06-05 | 成都嗨学洛子教育科技有限公司 | Method and device for recording operation log, electronic equipment and storage medium |
| CN112580094A (en) * | 2020-12-14 | 2021-03-30 | 京东数字科技控股股份有限公司 | Data processing method, electronic device, and storage medium |
| CN113220362A (en) * | 2021-04-30 | 2021-08-06 | 浙江大华技术股份有限公司 | Log record obtaining method and device, computer equipment and storage medium |
| CN113254399A (en) * | 2021-05-27 | 2021-08-13 | 平安普惠企业管理有限公司 | Log query method and device, electronic equipment and medium |
| CN113360138A (en) * | 2021-06-18 | 2021-09-07 | 深圳前海微众银行股份有限公司 | Operation log processing method and device, electronic equipment and storage medium |
| CN113608955A (en) * | 2021-06-30 | 2021-11-05 | 北京新氧科技有限公司 | Log recording method, device, equipment and storage medium |
| CN113849473A (en) * | 2021-09-17 | 2021-12-28 | 重庆京东方智慧科技有限公司 | Operation recording method, operation recording device, electronic device, and storage medium |
| CN115114113A (en) * | 2022-07-15 | 2022-09-27 | 平安科技（深圳）有限公司 | Log recording method, device, equipment and storage medium |
| CN115391142A (en) * | 2022-08-30 | 2022-11-25 | 金现代信息产业股份有限公司 | Database audit log generation method and system |
| CN115858471A (en) * | 2022-12-07 | 2023-03-28 | 湖南长银五八消费金融股份有限公司 | Service data change recording method, device, computer equipment and medium |
| CN115858320A (en) * | 2022-12-16 | 2023-03-28 | 中国建设银行股份有限公司 | Operation log recording method, apparatus, medium and product |
| CN115883647A (en) * | 2022-11-29 | 2023-03-31 | 京东科技信息技术有限公司 | Service log recording method, system, device, terminal, server and medium |
| CN116204540A (en) * | 2022-11-29 | 2023-06-02 | 明度智云(浙江)科技有限公司 | Operation log recording method, device, equipment and storage medium |
| CN116561146A (en) * | 2023-05-10 | 2023-08-08 | 北京洞悉网络有限公司 | Database log recording method, device, computer equipment and computer readable storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8676749B2 (en) * | 2008-07-31 | 2014-03-18 | Sybase, Inc. | Statement logging in databases |
-
2023
- 2023-12-14 CN CN202311728780.7A patent/CN117407369B/en active Active
Patent Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107704369A (en) * | 2017-08-31 | 2018-02-16 | 云宏信息科技股份有限公司 | A kind of recording method of Operation Log, electronic equipment, storage medium, system |
| CN111241125A (en) * | 2020-01-08 | 2020-06-05 | 成都嗨学洛子教育科技有限公司 | Method and device for recording operation log, electronic equipment and storage medium |
| CN112580094A (en) * | 2020-12-14 | 2021-03-30 | 京东数字科技控股股份有限公司 | Data processing method, electronic device, and storage medium |
| CN113220362A (en) * | 2021-04-30 | 2021-08-06 | 浙江大华技术股份有限公司 | Log record obtaining method and device, computer equipment and storage medium |
| CN113254399A (en) * | 2021-05-27 | 2021-08-13 | 平安普惠企业管理有限公司 | Log query method and device, electronic equipment and medium |
| CN113360138A (en) * | 2021-06-18 | 2021-09-07 | 深圳前海微众银行股份有限公司 | Operation log processing method and device, electronic equipment and storage medium |
| CN113608955A (en) * | 2021-06-30 | 2021-11-05 | 北京新氧科技有限公司 | Log recording method, device, equipment and storage medium |
| CN113849473A (en) * | 2021-09-17 | 2021-12-28 | 重庆京东方智慧科技有限公司 | Operation recording method, operation recording device, electronic device, and storage medium |
| CN115114113A (en) * | 2022-07-15 | 2022-09-27 | 平安科技（深圳）有限公司 | Log recording method, device, equipment and storage medium |
| CN115391142A (en) * | 2022-08-30 | 2022-11-25 | 金现代信息产业股份有限公司 | Database audit log generation method and system |
| CN115883647A (en) * | 2022-11-29 | 2023-03-31 | 京东科技信息技术有限公司 | Service log recording method, system, device, terminal, server and medium |
| CN116204540A (en) * | 2022-11-29 | 2023-06-02 | 明度智云(浙江)科技有限公司 | Operation log recording method, device, equipment and storage medium |
| CN115858471A (en) * | 2022-12-07 | 2023-03-28 | 湖南长银五八消费金融股份有限公司 | Service data change recording method, device, computer equipment and medium |
| CN115858320A (en) * | 2022-12-16 | 2023-03-28 | 中国建设银行股份有限公司 | Operation log recording method, apparatus, medium and product |
| CN116561146A (en) * | 2023-05-10 | 2023-08-08 | 北京洞悉网络有限公司 | Database log recording method, device, computer equipment and computer readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN117407369A (en) | 2024-01-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107220142B (en) | Method and device for executing data recovery operation | |
| CN117407369B (en) | Operation log recording method and device and electronic equipment | |
| CN111475376B (en) | Method, apparatus, computer device and storage medium for processing test data | |
| CN112154420B (en) | Automatic intelligent cloud service testing tool | |
| WO2020248375A1 (en) | Method and system for synchronizing data between databases, computer device and storage medium | |
| CN110597918A (en) | Account management method and device and computer readable storage medium | |
| CN108512716B (en) | Method, system, computer device and storage medium for reporting device information | |
| CN111737227B (en) | Data modification method and system | |
| CN111611207B (en) | State data processing method and device and computer equipment | |
| CN112486915B (en) | Data storage method and device | |
| CN111177776A (en) | Multi-tenant data isolation method and system | |
| CN112035471B (en) | Transaction processing method and computer equipment | |
| CN114647698A (en) | Data synchronization method and device and computer storage medium | |
| CN110647463B (en) | Method and device for restoring test breakpoint and electronic equipment | |
| CN115421968A (en) | Data recovery method and electronic equipment | |
| CN112235124B (en) | Method and device for configuring pico-cell, storage medium and electronic device | |
| CN113254399A (en) | Log query method and device, electronic equipment and medium | |
| CN115242872B (en) | Data processing method, device, computer equipment and readable storage medium | |
| CN115858320A (en) | Operation log recording method, apparatus, medium and product | |
| CN100382506C (en) | Method for verifying network-unit server in network management system | |
| CN114330278A (en) | Method and equipment for judging consistency of returned data | |
| CN112783500B (en) | Method and device for generating compiling optimization information and electronic equipment | |
| CN114253441A (en) | Target function starting method and device, storage medium and electronic device | |
| CN112947991A (en) | Method and device for acquiring version difference code file, computer equipment and medium | |
| CN113347033A (en) | Root cause positioning method and system based on block chain and verification node |
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 |