CN108415814B - Method for automatically recording field change, application server and computer readable storage medium - Google Patents
Method for automatically recording field change, application server and computer readable storage medium Download PDFInfo
- Publication number
- CN108415814B CN108415814B CN201810026291.XA CN201810026291A CN108415814B CN 108415814 B CN108415814 B CN 108415814B CN 201810026291 A CN201810026291 A CN 201810026291A CN 108415814 B CN108415814 B CN 108415814B
- Authority
- CN
- China
- Prior art keywords
- field
- entity
- data
- change
- custom
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3476—Data logging
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a method for automatically recording field change, which comprises the following steps: analyzing a data structure, and marking a custom note in an entity field; monitoring field data operation; when the entity field marked with the custom note changes, acquiring a monitored data change record of the entity field marked with the custom note; and converting the change record of the entity class field marked with the custom note into a user readable form. The invention also provides an application server and a computer readable storage medium. The method for automatically recording the field change, the application server and the computer readable storage medium provided by the invention can realize the history record of the important field change by adding the custom comment, realize the readability of the user and greatly reduce the pressure of developers.
Description
Technical Field
The present invention relates to the field of data processing, and in particular, to an automatic field change recording method, an application server, and a computer-readable storage medium.
Background
Data plays an irreplaceable role in an information system as a core element of the information system, and is the most basic prerequisite for other functions of the information system, and thus, recording changes of data becomes particularly important. At present, there are two main ways to record the change history of data: firstly, the method records in an application program, but needs to increase a lot of codes, and increases the burden of developers; and secondly, trigger records are used in a database, but the information is difficult to be read by a user, so that the system is difficult to deploy and transplant.
Disclosure of Invention
In view of the above, the present invention provides an automatic record field change method, an application server and a computer readable storage medium, so as to solve the problem how to avoid increasing a lot of codes or using trigger records in a database when recording data in an application program, and the data records are difficult to be readable by a user.
Firstly, in order to achieve the above object, the present invention provides a method for automatically recording field changes, which comprises the steps of:
analyzing a data structure, and marking a custom note in an entity field;
monitoring field data operation;
when the entity field marked with the custom note changes, acquiring a monitored data change record of the entity field marked with the custom note;
and converting the change record of the entity class field marked with the custom note into a user readable form.
Optionally, the step of analyzing the data structure and marking a custom note in the entity field specifically includes:
by adding a custom note @ loggap to an entity field, note that the field needs to record the change history.
Optionally, the step of monitoring data operation specifically includes the following steps:
establishing a listener;
accurately tracking modification of entity fields, change of entity association/cascade relation, entity field increase and entity field deletion through a monitor;
the value of the field before change and the value after change are recorded.
Optionally, the step of converting the data modification record into a user-readable form specifically includes:
the Readable form of itself is described by adding a custom note @ Readable to the entity class field.
Optionally, when it is monitored that the entity class data marked with the custom annotation changes, acquiring the monitored changed data record, further including the following steps:
when the monitored data changes, judging whether the data is entity class data marked with custom notes;
and if the changed data is not the entity class data marked with the custom annotation, not recording the change of the data.
In addition, in order to achieve the above object, the present invention further provides an application server, including a memory and a processor, where the memory stores an automatic record field change system operable on the processor, and the automatic record field change system, when executed by the processor, implements the following steps:
analyzing a data structure, and marking a custom note in an entity field;
monitoring field data operation;
when the entity field marked with the custom note changes, acquiring a monitored data change record of the entity field marked with the custom note;
and converting the change record of the entity class field marked with the custom note into a user readable form.
Optionally, the step of analyzing the data structure and marking a custom note in the entity field specifically includes:
adding a custom note @ Loggable in an entity field to indicate that the field needs to record change history;
the step of converting the data modification record into a user readable form specifically includes:
the Readable form of itself is described by adding a custom note @ Readable to the entity class field.
Optionally, the step of monitoring data operation specifically includes the following steps:
establishing a listener;
accurately tracking modification of entity fields, change of entity association/cascade relation, entity field increase and entity field deletion through a monitor;
the value of the field before change and the value after change are recorded.
Optionally, when it is monitored that the entity class data marked with the custom annotation changes, acquiring the monitored changed data record, further including the following steps:
when the monitored data changes, judging whether the data is entity class data marked with custom notes;
and if the changed data is not the entity class data marked with the custom annotation, not recording the change of the data.
Further, to achieve the above object, the present invention also provides a computer-readable storage medium storing an automatic record field change system, which is executable by at least one processor to cause the at least one processor to perform the steps of the automatic record field change method as described above.
Compared with the prior art, the automatic field change recording method, the application server and the computer readable storage medium provided by the invention have the advantages that firstly, a data structure is analyzed, and the entity field is marked with the custom annotation; then, monitoring field data operation; further, when the entity field marked with the custom note changes, acquiring a monitored data change record of the entity field marked with the custom note; and finally, converting the change record of the entity class field marked with the custom note into a user readable form. Therefore, the defects that in the prior art, a lot of codes are required to be added for recording in an application program, the burden of developers is increased or trigger records are used in a database, but the information is difficult to be read by a user, so that the deployment and the transplantation of the system are difficult are overcome, the change history of important fields can be recorded by adding custom notes, the user can be read, and the pressure of the developers is greatly reduced.
Drawings
FIG. 1 is a diagram of an alternative hardware architecture for an application server of the present invention;
FIG. 2 is a schematic diagram of program modules of a first embodiment of an automatic record field change system according to the present invention;
FIG. 3 is a schematic diagram of program modules of a second embodiment of an automatic record field change system according to the present invention;
FIG. 4 is a flowchart illustrating a first embodiment of a method for automatically recording field changes according to the present invention;
fig. 5 is a flowchart illustrating a second embodiment of an automatic recording field change method according to the present invention.
Reference numerals:
the implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention. 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 invention.
It should be noted that the description relating to "first", "second", etc. in the present invention is for descriptive purposes only and is not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In addition, technical solutions between various embodiments may be combined with each other, but must be realized by a person skilled in the art, and when the technical solutions are contradictory or cannot be realized, such a combination should not be considered to exist, and is not within the protection scope of the present invention.
Fig. 1 is a schematic diagram of an alternative hardware architecture of the application server 2 according to the present invention.
In this embodiment, the application server 2 may include, but is not limited to, a memory 11, a processor 12, and a network interface 13, which may be communicatively connected to each other through a system bus. It is noted that fig. 1 only shows the application server 2 with components 11-13, but it is to be understood that not all of the shown components are required to be implemented, and that more or fewer components may be implemented instead.
The application server 2 may be a rack server, a blade server, a tower server, or a rack server, and the application server 2 may be an independent server or a server cluster composed of a plurality of servers.
The memory 11 includes at least one type of readable storage medium including a flash memory, a hard disk, a multimedia card, a card type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a Read Only Memory (ROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), a Programmable Read Only Memory (PROM), a magnetic memory, a magnetic disk, an optical disk, etc. In some embodiments, the storage 11 may be an internal storage unit of the application server 2, such as a hard disk or a memory of the application server 2. In other embodiments, the memory 11 may also be an external storage device of the application server 2, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), or the like, provided on the application server 2. Of course, the memory 11 may also comprise both an internal storage unit of the application server 2 and an external storage device thereof. In this embodiment, the memory 11 is generally used for storing an operating system installed in the application server 2 and various types of application software, such as program codes of the automatic recording field changing system 200. Furthermore, the memory 11 may also be used to temporarily store various types of data that have been output or are to be output.
The processor 12 may be a Central Processing Unit (CPU), controller, microcontroller, microprocessor, or other data Processing chip in some embodiments. The processor 12 is typically used to control the overall operation of the application server 2. In this embodiment, the processor 12 is configured to run the program code stored in the memory 11 or process data, for example, run the automatic recording field changing system 200.
The network interface 13 may comprise a wireless network interface or a wired network interface, and the network interface 13 is generally used for establishing a communication connection between the application server 2 and other electronic devices.
The hardware structure and functions of the related devices of the present invention have been described in detail so far. Various embodiments of the present invention will be presented based on the above description.
First, the present invention provides an automatic record field change system 200.
Referring to fig. 2, a block diagram of a first embodiment of an automatic record field change system 200 according to the present invention is shown.
In this embodiment, the automatic record field change system 200 includes a series of computer program instructions stored on the memory 11, which when executed by the processor 12, may implement the automatic record field change operations of the embodiments of the present invention. In some embodiments, the automatic record field change system 200 may be divided into one or more modules based on the particular operations implemented by the portions of the computer program instructions. For example, in fig. 2, the automatic record field change system 200 can be divided into an annotation module 201, a listening module 202, an acquisition module 203, and a conversion module 204. Wherein:
the marking module 201 is used for analyzing the data structure and marking the self-defined notes in the entity field;
generally, there are two main ways to record the history of changes of data: one is to record in an application program, but many codes need to be added, which increases the burden of developers. And secondly, trigger records are used in a database, but the information is difficult to be read by a user, so that the system is difficult to deploy and transplant. Therefore, in this embodiment, in order to solve the above problem, the application server 2 marks some data (methods, classes, or variables) specified by adding annotations. Annotations are meta-programming instructions that do not affect the operation of the program, and are markers that are visible in the code.
Specifically, the application server 2 analyzes the data structure through the annotation module 201, determines the entity class field in which the change history needs to be recorded, and adds a custom note to the entity class field. In this embodiment, adding a custom note is realized by adding @ logable, which indicates that the entity needs to record history. It is understood that the annotation module 201 records the change history of the important entity class field only.
The monitoring module 202 is configured to monitor field data operations.
Specifically, the application server 2 monitors whether there is data operation information in real time through the monitoring module 202, such as operations of modifying an entity field, changing an entity association/concatenation relationship, adding an entity field, deleting an entity field, and the like.
In this embodiment, the monitoring module 202 establishes a listener Postupdate folder, monitors operations such as modification of an entity field, change of an entity association/cascade relationship, addition of an entity field, deletion of an entity field, and records a value before a field is changed and a value after the field is changed.
Please refer to the following codes, which are codes for establishing the listener in the embodiment, and it should be understood that the codes are only for better explaining the present invention and are not meant to be a limitation of the present invention.
The listener selects a PostInsterEventLister (event after insertion), a PostUpdateEventLister (event after update) and a PostDeleteEventLister (event after deletion) interface as a monitoring interface of the CRUD method, and does not influence the original code.
The obtaining module 203 is configured to obtain a monitored data change record of the entity field marked with the custom note when the entity field marked with the custom note changes;
specifically, when the monitoring module 203 monitors that the entity class field marked with the custom note changes, the application server 2 acquires the monitored changed data record through the acquiring module 203.
The conversion module 204 is configured to convert the change record of the entity class field labeled with the custom note into a user-readable form.
Specifically, in the prior art, operations such as modification of entity fields, change of entity association/cascade relationship, addition of entity fields, deletion of entity fields, etc. may be recorded in a database using a trigger, but these recorded information are difficult to be readable by a user, resulting in difficulty in deployment and migration of the system. Therefore, in this embodiment, the application server 2 converts the change record of the entity class field labeled with the custom note into a user-readable form through the conversion module 204. In this embodiment, the conversion module 204 adds a custom note @ Readable to the entity class field labeled with the custom note to describe a Readable form of the conversion module, so as to convert the data modification record into a user Readable form.
Through the program module 201 and 204, the automatic recording field change system 200 provided by the invention firstly analyzes the data structure and marks the custom annotation on the entity field; then, monitoring field data operation; further, when the entity field marked with the custom note changes, acquiring a monitored data change record of the entity field marked with the custom note; and finally, converting the change record of the entity class field marked with the custom note into a user readable form. Therefore, the defects that in the prior art, a lot of codes are required to be added for recording in an application program, the burden of developers is increased or trigger records are used in a database, but the information is difficult to be read by a user, so that the deployment and the transplantation of the system are difficult are overcome, the change history of important fields can be recorded by adding custom notes, the user can be read, and the pressure of the developers is greatly reduced.
Referring to fig. 3, a block diagram of a second embodiment of the automatic record field change system 200 according to the present invention is shown. In this embodiment, the automatic recording field change system 200 further includes a determination module 205 in addition to the labeling module 201, the monitoring module 202, the obtaining module 203, and the conversion module 204 in the first embodiment.
The determining module 205 is configured to determine whether the data is entity class data labeled with the custom annotation when it is monitored that the data changes.
Specifically, as can be seen from the above, in the first embodiment, the application server 2 listens to the field data operation through the listening module 202, but in the case that all the field data need to be recorded when changed, the server may be slow to run. Therefore, in this embodiment, when the monitoring module 202 monitors an operation with field data, that is, when the field data changes, the application server 2 determines, through the determining module 205, whether the changed field is an entity field marked with a custom note. If the changed field is an entity field marked with a custom note, the obtaining module 203 obtains the data change record monitored by the monitoring module 202. If the changed field is not the entity field marked with the custom note, the obtaining module 203 ignores the change information of the field data, that is, does not record the change of the data. The application server 2 ignores the data change information of the unimportant field by judging whether the changed field is marked with the entity field with the custom note, thereby reducing the system operation pressure of the server.
Through the program module 205, the system 200 for automatically recording field changes provided by the present invention can also determine whether the data is the entity type data marked with the custom note when monitoring that the data changes, and obtain the data change record if the changed field is the entity type field marked with the custom note. And if the changed field is not the entity field marked with the custom note, ignoring the change information of the field data, namely not recording the change of the data so as to reduce the operating pressure of the server.
In addition, the invention also provides an automatic field change recording method.
Fig. 4 is a schematic flow chart illustrating a first embodiment of the method for automatically recording a field change according to the present invention. In this embodiment, the execution order of the steps in the flowchart shown in fig. 5 may be changed and some steps may be omitted according to different requirements.
Step S501, analyzing a data structure, and marking a custom note on an entity field;
generally, there are two main ways to record the history of changes of data: one is to record in an application program, but many codes need to be added, which increases the burden of developers. And secondly, trigger records are used in a database, but the information is difficult to be read by a user, so that the system is difficult to deploy and transplant. Therefore, in this embodiment, in order to solve the above problem, the application server 2 marks some data (methods, classes, or variables) specified by adding annotations. Annotations are meta-programming instructions that do not affect the operation of the program, and are markers that are visible in the code.
Specifically, the application server 2 analyzes the data structure, determines the entity class field in which the change history needs to be recorded, and adds a custom note to the entity class field. In this embodiment, adding a custom note is realized by adding @ logable, which indicates that the entity needs to record history. It will be appreciated that the application server 2 only records the history of changes to important entity class fields.
Step S502, monitoring field data operation.
Specifically, the application server 2 monitors in real time whether there is data operation information, such as operations of modifying an entity field, changing an entity association/cascade relationship, adding an entity field, deleting an entity field, and the like.
In this embodiment, the application server 2 establishes a listener Postupdate folder, and monitors operations such as modification of an entity field, change of an entity association/cascade relationship, addition of an entity field, deletion of an entity field, and the like through the listener Postupdate folder, and records a value before a field is changed and a value after the field is changed.
Please refer to the following codes, which are codes for establishing the listener in the embodiment, and it should be understood that the codes are only for better explaining the present invention and are not meant to be a limitation of the present invention.
The listener selects a PostInsterEventLister (event after insertion), a PostUpdateEventLister (event after update) and a PostDeleteEventLister (event after deletion) interface as a monitoring interface of the CRUD method, and does not influence the original code.
Step S503, when the entity field marked with the custom note changes, acquiring the monitored data change record of the entity field marked with the custom note;
specifically, when the application server 2 monitors that the entity class field marked with the custom note changes, the application server 2 obtains the monitored changed data record.
Step S504, the change record of the entity field marked with the custom note is converted into a user readable form.
Specifically, in the prior art, operations such as modification of entity fields, change of entity association/cascade relationship, addition of entity fields, deletion of entity fields, etc. may be recorded in a database using a trigger, but these recorded information are difficult to be readable by a user, resulting in difficulty in deployment and migration of the system. Therefore, in this embodiment, the application server 2 converts the change record of the entity class field marked with the custom note into a user-readable form. In this embodiment, the application server 2 adds a custom note @ Readable to the entity class field labeled with the custom note to describe a Readable form of the application server, so as to convert the data modification record into a user Readable form.
Through the steps S501-S504, the method for automatically recording field changes provided by the invention comprises the steps of firstly analyzing a data structure and marking custom notes on entity fields; then, monitoring field data operation; further, when the entity field marked with the custom note changes, acquiring a monitored data change record of the entity field marked with the custom note; and finally, converting the change record of the entity class field marked with the custom note into a user readable form. Therefore, the defects that in the prior art, a lot of codes are required to be added for recording in an application program, the burden of developers is increased or trigger records are used in a database, but the information is difficult to be read by a user, so that the deployment and the transplantation of the system are difficult are overcome, the change history of important fields can be recorded by adding custom notes, the user can be read, and the pressure of the developers is greatly reduced.
Fig. 5 is a schematic flow chart illustrating a second embodiment of the method for automatically recording a field change according to the present invention. In this embodiment, the steps of the automatic recording field change method are similar to those of the first embodiment, except that the method further includes steps S603 and S605.
In this embodiment, the execution order of the steps in the flowchart shown in fig. 5 may be changed and some steps may be omitted according to different requirements.
Step S601, analyzing a data structure, and marking a custom note on an entity field;
step S602, a field data operation is monitored.
Specifically, the application server 2 monitors in real time whether there is data operation information, such as operations of modifying an entity field, changing an entity association/cascade relationship, adding an entity field, deleting an entity field, and the like.
In this embodiment, the application server 2 establishes a listener Postupdate folder, and monitors operations such as modification of an entity field, change of an entity association/cascade relationship, addition of an entity field, deletion of an entity field, and the like through the listener Postupdate folder, and records a value before a field is changed and a value after the field is changed.
Please refer to the following codes, which are codes for establishing the listener in the embodiment, and it should be understood that the codes are only for better explaining the present invention and are not meant to be a limitation of the present invention.
The listener selects a PostInsterEventLister (event after insertion), a PostUpdateEventLister (event after update) and a PostDeleteEventLister (event after deletion) interface as a monitoring interface of the CRUD method, and does not influence the original code.
Step S603, when it is monitored that the data is changed, determining whether the data is entity class data labeled with the custom note, if the changed field is the entity class field labeled with the custom note, executing step S604, and if the changed field is not the entity class field labeled with the custom note, jumping to execute step S605.
Step S604, when the entity field marked with the custom note changes, acquiring the monitored data change record of the entity field marked with the custom note.
And step S605, if the changed data is not the entity class data marked with the custom annotation, not recording the change of the data.
Specifically, as can be seen from the above, in the first embodiment, the application server 2 listens to the field data operation through the listening module 202, but in the case that all the field data need to be recorded when changed, the server may be slow to run. Therefore, in this embodiment, when the application server 2 monitors an operation with field data, that is, when the field data changes, the application server 2 determines whether the changed field is an entity field marked with a custom note. And if the changed field is the entity field marked with the custom note, the application server 2 monitors the data change record. If the changed field is not the entity field marked with the custom note, the application server 2 ignores the change information of the field data, that is, does not record the change of the data. The application server 2 ignores the data change information of the unimportant field by judging whether the changed field is marked with the entity field with the custom note, thereby reducing the system operation pressure of the server.
Step S606, converting the change record of the entity field marked with the custom note into a user readable form.
Through the steps S601-S606, the method for automatically recording field changes provided by the present invention can also determine whether the data is the entity type data marked with the custom note when the monitored data changes, and obtain the data change record if the changed field is the entity type field marked with the custom note. And if the changed field is not the entity field marked with the custom note, ignoring the change information of the field data, namely not recording the change of the data so as to reduce the operating pressure of the server.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (7)
1. An automatic recording field change method applied to an application server is characterized by comprising the following steps:
analyzing a data structure, marking a custom note @ Loggable in an entity field, and noting that the field needs to record a change history;
monitoring field data operation;
when the entity field marked with the custom note changes, acquiring a monitored data change record of the entity field marked with the custom note;
and converting the change record of the entity class field marked with the custom note into a user Readable form by adding the custom note @ Readable to the entity class field.
2. The method of claim 1, wherein the step of listening for field data operations comprises the steps of:
establishing a listener;
accurately tracking modification of entity fields, change of entity association/cascade relation, entity field increase and entity field deletion through a monitor;
the value of the field before change and the value after change are recorded.
3. The automatic record field change method according to any one of claims 1-2, wherein when the monitored entity class data marked with the custom annotation is changed, the monitored changed data record is obtained, further comprising the following steps:
when the monitored data changes, judging whether the data is entity class data marked with custom notes;
and if the changed data is not the entity class data marked with the custom annotation, not recording the change of the data.
4. An application server, comprising a memory, a processor, the memory having stored thereon an automatic record field change system operable on the processor, the automatic record field change system when executed by the processor implementing the steps of:
analyzing a data structure, marking a custom note @ Loggable in an entity field, and noting that the field needs to record a change history;
monitoring field data operation;
when the entity field marked with the custom note changes, acquiring a monitored data change record of the entity field marked with the custom note;
and converting the change record of the entity class field marked with the custom note into a user Readable form by adding the custom note @ Readable to the entity class field.
5. The application server of claim 4, wherein the step of listening for field data operations comprises the steps of:
establishing a listener;
accurately tracking modification of entity fields, change of entity association/cascade relation, entity field increase and entity field deletion through a monitor;
the value of the field before change and the value after change are recorded.
6. The application server according to any one of claims 4-5, wherein when the entity class data marked with the custom annotation is monitored to be changed, the monitored changed data record is obtained, further comprising the following steps:
when the monitored data changes, judging whether the data is entity class data marked with custom notes;
and if the changed data is not the entity class data marked with the custom annotation, not recording the change of the data.
7. A computer-readable storage medium storing an automatic record field change system executable by at least one processor to cause the at least one processor to perform the steps of the automatic record field change method according to any one of claims 1-3.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810026291.XA CN108415814B (en) | 2018-01-11 | 2018-01-11 | Method for automatically recording field change, application server and computer readable storage medium |
| PCT/CN2018/089723 WO2019136914A1 (en) | 2018-01-11 | 2018-06-03 | Method for automatically recording field change, application server and computer-readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810026291.XA CN108415814B (en) | 2018-01-11 | 2018-01-11 | Method for automatically recording field change, application server and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108415814A CN108415814A (en) | 2018-08-17 |
| CN108415814B true CN108415814B (en) | 2021-02-19 |
Family
ID=63125527
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810026291.XA Active CN108415814B (en) | 2018-01-11 | 2018-01-11 | Method for automatically recording field change, application server and computer readable storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN108415814B (en) |
| WO (1) | WO2019136914A1 (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112051985B (en) * | 2020-07-23 | 2023-07-25 | 北京奇艺世纪科技有限公司 | Event triggering method, device, electronic equipment and readable storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102096623A (en) * | 2009-12-14 | 2011-06-15 | 深圳速浪数字技术有限公司 | Operation log generation method, server and business operational support system |
| CN102270225A (en) * | 2011-06-28 | 2011-12-07 | 用友软件股份有限公司 | Data change log monitoring method and device |
| CN105095056A (en) * | 2015-08-14 | 2015-11-25 | 焦点科技股份有限公司 | Method for monitoring data in data warehouse |
| CN107346277A (en) * | 2017-06-29 | 2017-11-14 | 东软集团股份有限公司 | Date storage method and device |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9143881B2 (en) * | 2010-10-25 | 2015-09-22 | At&T Intellectual Property I, L.P. | Providing interactive services to enhance information presentation experiences using wireless technologies |
| CN104063409B (en) * | 2013-04-11 | 2016-03-16 | 腾讯科技（深圳）有限公司 | A kind of field of database increases method and system |
| CN107193821B (en) * | 2016-03-14 | 2021-07-13 | 创新先进技术有限公司 | Monitoring method and system |
-
2018
- 2018-01-11 CN CN201810026291.XA patent/CN108415814B/en active Active
- 2018-06-03 WO PCT/CN2018/089723 patent/WO2019136914A1/en active Application Filing
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102096623A (en) * | 2009-12-14 | 2011-06-15 | 深圳速浪数字技术有限公司 | Operation log generation method, server and business operational support system |
| CN102270225A (en) * | 2011-06-28 | 2011-12-07 | 用友软件股份有限公司 | Data change log monitoring method and device |
| CN105095056A (en) * | 2015-08-14 | 2015-11-25 | 焦点科技股份有限公司 | Method for monitoring data in data warehouse |
| CN107346277A (en) * | 2017-06-29 | 2017-11-14 | 东软集团股份有限公司 | Date storage method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108415814A (en) | 2018-08-17 |
| WO2019136914A1 (en) | 2019-07-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110069925B (en) | Software monitoring method, system and computer readable storage medium | |
| CN105045676B (en) | A kind of restoration methods of the loss data based on SQLite databases | |
| CN112486915B (en) | Data storage method and device | |
| CN112860662B (en) | Automatic production data blood relationship establishment method, device, computer equipment and storage medium | |
| CN112328631A (en) | Production fault analysis method and device, electronic equipment and storage medium | |
| CN112631924A (en) | Automatic testing method and device, computer equipment and storage medium | |
| CN110958292A (en) | File uploading method, electronic device, computer equipment and storage medium | |
| CN112416957A (en) | Data increment updating method and device based on data model layer and computer equipment | |
| CN113448862A (en) | Software version testing method and device and computer equipment | |
| CN110716804A (en) | Method and device for automatically deleting useless resources, storage medium and electronic equipment | |
| CN109388617B (en) | Method and device for judging reliability of file timestamp | |
| CN109871593B (en) | Information inheritance method and device based on BIM platform and storage device | |
| CN110866834A (en) | Batch processing program execution method and system | |
| CN108415814B (en) | Method for automatically recording field change, application server and computer readable storage medium | |
| CN108984757A (en) | A kind of data lead-in method and equipment | |
| CN110515792B (en) | Monitoring method and device based on web version task management platform and computer equipment | |
| CN111078529B (en) | Client writing module testing method and device and electronic equipment | |
| CN110287182B (en) | Big data comparison method, device, equipment and terminal | |
| CN106934041B (en) | image file management method and device | |
| CN114143308A (en) | File uploading information processing method and device, computer equipment and storage medium | |
| CN114416420A (en) | Equipment problem feedback method and system | |
| CN112308098B (en) | Image processing method and device | |
| CN111352917A (en) | Information input method and device, electronic equipment and storage medium | |
| CN113595762A (en) | Network card configuration storage method and device | |
| CN110781146A (en) | Event storage method, power terminal and computer-readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |