CN105005592B - Data dictionary generation method and data dictionary creation device - Google Patents
Data dictionary generation method and data dictionary creation device Download PDFInfo
- Publication number
- CN105005592B CN105005592B CN201510370318.3A CN201510370318A CN105005592B CN 105005592 B CN105005592 B CN 105005592B CN 201510370318 A CN201510370318 A CN 201510370318A CN 105005592 B CN105005592 B CN 105005592B
- Authority
- CN
- China
- Prior art keywords
- data dictionary
- data
- entity
- relationship
- entity object
- 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
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/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
- G06F16/288—Entity relationship models
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Document Processing Apparatus (AREA)
Abstract
The present invention proposes a kind of data dictionary generation method and device, wherein the method includes：According to the entity relationship in multiple entity objects, the multiple entity object between the attribute information and the multiple entity object of each entity object, multiple data dictionary format data of corresponding the multiple entity object are generated；The annotation information for adding multiple entity objects described in the multiple data dictionary format data, to form the data dictionary specification for including the annotation information；Data dictionary is generated according to the multiple data dictionary format data and the data dictionary specification.Technical solution through the invention, by using data base normalization data structure the characteristics of generate data dictionary, avoid the annotation information generation data dictionary for being completely dependent on entity object, and the difficulty for generating data dictionary is also reduced, to make the generation of data dictionary that there is operability.
Description
Technical field
The present invention relates to technical field of information processing, in particular to a kind of data dictionary generation method and data word
Allusion quotation generating means.
Background technology
Currently, in the products such as application software system, usually using relevant database depositing as software system data
Storage media, wherein software system data can be divided into two big module of system configuration data and operation flow data：System configuration number
According to the configurations and parameter run comprising system environments；Operation flow data：Including file data, flow data, flow are joined
The multiple business relation datas such as number.Often there are following characteristics in software system data：Clue, normalization and consistency.
In the related art, annotation information is added to entity object in relevant database in advance, then copies or exports
To in Excel into edlin to generate data dictionary, or by other methods data dictionary is directly generated from database, but
It is that the data dictionary of the relevant technologies is completely dependent on the annotation information of entity object.In addition, due to joining in the life cycle of product
The participant of research and development and later maintenance with product ignores annotation to the entity object in database or without forming annotation
Consciousness and custom, directly increase the difficulty for generating data dictionary and inoperable property in this way.
Therefore, how to avoid the annotation information for being completely dependent on entity object from generating data dictionary, while reducing generation data
The difficulty of dictionary, to make the generation of data dictionary that there is operability to become urgent problem to be solved.
Invention content
The present invention is based on the above problem, it is proposed that a kind of new technical solution makes full use of data base normalization
The characteristics of data structure, generates data dictionary, avoids the annotation information generation data dictionary for being completely dependent on entity object, and
And the difficulty for generating data dictionary is also reduced, to make the generation of data dictionary that there is operability.
In view of this, an aspect of of the present present invention proposes a kind of data dictionary generation method, including：According to multiple entities pair
As the entity in, the multiple entity object between the attribute information and the multiple entity object of each entity object closes
System generates multiple data dictionary format data of corresponding the multiple entity object；Add the multiple data dictionary format number
The annotation information of multiple entity objects described in, to form the data dictionary specification for including the annotation information；Root
Data dictionary is generated according to the multiple data dictionary format data and the data dictionary specification.
In the technical scheme, due to the participant of the research and development and the later maintenance that participate in product in the life cycle of product
Member updates and replaces often, therefore, by multiple data dictionary format data of multiple entity objects in the database of product and
Data dictionary specification generate data dictionary, not only allow participant according to data dictionary more fast with easily
Solve the database structure of product, the characteristics of also making full use of the data structure of data base normalization (multiple entities i.e. in database
Entity relationship in object, multiple entity objects between the attribute information and multiple entity objects of each entity object) next life
At data dictionary, the annotation information generation data dictionary for being completely dependent on entity object is avoided.
In the above-mentioned technical solutions, it is preferable that described according to each real in multiple entity objects, the multiple entity object
Entity relationship between the attribute information of body object and the multiple entity object generates corresponding the multiple entity pair respectively
It the step of multiple data dictionary format data of elephant, specifically includes：The multiple entity object, described every is obtained in the database
The entity relationship between the attribute information and the multiple entity object of a entity object；According to each reality
Body object, each entity object the attribute information and the multiple entity object between the entity relationship,
Define the data dictionary format rule of each entity object；According to each entity object described in the multiple entity object
The data dictionary format rule generate the multiple data dictionary format data.
In the technical scheme, according to multiple entity objects in database, the attribute information of each entity object and more
Entity relationship between a entity object defines the data dictionary format rule of each entity object, so as to according to data word
Allusion quotation format convention generates the data dictionary format data of each entity object, makes full use of the data structure of data base normalization
Feature avoids the annotation information generation data dictionary for being completely dependent on entity object.
In the above-mentioned technical solutions, it is preferable that multiple realities described in the multiple data dictionary format data of addition
It the step of annotation information of body object, specifically includes：It is arranged self-defined between user-defined the multiple entity object
Relationship；According to the entity relationship and the self-defined relationship pair between the principle of consent of the same name and the multiple entity object
The multiple data dictionary format data are compressed；It adds more described in compressed the multiple data dictionary format data
The annotation information of a entity object.
In the technical scheme, since there is also in addition to entity relationship between multiple entity objects in practical applications
Other relationships can efficiently reduce data dictionary specification by the self-defined relationship being arranged between multiple entity objects
Range, so as to more accurately and efficiently generate data dictionary.In addition, due to entity object annotation information there may be
It repeats, therefore, according to the entity relationship between the principle of consent of the same name and multiple entity objects with self-defined relationship to multiple data
Dictionary format data are compressed, to reduce the superfluous of annotation information while ensureing the data dictionary accuracy of production
It is remaining.
In the above-mentioned technical solutions, it is preferable that described according to the multiple data dictionary format data and the data word
Allusion quotation specification generates the step of data dictionary, specifically includes：According to the entity relationship between the multiple entity object
With the self-defined relationship, the annotation information in the data dictionary specification is written to the multiple data dictionary
In comments forms data in formatted data；According to the multiple data dictionary format data life for including the annotation information
At the data dictionary.
In the technical scheme, by the way that the annotation information in data dictionary specification is written to multiple data dictionary lattice
In comments forms data in formula data, and data dictionary is generated according to multiple data dictionaries with annotation information, makes participation
Personnel can according to data dictionary more fast with easily understand product database structure.
In the above-mentioned technical solutions, it is preferable that the multiple entity object includes：Physical table, view and function；And institute
Stating entity relationship includes：Relationship, the physical table between the physical table and the physical table and the pass between the view
System and the relationship between the view and the view.
In the technical scheme, multiple entity objects include but not limited to：Physical table, view and function, for example, entity pair
As can also be storing process, wherein the attribute information of physical table includes table name, sets of fields, major key, external key etc., the category of view
Property information includes view name, sets of fields etc., and the attribute information of function includes function name, parameter set, return value etc., storing process
Attribute information includes storing process name, parameter set etc..In addition, entity relationship includes but not limited to：Between physical table and physical table
Relationship, the relationship between physical table and view and the relationship between view and view, wherein between physical table and physical table
Relationship is embodied with foreign key constraint relationship in the database, the relationship between relationship and view and view between view and physical table
It is embodied in the database with connection relation in view query source.
Another aspect of the present invention proposes a kind of data dictionary generating means, including：First generation unit is used for basis
In multiple entity objects, the multiple entity object between the attribute information and the multiple entity object of each entity object
Entity relationship, generate multiple data dictionary format data of corresponding the multiple entity object；Processing unit, for adding
The annotation information for stating multiple entity objects described in multiple data dictionary format data includes the annotation information to be formed
Data dictionary specification；Second generation unit, for according to the multiple data dictionary format data and the data dictionary
Specification generates data dictionary.
In the technical scheme, due to the participant of the research and development and the later maintenance that participate in product in the life cycle of product
Member updates and replaces often, therefore, by multiple data dictionary format data of multiple entity objects in the database of product and
Data dictionary specification generate data dictionary, not only allow participant according to data dictionary more fast with easily
Solve the database structure of product, the characteristics of also making full use of the data structure of data base normalization (multiple entities i.e. in database
Entity relationship in object, multiple entity objects between the attribute information and multiple entity objects of each entity object) next life
At data dictionary, the annotation information generation data dictionary for being completely dependent on entity object is avoided.
In the above-mentioned technical solutions, it is preferable that first generation unit includes：Acquiring unit, in the database
Between the attribute information and the multiple entity object that obtain the multiple entity object, each entity object
The entity relationship；Definition unit, for the attribute information according to each entity object, each entity object
And the entity relationship between the multiple entity object, define the data dictionary format rule of each entity object
Then；First generation unit is specifically used for, according to the data of each entity object described in the multiple entity object
Dictionary format rule generates the multiple data dictionary format data.
In the technical scheme, according to multiple entity objects in database, the attribute information of each entity object and more
Entity relationship between a entity object defines the data dictionary format rule of each entity object, so as to according to data word
Allusion quotation format convention generates the data dictionary format data of each entity object, to make full use of the data knot of data base normalization
The characteristics of structure, avoids the annotation information generation data dictionary for being completely dependent on entity object.
In the above-mentioned technical solutions, it is preferable that the processing unit includes：Setting unit, for User Defined to be arranged
The multiple entity object between self-defined relationship；Compression unit, for according to the principle of consent of the same name and the multiple
The entity relationship between entity object compresses the multiple data dictionary format data with the self-defined relationship；
The processing unit is specifically used for, and adds multiple entity objects described in compressed the multiple data dictionary format data
The annotation information.
In the technical scheme, since there is also in addition to entity relationship between multiple entity objects in practical applications
Other relationships can efficiently reduce data dictionary specification by the self-defined relationship being arranged between multiple entity objects
Range, so as to more accurately and efficiently generate data dictionary.In addition, due to entity object annotation information there may be
It repeats, therefore, according to the entity relationship between the principle of consent of the same name and multiple entity objects with self-defined relationship to multiple data
Dictionary format data are compressed, to reduce the superfluous of annotation information while ensureing the data dictionary accuracy of production
It is remaining.
In the above-mentioned technical solutions, it is preferable that second generation unit is specifically used for：According to the multiple entity object
Between the entity relationship and the self-defined relationship, the annotation information in the data dictionary specification is written
Into the comments forms data in the multiple data dictionary format data, according to including the multiple of the annotation information
Data dictionary format data generate the data dictionary.
In the technical scheme, by the way that the annotation information in data dictionary specification is written to multiple data dictionary lattice
In comments forms data in formula data, and data dictionary is generated according to multiple data dictionaries with annotation information, makes participation
Personnel can according to data dictionary more fast with easily understand product database structure.
In the above-mentioned technical solutions, it is preferable that the multiple entity object includes：Physical table, view and function；And institute
Stating entity relationship includes：Relationship, the physical table between the physical table and the physical table and the pass between the view
System and the relationship between the view and the view.
In the technical scheme, multiple entity objects include but not limited to：Physical table, view and function, for example, entity pair
As can also be storing process, wherein the attribute information of physical table includes table name, sets of fields, major key, external key etc., the category of view
Property information includes view name, sets of fields etc., and the attribute information of function includes function name, parameter set, return value etc., storing process
Attribute information includes storing process name, parameter set etc..In addition, entity relationship includes but not limited to：Between physical table and physical table
Relationship, the relationship between physical table and view and the relationship between view and view, wherein between physical table and physical table
Relationship is embodied with foreign key constraint relationship in the database, the relationship between relationship and view and view between view and physical table
It is embodied in the database with connection relation in view query source.
Technical solution through the invention, by using data base normalization data structure the characteristics of generate data word
Allusion quotation avoids the annotation information generation data dictionary for being completely dependent on entity object, and also reduces the difficulty for generating data dictionary
Degree, to make the generation of data dictionary that there is operability.
Description of the drawings
Fig. 1 shows the flow diagram of data dictionary generation method according to an embodiment of the invention；
Fig. 2 shows the flow diagrams of the generation of data dictionary format data according to an embodiment of the invention；
Fig. 3 shows the flow diagram of the generation of data dictionary specification according to an embodiment of the invention；
Fig. 4 shows the flow diagram of data dictionary generation method according to another embodiment of the invention；
Fig. 5 shows the structural schematic diagram of data dictionary generating means according to an embodiment of the invention；
Fig. 6 shows the structural schematic diagram of data dictionary generating means according to another embodiment of the invention.
Specific implementation mode
It is below in conjunction with the accompanying drawings and specific real in order to be more clearly understood that the above objects, features and advantages of the present invention
Mode is applied the present invention is further described in detail.It should be noted that in the absence of conflict, the implementation of the application
Feature in example and embodiment can be combined with each other.
Many details are elaborated in the following description to facilitate a thorough understanding of the present invention, still, the present invention may be used also
To be implemented different from other modes described here using other, therefore, protection scope of the present invention is not by described below
Specific embodiment limitation.
Fig. 1 shows the flow diagram of data dictionary generation method according to an embodiment of the invention.
As shown in Figure 1, data dictionary generation method according to an embodiment of the invention, including：
Step 102, according to the attribute information of each entity object in multiple entity objects, the multiple entity object and
Entity relationship between the multiple entity object generates multiple data dictionary format numbers of corresponding the multiple entity object
According to；
Step 104, the annotation information for adding multiple entity objects described in the multiple data dictionary format data, with shape
At the data dictionary specification for including the annotation information；
Step 106, data word is generated according to the multiple data dictionary format data and the data dictionary specification
Allusion quotation.
In the technical scheme, due to the participant of the research and development and the later maintenance that participate in product in the life cycle of product
Member updates and replaces often, therefore, by multiple data dictionary format data of multiple entity objects in the database of product and
Data dictionary specification generate data dictionary, not only allow participant according to data dictionary more fast with easily
Solve the database structure of product, the characteristics of also making full use of the data structure of data base normalization (multiple entities i.e. in database
Entity relationship in object, multiple entity objects between the attribute information and multiple entity objects of each entity object) next life
At data dictionary, the annotation information generation data dictionary for being completely dependent on entity object is avoided.
In the above-mentioned technical solutions, it is preferable that step 102, specifically include：The multiple entity pair is obtained in the database
As, each entity object the attribute information and the multiple entity object between the entity relationship；According to
Each entity object, each entity object the attribute information and the multiple entity object between it is described
Entity relationship defines the data dictionary format rule of each entity object；According to every described in the multiple entity object
The data dictionary format rule of a entity object generates the multiple data dictionary format data.
In the technical scheme, according to multiple entity objects in database, the attribute information of each entity object and more
Entity relationship between a entity object defines the data dictionary format rule of each entity object, so as to according to data word
Allusion quotation format convention generates the data dictionary format data of each entity object, to make full use of the data knot of data base normalization
The characteristics of structure, avoids the annotation information generation data dictionary for being completely dependent on entity object.
In the above-mentioned technical solutions, it is preferable that multiple realities described in the multiple data dictionary format data of addition
It the step of annotation information of body object, specifically includes：It is arranged self-defined between user-defined the multiple entity object
Relationship；According to the entity relationship and the self-defined relationship pair between the principle of consent of the same name and the multiple entity object
The multiple data dictionary format data are compressed；It adds more described in compressed the multiple data dictionary format data
The annotation information of a entity object.
In the technical scheme, since there is also in addition to entity relationship between multiple entity objects in practical applications
Other relationships can efficiently reduce data dictionary specification by the self-defined relationship being arranged between multiple entity objects
Range, so as to more accurately and efficiently generate data dictionary.In addition, due to entity object annotation information there may be
It repeats, therefore, according to the entity relationship between the principle of consent of the same name and multiple entity objects with self-defined relationship to multiple data
Dictionary format data are compressed, to reduce the superfluous of annotation information while ensureing the data dictionary accuracy of production
It is remaining.
In the above-mentioned technical solutions, it is preferable that step 106, specifically include：According to the institute between the multiple entity object
Entity relationship and the self-defined relationship are stated, the annotation information in the data dictionary specification is written to described more
In comments forms data in a data dictionary format data；According to the multiple data dictionary for including the annotation information
Formatted data generates the data dictionary.
In the technical scheme, by the way that the annotation information in data dictionary specification is written to multiple data dictionary lattice
In comments forms data in formula data, and data dictionary is generated according to multiple data dictionaries with annotation information, makes participation
Personnel can according to data dictionary more fast with easily understand product database structure.
In the above-mentioned technical solutions, it is preferable that the multiple entity object includes：Physical table, view and function；And institute
Stating entity relationship includes：Relationship, the physical table between the physical table and the physical table and the pass between the view
System and the relationship between the view and the view.
In the technical scheme, multiple entity objects include but not limited to：Physical table, view and function, for example, entity pair
As can also be storing process, wherein the attribute information of physical table includes table name, sets of fields, major key, external key etc., the category of view
Property information includes view name, sets of fields etc., and the attribute information of function includes function name, parameter set, return value etc., storing process
Attribute information includes storing process name, parameter set etc..In addition, entity relationship includes but not limited to：Between physical table and physical table
Relationship, the relationship between physical table and view and the relationship between view and view, wherein between physical table and physical table
Relationship is embodied with foreign key constraint relationship in the database, the relationship between relationship and view and view between view and physical table
It is embodied in the database with connection relation in view query source.
Fig. 2 shows the flow diagrams of the generation of data dictionary format data according to an embodiment of the invention.
As shown in Fig. 2, the generation of data dictionary format data according to an embodiment of the invention, including：
Step 202, entity object and attribute information in database are obtained.Wherein, entity object includes physical table, regards
Figure, function, storing process etc.；The different attribute information of entity object can be obtained from the system table in database, such as：Physics
The attribute information of table includes table name, sets of fields, major key, external key etc.；The attribute information of view includes view name, sets of fields etc.；Letter
Several attribute informations includes function name, parameter set, return value etc.；The attribute information of storing process includes storing process name, parameter
Collection etc..The attribute information of sets of fields and parameter set include title, data type, data length, default value, whether allow for
Empty, field annotation etc..
Step 204, the entity relationship between multiple entity objects is obtained.Relationship between entity object can be divided into physical table with
Relationship between relationship, view between physical table and the relationship between physical table, view and view.Wherein, physical table and object
The relationship managed between table is embodied with foreign key constraint relationship in the database；Relationship between view and physical table and view and view is in number
It is embodied with connection relation in view query source according in library.
Step 206, the data dictionary format rule of each entity object is defined, data dictionary format rule is (for example, data
Dictionary format rule is XML data dictionary format rule, and XML indicates Extensible Markup Language, expansible mark
Note language) for multiple entity objects of the databases such as physical table, view, function, storing process to be converted to data dictionary lattice
Formula data (for example, XML data dictionary format data).Data dictionary format rule includes multiple entity objects of database
The comments forms data of attribute information and entity relationship and entity object.
For example, shown in XML data dictionary format rule is defined as follows：
<DataDictionary>
<DataObject ObjectName=' entity objects name ' ObjectType=' deposit by physical table/view/function/
Storage process '>
<Comments LocaleID=' zh-CN ' Comment=' Chinese annotations describe '/>
<The description of Comments LocaleID=' zh-TW ' Comment=' traditional fonts annotation '/>
<Comments LocaleID=' en-US ' Comment=' english notes describe '/>
<Fields FieldName=' fields/parameter name '>
<Attrs Name=' Property Names ' Value=' attribute value '/>
……
<Foreignkey DataObject=' associated entities ' Field=' associate field '/>
<Comments LocaleID=' zh-CN ' Comment=' Chinese annotations describe '/>
<The description of Comments LocaleID=' zh-TW ' Comment=' traditional fonts annotation '/>
<Comments LocaleID=' en-US ' Comment=' english notes describe '/>
</Fields>
</DataObject>
</DataDictionary>
1. the entity object in the database of acquisition is recorded in XML data dictionary format<DataObject>Metadata
In node.ObjectName records the title of entity object, the type of ObjectType mark-up entity objects.
2. in XML data dictionary format<Fields>The relevant field of entity object or parameter are recorded in metadata node
Information.The title of FieldName record fields or parameter.
3. in XML data dictionary format<Attrs>The relevant sets of fields of entity object or ginseng are recorded in metadata node
The various correlation attribute informations of manifold.The attribute of the Property Name of Name tag fields or parameter, Value record fields or parameter
Value.Whether field and parameter include attribute information has data type, data length, default value, allows for sky etc..
4. in XML data dictionary format<Foreignkey>Record field and other entity object words in metadata node
The relationship of the field of Duan Jizhong.DataObject marks associated entity object, Field to mark the word of associated entity object
Section.
5. in XML data dictionary format<Comments>In metadata node database of record entity object or field or
The annotation information of parameter.The corresponding language information of LocaleID marker annotations information, the corresponding languages of Comment records are retouched in detail
It states.
Step 208, corresponding XML data dictionary format number is generated according to the data dictionary format rule of each entity object
According to.
Fig. 3 shows the flow diagram of the generation of data dictionary specification according to an embodiment of the invention.
As shown in figure 3, the generation of data dictionary specification according to an embodiment of the invention, including：
Step 302, there are other relationships in addition to entity relationship between entity object in practical applications, pass through in this way
Self-defined relationship between multiple entity objects is set to reduce the annotation information of redundancy.Wherein it is possible to by the way that XML data is arranged
Foreignkey attributes realize the setting of self-defined relationship in dictionary format data.
Step 304, according between the principle of consent of the same name and multiple entity objects entity relationship and self-defined relationship compress
Data dictionary format data.For example, to data dictionary format data compress as shown in table 1：
Table 1
Step 306, annotation information is added to the entity object in compressed data dictionary format data, to generate data
Dictionary specification.For example, the annotation information of addition entity object is as shown in table 2,
Table 2
Fig. 4 shows the flow diagram of data dictionary generation method according to another embodiment of the invention.
As shown in figure 4, data dictionary generation method according to another embodiment of the invention, including：
Step 402, XML data dictionary format data are obtained.
Step 404, data dictionary specification is obtained.
Step 406, data dictionary is generated according to XML data dictionary format data and data dictionary specification, specifically,
According to entity relationship and the self-defined relationship between multiple entity objects, the annotation information in data dictionary specification is written
Into the comments forms data in multiple data dictionary format data, according to the multiple data dictionary formats for including annotation information
Data generate data dictionary.
Fig. 5 shows the structural schematic diagram of data dictionary generating means according to an embodiment of the invention.
As shown in figure 5, data dictionary generating means 500 according to an embodiment of the invention, including：First generates list
Member 502, for according to the attribute information of each entity object in multiple entity objects, the multiple entity object and described more
Entity relationship between a entity object generates multiple data dictionary format data of corresponding the multiple entity object；Processing
Unit 504, the annotation information for adding multiple entity objects described in the multiple data dictionary format data, to form packet
Include the data dictionary specification of the annotation information；Second generation unit 506, for according to the multiple data dictionary lattice
Formula data and the data dictionary specification generate data dictionary.
In the technical scheme, due to the participant of the research and development and the later maintenance that participate in product in the life cycle of product
Member updates and replaces often, therefore, by multiple data dictionary format data of multiple entity objects in the database of product and
Data dictionary specification generate data dictionary, not only allow participant according to data dictionary more fast with easily
Solve the database structure of product, the characteristics of also making full use of the data structure of data base normalization (multiple entities i.e. in database
Entity relationship in object, multiple entity objects between the attribute information and multiple entity objects of each entity object) next life
At data dictionary, the annotation information generation data dictionary for being completely dependent on entity object is avoided.
In the above-mentioned technical solutions, it is preferable that first generation unit 502 includes：Acquiring unit 5022, in number
According to obtaining the multiple entity object, the attribute information of each entity object and the multiple entity object in library
Between the entity relationship；Definition unit 5024, for the institute according to each entity object, each entity object
The entity relationship between attribute information and the multiple entity object is stated, the data word of each entity object is defined
Allusion quotation format convention；First generation unit 502 is specifically used for, according to each entity object described in the multiple entity object
The data dictionary format rule generate the multiple data dictionary format data.
In the technical scheme, according to multiple entity objects in database, the attribute information of each entity object and more
Entity relationship between a entity object defines the data dictionary format rule of each entity object, so as to according to data word
Allusion quotation format convention generates the data dictionary format data of each entity object, to make full use of the data knot of data base normalization
The characteristics of structure, avoids the annotation information generation data dictionary for being completely dependent on entity object.
In the above-mentioned technical solutions, it is preferable that the processing unit 504 includes：Setting unit 5042, for user to be arranged
Self-defined relationship between customized the multiple entity object；Compression unit 5044, for according to the principle of consent of the same name with
And the entity relationship between the multiple entity object and the self-defined relationship are to the multiple data dictionary format number
According to being compressed；The processing unit 504 is specifically used for, and adds described in compressed the multiple data dictionary format data
The annotation information of multiple entity objects.
In the technical scheme, since there is also in addition to entity relationship between multiple entity objects in practical applications
Other relationships can efficiently reduce data dictionary specification by the self-defined relationship being arranged between multiple entity objects
Range, so as to more accurately and efficiently generate data dictionary.In addition, due to entity object annotation information there may be
It repeats, therefore, according to the entity relationship between the principle of consent of the same name and multiple entity objects with self-defined relationship to multiple data
Dictionary format data are compressed, to reduce the superfluous of annotation information while ensureing the data dictionary accuracy of production
It is remaining.
In the above-mentioned technical solutions, it is preferable that second generation unit 506 is specifically used for：According to the multiple entity
The entity relationship between object and the self-defined relationship, by the annotation information in the data dictionary specification
It is written in the comments forms data in the multiple data dictionary format data, according to including described in the annotation information
Multiple data dictionary format data generate the data dictionary.
In the technical scheme, by the way that the annotation information in data dictionary specification is written to multiple data dictionary lattice
In comments forms data in formula data, and data dictionary is generated according to multiple data dictionaries with annotation information, makes participation
Personnel can according to data dictionary more fast with easily understand product database structure.
In the above-mentioned technical solutions, it is preferable that the multiple entity object includes：Physical table, view and function；And institute
Stating entity relationship includes：Relationship, the physical table between the physical table and the physical table and the pass between the view
System and the relationship between the view and the view.
In the technical scheme, multiple entity objects include but not limited to：Physical table, view and function, for example, entity pair
As can also be storing process, wherein the attribute information of physical table includes table name, sets of fields, major key, external key etc., the category of view
Property information includes view name, sets of fields etc., and the attribute information of function includes function name, parameter set, return value etc., storing process
Attribute information includes storing process name, parameter set etc..In addition, entity relationship includes but not limited to：Between physical table and physical table
Relationship, the relationship between physical table and view and the relationship between view and view, wherein between physical table and physical table
Relationship is embodied with foreign key constraint relationship in the database, the relationship between relationship and view and view between view and physical table
It is embodied in the database with connection relation in view query source.
Fig. 6 shows the structural schematic diagram of data dictionary generating means according to another embodiment of the invention.
As shown in fig. 6, data dictionary generating means 600 according to another embodiment of the invention, including data dictionary
Formatted data module 602, data dictionary specification module 604 and data dictionary generation module 606, be described in detail below this three
A module：
Data dictionary format data module 602, for realizing multiple entity objects, the multiple reality is obtained from database
Entity relationship in body object between the attribute information and the multiple entity object of each entity object, according to each entity
The data dictionary format rule of object generates XML data dictionary format data.
Data dictionary specification module 604 carries out redundancy for realizing to the information in XML data dictionary format data
Processing, to form data dictionary specification.
Data dictionary generation module 606, for being generated according to XML data dictionary format data and data dictionary specification
Data dictionary.
Technical scheme of the present invention is described in detail above in association with attached drawing, by using the data structure of data base normalization
The characteristics of to generate data dictionary, avoid be completely dependent on entity object annotation information generate data dictionary, and reduce
The difficulty for generating data dictionary, to make the generation of data dictionary that there is operability.
The foregoing is only a preferred embodiment of the present invention, is not intended to restrict the invention, for the skill of this field
For art personnel, the invention may be variously modified and varied.All within the spirits and principles of the present invention, any made by repair
Change, equivalent replacement, improvement etc., should all be included in the protection scope of the present invention.
Claims (8)
1. a kind of data dictionary generation method, which is characterized in that including：
Between the attribute information and the multiple entity object that obtain multiple entity objects, each entity object in the database
Entity relationship；
According to each entity object, the attribute information of each entity object and the multiple entity object it
Between the entity relationship, define the data dictionary format rule of each entity object；
Multiple data are generated according to the data dictionary format rule of each entity object described in the multiple entity object
Dictionary format data；
The annotation information for adding multiple entity objects described in the multiple data dictionary format data includes described to be formed
The data dictionary specification of annotation information；
Data dictionary is generated according to the multiple data dictionary format data and the data dictionary specification.
2. data dictionary generation method according to claim 1, which is characterized in that the multiple data dictionary of addition
Described in formatted data the step of the annotation information of multiple entity objects, specifically include：
Self-defined relationship between user-defined the multiple entity object is set；
According to the entity relationship and the self-defined relationship pair between the principle of consent of the same name and the multiple entity object
The multiple data dictionary format data are compressed；
Add the annotation information of multiple entity objects described in compressed the multiple data dictionary format data.
3. data dictionary generation method according to claim 2, which is characterized in that described according to the multiple data dictionary
The step of formatted data and the data dictionary specification generate data dictionary, specifically includes：
According to the entity relationship and the self-defined relationship between the multiple entity object, by the data dictionary specification
The annotation information in definition is written in the comments forms data in the multiple data dictionary format data；
According to the multiple data dictionary format data generation data dictionary for including the annotation information.
4. data dictionary generation method according to any one of claim 1 to 3, which is characterized in that
The multiple entity object includes：Physical table, view and function；And
The entity relationship includes：Relationship, the physical table between the physical table and the physical table and the view it
Between relationship and the view and the view between relationship.
5. a kind of data dictionary generating means, which is characterized in that including：
Acquiring unit, attribute information for obtaining multiple entity objects, each entity object in the database and described more
Entity relationship between a entity object；
Definition unit, for according to each entity object, the attribute information of each entity object and described
The entity relationship between multiple entity objects defines the data dictionary format rule of each entity object；
First generation unit, for the data dictionary format according to each entity object described in the multiple entity object
Rule generates multiple data dictionary format data；
Processing unit, the annotation information for adding multiple entity objects described in the multiple data dictionary format data, with
Formation includes the data dictionary specification of the annotation information；
Second generation unit, for generating number according to the multiple data dictionary format data and the data dictionary specification
According to dictionary.
6. data dictionary generating means according to claim 5, which is characterized in that the processing unit includes：
Setting unit, for the self-defined relationship between user-defined the multiple entity object to be arranged；
Compression unit, for according between the principle of consent of the same name and the multiple entity object the entity relationship with it is described
Self-defined relationship compresses the multiple data dictionary format data；
The processing unit is specifically used for, and adds multiple entities pair described in compressed the multiple data dictionary format data
The annotation information of elephant.
7. data dictionary generating means according to claim 6, which is characterized in that second generation unit is specifically used
In：
According to the entity relationship and the self-defined relationship between the multiple entity object, by the data dictionary specification
The annotation information in definition is written in the comments forms data in the multiple data dictionary format data,
According to the multiple data dictionary format data generation data dictionary for including the annotation information.
8. data dictionary generating means according to any one of claims 5 to 7, which is characterized in that
The multiple entity object includes：Physical table, view and function；And
The entity relationship includes：Relationship, the physical table between the physical table and the physical table and the view it
Between relationship and the view and the view between relationship.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510370318.3A CN105005592B (en) | 2015-06-29 | 2015-06-29 | Data dictionary generation method and data dictionary creation device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510370318.3A CN105005592B (en) | 2015-06-29 | 2015-06-29 | Data dictionary generation method and data dictionary creation device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105005592A CN105005592A (en) | 2015-10-28 |
| CN105005592B true CN105005592B (en) | 2018-10-16 |
Family
ID=54378268
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510370318.3A Active CN105005592B (en) | 2015-06-29 | 2015-06-29 | Data dictionary generation method and data dictionary creation device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105005592B (en) |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106933832A (en) * | 2015-12-30 | 2017-07-07 | 中国科学院沈阳自动化研究所 | A kind of construction method of the digital dictionary of oil reservoir |
| CN107203525B (en) * | 2016-03-16 | 2020-03-06 | 北大方正集团有限公司 | Database processing method and device |
| CN106202008B (en) * | 2016-06-28 | 2019-04-05 | 武汉斗鱼网络科技有限公司 | A kind of MySQL database structured document generation method and device |
| CN108038203B (en) * | 2017-12-13 | 2021-08-03 | 明算科技（北京）股份有限公司 | Storage device of data dictionary |
| CN110348004B (en) * | 2019-05-23 | 2022-05-06 | 平安科技（深圳）有限公司 | Method and device for generating data dictionary, electronic equipment and storage medium |
| CN110471995B (en) * | 2019-08-14 | 2022-04-15 | 中电科新型智慧城市研究院有限公司 | Cross-domain information sharing exchange data model modeling method |
| CN110502535B (en) * | 2019-08-28 | 2022-02-22 | 上海达梦数据库有限公司 | Data access method, device, equipment and storage medium |
| CN110825805B (en) * | 2019-11-12 | 2022-07-19 | 望海康信(北京)科技股份公司 | Data visualization method and device |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102096670A (en) * | 2009-12-14 | 2011-06-15 | 深圳速浪数字技术有限公司 | Data dictionary generation method and device |
| CN102541867A (en) * | 2010-12-15 | 2012-07-04 | 金蝶软件（中国）有限公司 | Data dictionary generating method and system |
| CN102999600A (en) * | 2012-11-20 | 2013-03-27 | 中兴通讯股份有限公司 | Method and system for automatically generating embedded database |
| CN103970855A (en) * | 2014-05-06 | 2014-08-06 | 车智互联（北京）科技有限公司 | Device and method for processing data |
| CN104462108A (en) * | 2013-09-17 | 2015-03-25 | 中兴通讯股份有限公司 | Database structure object processing method and device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR100701104B1 (en) * | 2004-12-22 | 2007-03-28 | 한국전자통신연구원 | Method of generating database schema to provide integrated view of dispersed information and integrating system of information |
-
2015
- 2015-06-29 CN CN201510370318.3A patent/CN105005592B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102096670A (en) * | 2009-12-14 | 2011-06-15 | 深圳速浪数字技术有限公司 | Data dictionary generation method and device |
| CN102541867A (en) * | 2010-12-15 | 2012-07-04 | 金蝶软件（中国）有限公司 | Data dictionary generating method and system |
| CN102999600A (en) * | 2012-11-20 | 2013-03-27 | 中兴通讯股份有限公司 | Method and system for automatically generating embedded database |
| CN104462108A (en) * | 2013-09-17 | 2015-03-25 | 中兴通讯股份有限公司 | Database structure object processing method and device |
| CN103970855A (en) * | 2014-05-06 | 2014-08-06 | 车智互联（北京）科技有限公司 | Device and method for processing data |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105005592A (en) | 2015-10-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105005592B (en) | Data dictionary generation method and data dictionary creation device | |
| US11620301B2 (en) | Extended computerized query language syntax for analyzing multiple tabular data arrangements in data-driven collaborative projects | |
| US20190050459A1 (en) | Localized link formation to perform implicitly federated queries using extended computerized query language syntax | |
| US8756495B2 (en) | Computer-implemented system and method for tagged and rectangular data processing | |
| US9058407B2 (en) | Persistent multimedia content versioning | |
| US9230040B2 (en) | Scalable, schemaless document query model | |
| US9607061B2 (en) | Using views of subsets of nodes of a schema to generate data transformation jobs to transform input files in first data formats to output files in second data formats | |
| US9785725B2 (en) | Method and system for visualizing relational data as RDF graphs with interactive response time | |
| US7720885B2 (en) | Generating a word-processing document from database content | |
| Comyn-Wattiau et al. | Model driven reverse engineering of NoSQL property graph databases: The case of Neo4j | |
| US9171051B2 (en) | Data definition language (DDL) expression annotation | |
| CN106649769B (en) | Semantic-based conversion method from XBRL data to OWL data | |
| US8612489B2 (en) | LossLess transformation of XBRL instance to XML data model instance | |
| CN106547918A (en) | A kind of integration method and system of statistical data | |
| Sengupta et al. | XER-extensible entity relationship modeling | |
| US20070299821A1 (en) | Report specification system and method | |
| CN105159904B (en) | A kind of method and system of digital resource associate management | |
| CN107491524B (en) | Method and device for calculating Chinese word relevance based on Wikipedia concept vector | |
| CN115080594A (en) | Method and system for carrying out multi-dimensional analysis on data and electronic equipment | |
| Dickson et al. | The semi-structured data model and implementation issues for semi-structured data | |
| Ren et al. | Rules and implementation for generating Ontology from relational database | |
| JP2003288332A (en) | Method and system for supporting structured document creation | |
| CN113205881B (en) | OpenEHR prototype and template automatic generation method based on thought guide graph | |
| CN117744615A (en) | Form data processing method and device, electronic equipment and readable storage medium | |
| CN118093632A (en) | Graph database query method and device based on large language model and graph structure |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |