CN101552701B - Method, system and device for recording parameter maintenance variation - Google Patents
Method, system and device for recording parameter maintenance variation Download PDFInfo
- Publication number
- CN101552701B CN101552701B CN2008100897238A CN200810089723A CN101552701B CN 101552701 B CN101552701 B CN 101552701B CN 2008100897238 A CN2008100897238 A CN 2008100897238A CN 200810089723 A CN200810089723 A CN 200810089723A CN 101552701 B CN101552701 B CN 101552701B
- Authority
- CN
- China
- Prior art keywords
- parameter
- change
- data
- type
- entity
- 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.)
- Expired - Fee Related
Links
Images
Abstract
An embodiment of the invention discloses a method, a system and a device for recording parameter maintenance variation. The method comprises the following steps: obtaining parameter maintenance variation information; reading metadata of the parameter type according to parameter types in the parameter maintenance variation information, and obtaining the parameter configuration information of the parameter types; generating service variation item objects and entity variation item objects according to the parameter maintenance variation information and the parameter configuration information, andgenerating field variation item objects by a conventional data comparing method; and generating parameter datasheet data and journaling datasheet data according to the parameter service variation ite m objects, the entity variation item objects and the field variation item objects. The embodiment of the invention realizes the maintenance functions of all parameter data by a mode of reading the parameter metadata and automatically records journals, thereby reducing the development workload.
Description
Technical field
The present invention relates to communication technical field, particularly relate to a kind of method, system and device of recording parameter maintenance variation.
Background technology
Most software systems generally all can have one or more parameter maintenance class subsystems.Parameter maintenance be to one or more tables of data increase, deletion, modification, query manipulation.Because the maintenance of parameter is mainly undertaken by manual work, the probability that makes a mistake is than higher.Yet the effect of parameter is very crucial, the wrong accuracy that can influence the whole system operation occurs.So, be necessary very much the change daily record of recording parameters, get off relevant information records such as the value before and after the data change, change time, alter operation person, be convenient to check and the recovery of data afterwards.Thereby improve stability, fail safe and the restorability of the integral body of system.
Though record change daily record implements and do not have the complicated technology difficulty when revising supplemental characteristic, workload is bigger, and the maintenance module of each type parameter all needs exploitation separately, and human cost is higher, also influences the stability of system.
The processing procedure of the prior art relevant with the present invention such as Fig. 1 comprise:
The details of step S101, operator query argument data D at the system operation interface, trigger parameter data D maintenance module is to data base querying parameter D and be presented on the system operation interface; The supplemental characteristic D that is presented on the system operation interface is made up of n element, be respectively D1, D2, D3 ... Dn;
Step S102, operator are at formation element D1 and the D2 of system operation interface modification supplemental characteristic D, and the system operation interface is submitted to supplemental characteristic D maintenance module to the forward and backward supplemental characteristic D of change through the mode of data object;
Step S103, supplemental characteristic D maintenance module through the n section independently code relatively change n corresponding data element of two forward and backward supplemental characteristic objects respectively, ultimate analysis goes out data element D1, change has taken place D2;
Step S104, supplemental characteristic D maintenance module are revised data element D1, the D2 of supplemental characteristic D in the database, the daily record of record data change simultaneously.
The inventor finds that there is following shortcoming in this prior art:
When 1, submitting at the system operation interface, each data element (field) of supplemental characteristic all needs one section independently to analyze relatively code, and being used for relatively, whether this element change has taken place;
2, each type supplemental characteristic all needs a corresponding parameters data maintenance module to be responsible for corresponding data change processing;
3, the modification of the additions and deletions of the data element of composition parameter data and data element attribute (like data type etc.) all need be revised the realization code, all need code be recompilated and issue;
This solution development workload is bigger, and one type of supplemental characteristic of every increase all will be developed a corresponding parameters data maintenance module, thereby causes the stability of system and autgmentability relatively poor.
Summary of the invention
The problem that the embodiment of the invention will solve provides a kind of extendible general parameter data maintaining method, dynamically realizes the maintenance function of all supplemental characteristics, also automatic log through the mode that reads the parameter metadata, to reduce development workload.
For achieving the above object, the embodiment of the invention proposes a kind of method of recording parameter maintenance variation on the one hand, may further comprise the steps:
Maintenance variation information gets parms;
Read the metadata of said parameter type according to the parameter type in the said parameter maintenance variation information, obtain the parameter configuration of said parameter type;
Generate parameter business change item object, Entity Change item object according to said parameter maintenance variation information and said parameter configuration, and generate a field change object through the conventional data comparative approach; Said conventional data comparative approach comprises at least a among the following method: the date type comparative approach; The character types comparative approach; The numeric type comparative approach;
Generate parametric data table data and daily record data table data according to said parameter business change item object, Entity Change item object and a field change object.
The embodiment of the invention also proposes a kind of system of recording parameter maintenance variation on the one hand, comprising:
The metadata resolution component is used to the maintenance variation information that gets parms, and reads the metadata of said parameter type according to the parameter type in the said parameter maintenance variation information, obtains the parameter configuration of said parameter type;
A change object formation component is used for generating parameter business change item object, Entity Change item object according to said parameter maintenance variation information and said parameter configuration, and generates a field change object through the conventional data comparative approach; Said conventional data comparative approach comprises at least a among the following method: the date type comparative approach; The character types comparative approach; The numeric type comparative approach;
The logdata record assembly is used for generating daily record data table data according to said parameter business change item object, Entity Change item object and a field change object;
The supplemental characteristic record component is used for generating the parametric data table data according to said parameter business change item object, Entity Change item object and a field change object.
This system also comprises schedule component, is used to dispatch said metadata resolution component, a change object formation component, logdata record assembly and/or the collaborative completion of supplemental characteristic record component supplemental characteristic attended operation, and the recording operation daily record.
Wherein, said metadata resolution component comprises: receiver module is used for receiving the parameter type information of said parameter maintenance variation information; Read module is used for reading according to the parameter type information that said receiver module receives the metadata of said parameter type, obtains the parameter configuration of said parameter type; Sending module is used to send the parameter configuration of the said parameter type that said read module obtains.
A said change object formation component comprises: business change item object generation module is used for generating parameter business change item object according to said parameter maintenance variation information and said parameter configuration; Entity Change item object generation module is used for generating Entity Change item object according to said parameter maintenance variation information and said parameter configuration; A field change object generation module is used for according to said parameter maintenance variation information and said parameter configuration and passes through the conventional data comparative approach generating a field change object.
The technical scheme of the embodiment of the invention has the following advantages:
Dynamically realize the maintenance function of all supplemental characteristics through the mode that reads the parameter metadata, log has reduced development workload automatically.
Description of drawings
Fig. 1 is the schematic flow sheet of the present invention's modification supplemental characteristic of the prior art;
Fig. 2 is the system configuration sketch map of the recording parameter maintenance variation in the embodiment of the invention;
Fig. 3 is the workflow sketch map of the change item object maker assembly in the embodiment of the invention;
Fig. 4 be in the embodiment of the invention business diary tables of data, entity daily record data table, field daily record data table concern sketch map;
Fig. 5 is a retouching operation schematic flow sheet in the parameter maintenance variation in the embodiment of the invention;
Fig. 6 is the data flow diagram of the parameter maintenance variation system in the embodiment of the invention;
Fig. 7 is the method flow sketch map of the recording parameter maintenance variation daily record in the embodiment of the invention.
Embodiment
The embodiment of the invention provides a kind of method, system and device of maintenance parameters data.
Below in conjunction with accompanying drawing and embodiment, specific embodiments of the invention describes in further detail:
Fig. 2 is the system configuration sketch map of the recording parameter maintenance variation in the embodiment of the invention; As shown in the figure; Wherein parametric data table is exactly to be used for the general designation of tables of data of stored parameter data in the software systems, for example data dictionary table, operator's definition list, system actor definition list, type of service definition list etc.The system operation interface is meant and each type parametric data table corresponding parameters data maintenance interface, and what supply that the operator realizes supplemental characteristic increases, deletes, changes, looks into operation.
And directly do not get in touch between system operation interface and the parametric data table; The schedule component of system is submitted in just be the operator on the interface at the system operation interface to supplemental characteristic change; Dispatch other system component again by schedule component; Finally be submitted to parametric data table to the modification information of supplemental characteristic, and arrive the daily record data table to operation log recording.
The function of each functional unit is described below in the embodiment of the invention system shown in Figure 2:
System operation interface 1: be used to gather user's parameter maintenance variation information, said parameter maintenance variation information is sent to schedule component.Promptly gathering the user needs the change supplemental characteristic of (containing increase, modification, deletion), and information such as the supplemental characteristic object (parameter class instance) before and after being configured to revise, action type, parameter type coding, operator's coding are submitted to schedule component;
Schedule component 2: the said metadata resolution component of parameter maintenance variation message scheduling, a change object formation component, logdata record assembly and/or the supplemental characteristic record component that are used for submitting to according to system operation interface 1 are worked in coordination with and are accomplished the supplemental characteristic attended operation, and the recording operation daily record.
Metadata resolution component 3: be used to the maintenance variation information that gets parms, read the metadata of said parameter type, obtain the parameter configuration of said parameter type according to the parameter type in the said parameter maintenance variation information.After obtaining these parameter configuration (attribute information) are returned to schedule component 2.
Wherein metadata resolution component 3 comprises: receiver module 31 is used for receiving the parameter type information of said parameter maintenance variation information; Read module 32 is used for reading according to the parameter type information that said receiver module 31 receives the metadata of said parameter type, obtains the parameter configuration of said parameter type; Sending module 33 is used to send the parameter configuration of the said parameter type that said read module 32 obtains.
Wherein metadata mainly comprises the following aspects for describing the attribute information of all parameters:
Parameter type coding, title;
Constitute the tables of data of parameter, promptly parameter current is made up of several tables of data;
Parameter list information: table name, major key field information, list of fields, corresponding parameters class name information;
Parameter list field information: field title, field type, precision, corresponding parameter generic attribute sequence number;
Wherein the reference content of XML file and form are following:
<ROOT>
< parameter type >
<parameter type coding>PARA_ID</parameter type coding>
<parameter type Ming Cheng>PARA_NAME</parameter type Ming Cheng>
<tables of data >
<table name Cheng>TAB_NAME</table name Cheng>
<parameter class title; CLASS_NAME </>parameter class title;
<zhu Jian>FLD_ID1</Zhu Jian>
<zhu Jian>FLD_ID2</Zhu Jian>
< field >
<ming Cheng>FLD_ID</Ming Cheng>
<can Shuoleixing>FLD_DATATYPE</Can Shuoleixing>
<corresponding parameter generic attribute Ming Cheng>CLS_ATTR_NAME</corresponding parameter generic attribute Ming Cheng>
<corresponding parameter generic attribute Xu Hao>CLS_ATTR_ID</corresponding parameter generic attribute Xu Hao>
<jing Du>PRECISION</Jing Du>
</Zi Duan>
</Shuo Jubiao>
<tables of data >
<table name Cheng>TAB_NAME</table name Cheng>
</Shuo Jubiao>
</Can Shuoleixing>
< parameter type >
</Can Shuoleixing>
<ROOT>
The key message of allocation list was following when the carrier of metadata was tables of data:
The parameter type allocation list:
| Sequence number | Title | Data type | Major key/ |
|
| 1 | The parameter type coding | | Major key | |
| 2 | The parameter type title | Character | ? |
Parameter list information configuration table:
| Sequence number | Title | Data type | Major key/ |
| 1 | The parameter type coding | Character | Major key/ |
| 2 | Table name | Character | Major key |
| 3 | The table Chinese name | Character | ? |
| ? | ? | ? | ? |
Parameter list field information allocation list:
| Sequence number | Title | Data type | Major key/ |
| 1 | Table name | Character | Major key/ |
| 2 | The field title | Character | Major key |
| ?3 | Field title Chinese name | Character | ? |
| ?4 | Field type | Character | ? |
| ?5 | Precision | Character | ? |
| ?6 | Major key whether | Numeral | ? |
A change object maker assembly 4: be used for generating business change item object, Entity Change item object, and generate a field change object through the conventional data comparative approach according to said parameter maintenance variation information and said parameter configuration.As shown in Figure 2, a change object formation component 4 comprises: business change item object generation module 41 is used for generating business change item object according to parameter maintenance variation information and parameter configuration; Entity Change item object generation module 42 is used for generating Entity Change item object according to said parameter maintenance variation information and said parameter configuration; A field change object generation module 43 is used for according to said parameter maintenance variation information and said parameter configuration and passes through the conventional data comparative approach generating a field change object.Concrete function is described below:
The parameter metadata that receiving scheduling assembly 2 imports into (being provided by the metadata resolution component), the supplemental characteristic object of revising front and back and action type (increase, delete, revise) (being provided by system operation interface 1) generate accordingly and return to schedule component 2 behind the change item class object.
The execution flow process of this assembly is as shown in Figure 3:
Obtain information creating business change item object, Entity Change item object and a field change object such as information such as operator, parameter type, action type, the supplemental characteristic object after before changing and metadata from schedule component 2.
Each operation change object maker assembly 4 all can be created a corresponding service change object, and only can create one.
Each operation change object maker assembly 4 can be created the Entity Change item object of a correspondence for each parametric data table that data change has taken place.At least create one at every turn, can not surpass the number of parameter list at most.Constitute by data dictionary group definition list and two tables of data dictionary item definition list such as the data dictionary parameter; Revising the data dictionary parameter so at every turn and at most only can create two Entity Change item objects, is respectively a data dictionary group object change object and data dictionary item Entity Change item object.
Each operation change object maker assembly 4 can be created a field change object of a correspondence for each field of parametric data table that data change has taken place; At least create one at every turn, can not surpass the summation of all relevant parameter literary name section numbers at most.
A change object maker assembly 4 is divided into date type, numeric type, three kinds big classes of character type to the data type of generic attribute (literary name section); And three kinds of corresponding with it general data comparing methods have been designed; The data type of setting in metadata according to each field is then called suitable comparative approach and is compared; Judge whether each field before and after revising change has taken place, thereby avoided writing the problem of comparison code for each attribute.
Illustrate with the data dictionary parameter below:
The data dictionary parameter is made up of two tables of data: data dictionary group definition list and data dictionary item definition list, and data dictionary item definition list is the sublist of data dictionary group definition list, its pass list structure is following:
Data dictionary group definition list:
| Sequence number | Title | Data type | Major key/ |
|
| 1 | The dictionary group coding | | Major key | |
| 2 | The field groups title | Character | ? |
Data dictionary item definition list:
| Sequence number | Title | Data type | Major key/ |
| 1 | The dictionary group coding | Character | Major key/ |
| 2 | Dictionary item coding | Character | Major key |
| 3 | Dictionary item title | Character | ? |
For example " sex " is a dictionary group, and it is a record in the data dictionary group definition list; " man ", " woman " are the dictionary items, and they are respectively records in the data dictionary item definition list.
Increase operation: the operator adds " sex " dictionary group at the system operation interface, and to have added " sex " be the data dictionary of " man ".Change object maker assembly can be created the field daily record object of a business change item object, two each and every one Entity Change item objects and two correspondences so.
Retouching operation: the operator at the system operation interface modification dictionary item of " sex " dictionary group, change " man " to " man " into.A change object maker assembly can be created the field daily record object of a business diary object, an entity daily record object and a correspondence.
Deletion action: similar with retouching operation, because the unactual deletion reference record of deletion action, but the mode field of modification data, it is invalid to be changed to these data, so can be regarded as deletion action a kind of special circumstances of retouching operation.
Logdata record assembly 5: be used for generating daily record data table data according to said parameter business change item object, Entity Change item object and a field change object.Comprise:
The change item object that receiving scheduling assembly 2 imports into (business change item object, Entity Change item object and a field change object); Through resolving a change object and metadata; Dynamic construction and execution SQL statement, and the supplemental characteristic and the operation information thereof that carry in the change object are updated in the daily record data table.Wherein the daily record data table is used for depositing the tables of data data of all supplemental characteristic operating process, is made up of three tables: business diary tables of data data, entity daily record data table data and field daily record data table data.
Business diary tables of data data: be used for writing down each type supplemental characteristic and when operated by which operator; Its main information has: information such as parameter type title, parameter type coding, operating time, operator's coding, operator unit are used to write down the parameter operation information that data change takes place with its corresponding service log sheet.
Entity daily record data table data: be the sublist of business diary tables of data data, the parametric data table data (the primary parameter maintenance variation possibly only revised some sublists of such parameter) of change take place in record; Its main information has: tables of data title, action type, major key field title, Major key, the entity log sheet corresponding with it are used to write down the parametric data table data message that data change takes place, and can directly locate the relevant parameters record through major key.
Field daily record data table: be the sublist of entity daily record data table, the field information (the primary parameter maintenance variation possibly only revised certain several field of some sublists of such parameter) of the parametric data table data of change takes place in record; Its main information has: value, modification back value before field title, the modification, the field log sheet corresponding with it is used to write down the field information that data change takes place.
In other words be exactly: when who to which kind of parameter operates business diary tables of data record; Entity daily record data table record has been made what operation (add, delete, revise) to which table; Field daily record data table record has been done alter operation to which field of these several tables, and value before the record modification and modification value afterwards.The relation of business diary tables of data, entity daily record data table and field daily record data table is as shown in Figure 4; Wherein business diary tables of data record wall scroll or many said entity daily record data table data, entity daily record data table record wall scroll or many field daily record data table data.
Supplemental characteristic record component 6: be used for generating the parametric data table data according to said parameter business change item object, Entity Change item object and a field change object.Comprise:
The change item object that receiving scheduling assembly 2 imports into (business change item object, Entity Change item object and a field change object); Through resolving a change object and metadata; Dynamic construction and execution SQL statement, and the supplemental characteristic that carries in the change object is updated in the relevant parameters tables of data.
Wherein parametric data table is meant a series of tables of data data that are used for depositing supplemental characteristic in the operation system database; Each type parameter can be made up of a parameter list; Also can constitute by a plurality of parameter lists; The data dictionary table that for example almost all can use in each software systems, operator person's table, role definition table, menu sheet etc., the data dictionary table can be made up of data dictionary group definition list and data dictionary item definition list again.
The interaction flow of each parts is as shown in Figure 5, may further comprise the steps:
Step S501, the operator is 1 input inquiry condition at the system operation interface, inquires about a certain type of supplemental characteristic.
Step S502, system operation interface 1 call parameters enquiry module are presented on the system operation interface after the query argument data in the database, and this metadata cache in parameter class object (type instance).
Step S503, operator revise the supplemental characteristic that inquires and submit retouching operation on system operation interface 1.
Step S504, the supplemental characteristic object before and after encode the operator, revise at the system operation interface, parameter type, action type (as revising, add, deleting) are submitted to schedule component 2.
Step S505, schedule component 2 is called metadata resolution component 3, imports the parameter type that submit at the system operation interface into, extracts the parameter current metadata by metadata resolution component 3, obtains relevant parameter list configuration information.
Step S506; Schedule component 2 passes to a change object maker assembly 4 to the supplemental characteristic object before and after the metadata of parameter and the modification, creates a corresponding business change class object, Entity Change item class object and a field change item class object by a change item object maker assembly 4.Wherein which operator business change item class object has mainly comprised and when has done what business; Entity Change item class object has comprised has made any operation (modification) to which parameter list; And the major key information of every table; A field change class object mainly representes to have revised which field of parameter list, the value before and after field is revised.
Step S507; As input, recall parameter data record component 6 is by the information that provides in this analyzing component change class object the change item class object of step S506 establishment for schedule component 2; Automatically generate and carry out SQL statement, be submitted to parameter list to the parameter information of change.
Step S508, schedule component 2 as input, is called logdata record assembly 5 to a change class object, the information by providing in this analyzing component change class object generates and carries out SQL statement automatically, the Operation Log data record in the daily record data table.
Step S509, schedule component 2 returns to system operation interface 1 operating result, is presented on the interface by system operation interface 1.
Above flow process introduction be that retouching operation, deletion action flow process are identical with it; Increasing operation does not have the query manipulation sub-process in the above flow process, and other flow process and retouching operation are basic identical, and just the flow process of change item object maker component internal and retouching operation, deletion action are variant.
Fig. 6 is the supplementary notes to Fig. 5, in the interaction flow of Fig. 5, has added concrete data flow, and idiographic flow and Fig. 5 are similar, repeat no more.
In sum, the method flow of the recording parameter maintenance variation in the embodiment of the invention comprises:
Step S701, maintenance variation information gets parms.
Step S702 reads the metadata of said parameter type according to the parameter type in the said parameter maintenance variation information, obtains the parameter configuration of said parameter type.
Step S703 generates business change item object, Entity Change item object according to said parameter maintenance variation information and said parameter configuration, and generates a field change object through the conventional data comparative approach.
Step S704 generates parametric data table data and daily record data table data according to said parameter business change item object, Entity Change item object and a field change object.
The technical scheme of the embodiment of the invention has the following advantages:
(1), realize safeguard (increase, modification, the deletion action) of supplemental characteristic, each type supplemental characteristic of being safeguarded can be a table, also can be made up of a plurality of correlation tables through easy configuration; The major key of each table can be single field, can be the associating major key also, avoids the development of a large amount of repeatability, increases work efficiency, and promotes software systems stability.
(2), through the attribute of adjustment configuration change supplemental characteristic, promptly for the supplemental characteristic of design attributes (like the parameter list list structure) change, also only need the corresponding configuration of adjustment to realize.
(3), except supplemental characteristic management, this method is professional fairly simple applicable to other also, to business datum simply increase, deletion, modification demand and need the functional module of recording operation daily record.
Therefore, the embodiment of the invention dynamically realizes the maintenance function of all supplemental characteristics through the mode that reads the parameter metadata, and log has reduced development workload automatically.
Through the description of above execution mode, those skilled in the art can be well understood to the present invention and can realize by the mode that software adds essential general hardware platform, can certainly pass through hardware.Based on such understanding; The part that technical scheme of the present invention contributes to prior art in essence in other words can be come out with the embodied of software product; This computer software product is stored in the storage medium, comprise some instructions with so that a station terminal equipment (can be mobile phone, personal computer; Server, the perhaps network equipment etc.) carry out the described method of each embodiment of the present invention.
The above only is a preferred implementation of the present invention; Should be pointed out that for those skilled in the art, under the prerequisite that does not break away from the principle of the invention; Can also make some improvement and retouching, these improvement and retouching also should be looked protection scope of the present invention.
Claims (12)
1. the method for a recording parameter maintenance variation is characterized in that, may further comprise the steps:
Maintenance variation information gets parms;
Read the metadata of said parameter type according to the parameter type in the said parameter maintenance variation information, obtain the parameter configuration of said parameter type;
Generate parameter business change item object, Entity Change item object according to said parameter maintenance variation information and said parameter configuration, and generate a field change object through the conventional data comparative approach; Said conventional data comparative approach comprises at least a among the following method: the date type comparative approach; The character types comparative approach; The numeric type comparative approach;
Generate parametric data table data and daily record data table data according to said parameter business change item object, Entity Change item object and a field change object.
2. the method for claim 1 is characterized in that, said parameter maintenance variation information comprises:
Supplemental characteristic object before and after revising, the operator's coding before and after revising, the parameter type before and after revising, and the action type before and after revising.
3. the method for claim 1 is characterized in that, saidly generates a field change object through the conventional data comparative approach and comprises:
Obtain and revise front and back object properties value;
Call at least a comparative approach among date type comparative approach, character types comparative approach and the numeric type comparative approach relatively judge said modification before and after the object properties value whether be modified, increase or delete;
Result according to said comparative approach comparison of calling generates a field change object.
4. the method for claim 1 is characterized in that, saidly generates daily record data table data according to said parameter business change item object, Entity Change item object and a field change object and comprises:
Generate business diary tables of data data according to said parameter business change item object;
Generate entity daily record data table data according to said Entity Change item object;
Generate field daily record data table data according to a said field change object.
5. method as claimed in claim 4 is characterized in that, said business diary tables of data record wall scroll or many said entity daily record data table data, said entity daily record data table record wall scroll or many said field daily record data table data.
6. the method for claim 1 is characterized in that, also comprises: through the attribute of adjustment configuration change supplemental characteristic.
7. the system of a recording parameter maintenance variation is characterized in that, comprising:
The metadata resolution component is used to the maintenance variation information that gets parms, and reads the metadata of said parameter type according to the parameter type in the said parameter maintenance variation information, obtains the parameter configuration of said parameter type;
A change object formation component is used for generating parameter business change item object, Entity Change item object according to said parameter maintenance variation information and said parameter configuration, and generates a field change object through the conventional data comparative approach; Said conventional data comparative approach comprises at least a among the following method: the date type comparative approach; The character types comparative approach; The numeric type comparative approach;
The logdata record assembly is used for generating daily record data table data according to said parameter business change item object, Entity Change item object and a field change object;
The supplemental characteristic record component is used for generating the parametric data table data according to said parameter business change item object, Entity Change item object and a field change object.
8. system as claimed in claim 7 is characterized in that, also comprises:
Schedule component, at least one assembly synergistic that is used to dispatch among said metadata resolution component, a change object formation component, logdata record assembly and the supplemental characteristic record component is accomplished supplemental characteristic attended operation, and the recording operation daily record.
9. system as claimed in claim 8 is characterized in that, also comprises:
The system operation interface is used to gather user's parameter maintenance variation information, and said parameter maintenance variation information is sent to schedule component.
10. system as claimed in claim 7 is characterized in that, said metadata resolution component comprises:
Receiver module is used for receiving the parameter type information of said parameter maintenance variation information;
Read module is used for reading according to the parameter type information that said receiver module receives the metadata of said parameter type, obtains the parameter configuration of said parameter type;
Sending module is used to send the parameter configuration of the said parameter type that said read module obtains.
11. system as claimed in claim 7 is characterized in that, a said change object formation component comprises:
Parameter business change item object generation module is used for generating parameter business change item object according to said parameter maintenance variation information and said parameter configuration;
Entity Change item object generation module is used for generating Entity Change item object according to said parameter maintenance variation information and said parameter configuration;
A field change object generation module is used for according to said parameter maintenance variation information and said parameter configuration and passes through the conventional data comparative approach generating a field change object.
12. system as claimed in claim 7 is characterized in that, said logdata record assembly comprises:
Parsing module is used for receiving and resolving said parameter business change item object, Entity Change item object and a field change object and metadata;
Dynamic construction and Executive Module; The field that is used for resolving according to said parsing module changes an object and metadata dynamic construction and execution architecture query language SQL statement, and the supplemental characteristic and the operation information that carry in parameter business change item object, Entity Change item object and the field change object are updated in the log sheet.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008100897238A CN101552701B (en) | 2008-04-03 | 2008-04-03 | Method, system and device for recording parameter maintenance variation |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008100897238A CN101552701B (en) | 2008-04-03 | 2008-04-03 | Method, system and device for recording parameter maintenance variation |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101552701A CN101552701A (en) | 2009-10-07 |
| CN101552701B true CN101552701B (en) | 2012-07-04 |
Family
ID=41156707
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2008100897238A Expired - Fee Related CN101552701B (en) | 2008-04-03 | 2008-04-03 | Method, system and device for recording parameter maintenance variation |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101552701B (en) |
Families Citing this family (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104699811B (en) * | 2015-03-23 | 2018-02-23 | 重庆广播电视大学 | A kind of no intrusive mood form data change record and the method and device of backtracking |
| CN104951565B (en) * | 2015-07-10 | 2018-07-24 | 上海斐讯数据通信技术有限公司 | XM (extensible messaging client) L (extensible markup language) configuration maintenance method and system based on memory database |
| CN107861712A (en) * | 2016-09-26 | 2018-03-30 | 平安科技（深圳）有限公司 | Develop the generation method and system of daily record |
| CN107491558B (en) * | 2017-09-08 | 2020-09-15 | 北京奇艺世纪科技有限公司 | Metadata updating method and device |
| CN107818178A (en) * | 2017-11-23 | 2018-03-20 | 郑州云海信息技术有限公司 | A kind of method of automatically generated data storehouse change SQL scripts |
| CN108200195B (en) * | 2018-01-31 | 2021-08-27 | 新华三技术有限公司 | Method and network equipment for upgrading ISSU data communication without interrupting service |
| CN108388462B (en) * | 2018-02-28 | 2021-04-27 | 武汉斗鱼网络科技有限公司 | Element change notification method and device and terminal equipment |
| CN108984377B (en) * | 2018-06-29 | 2022-03-08 | 深圳市同泰怡信息技术有限公司 | Method, system and medium for counting BIOS log |
| CN110399360A (en) * | 2019-07-26 | 2019-11-01 | 北京明略软件系统有限公司 | The setting method and device of dictionary table, storage medium, electronic device |
| CN110990406B (en) * | 2019-11-28 | 2023-07-14 | 中国建设银行股份有限公司 | Fuzzy query method, device, equipment and medium |
| CN113297202B (en) * | 2020-07-09 | 2024-03-08 | 阿里巴巴集团控股有限公司 | Data type change processing method and device |
| CN114327716A (en) * | 2021-12-27 | 2022-04-12 | 凌云光技术股份有限公司 | Method and system for generating local language operation log based on XML language |
| CN115657901B (en) * | 2022-10-20 | 2023-07-11 | 吉林银行股份有限公司 | Service changing method and device based on unified parameters |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1848760A (en) * | 2005-08-30 | 2006-10-18 | 华为技术有限公司 | Software assembly parameter configuration method, and system and terminal equipment thereof |
| CN101060645A (en) * | 2007-04-10 | 2007-10-24 | 华为技术有限公司 | A communication method, equipment and system |
| CN101093572A (en) * | 2007-07-20 | 2007-12-26 | 中国建设银行股份有限公司 | A preposition system and a centralized data processing system |
-
2008
- 2008-04-03 CN CN2008100897238A patent/CN101552701B/en not_active Expired - Fee Related
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1848760A (en) * | 2005-08-30 | 2006-10-18 | 华为技术有限公司 | Software assembly parameter configuration method, and system and terminal equipment thereof |
| CN101060645A (en) * | 2007-04-10 | 2007-10-24 | 华为技术有限公司 | A communication method, equipment and system |
| CN101093572A (en) * | 2007-07-20 | 2007-12-26 | 中国建设银行股份有限公司 | A preposition system and a centralized data processing system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101552701A (en) | 2009-10-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101552701B (en) | Method, system and device for recording parameter maintenance variation | |
| US20220292103A1 (en) | Information service for facts extracted from differing sources on a wide area network | |
| US20040255301A1 (en) | Context association schema for computer system architecture | |
| JP4795945B2 (en) | User interface for access control to computer objects | |
| US8407215B2 (en) | Text analysis to identify relevant entities | |
| EP1492003A2 (en) | Sharing computer objects with associations | |
| US6772137B1 (en) | Centralized maintenance and management of objects in a reporting system | |
| US8620946B2 (en) | Storage and searching of temporal entity information | |
| US20040254938A1 (en) | Computer searching with associations | |
| US20090125530A1 (en) | Hierarchy Nodes Derived Based on Parent/Child Foreign Key and/or Range Values on Parent Node | |
| CN102917009B (en) | A kind of stock certificate data collection based on cloud computing technology and storage means and system | |
| CN111767303A (en) | Data query method and device, server and readable storage medium | |
| CN106294374A (en) | The method of small documents merging and data query system | |
| US20230368091A1 (en) | Systems and methods for efficiently distributing alert messages | |
| CN105975489A (en) | Metadata-based online SQL code completion method | |
| CN111190965B (en) | Impromptu relation analysis system and method based on text data | |
| US7487183B1 (en) | Grouped filter rules for workflow application update notifications | |
| CN102724290B (en) | Method, device and system for getting target customer group | |
| Tannenbaum | Implementing a corporate repository: the models meet reality | |
| US8504592B2 (en) | Data organization tool and apparatus for remotely managing a meeting | |
| CN116185347A (en) | Automatic term complement requirement definition system based on intelligent keyword prompt | |
| CN117474465A (en) | Data management platform task configuration method, system, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20120704 Termination date: 20150403 |
|
| EXPY | Termination of patent right or utility model |