CN109947741A - A kind of modeling and storage method of items property parameters - Google Patents
A kind of modeling and storage method of items property parameters Download PDFInfo
- Publication number
- CN109947741A CN109947741A CN201910104873.XA CN201910104873A CN109947741A CN 109947741 A CN109947741 A CN 109947741A CN 201910104873 A CN201910104873 A CN 201910104873A CN 109947741 A CN109947741 A CN 109947741A
- Authority
- CN
- China
- Prior art keywords
- class
- items
- types
- relationship
- variables
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Abstract
It is an object of the invention to disclose the modeling and storage method of a kind of items property parameters, data modeling is carried out using " name-reality separation ", it is able to achieve by the class of four cores and several non-core classes and all properties and relationship of all items is modeled, and storage of the realization to all edition datas and its satellite information, in relationship metadata modeling, it only needs to be defined from one end of relationship, items type without defining relationship both ends simultaneously, alleviate the workload of contextual definition, pass through the relationship metadata at specified both ends in relation value storage simultaneously, so that relation information is complete, and relationship lookup and statistics can be carried out from any end, realize distributed storage, conducive to implementation search mechanism, improve the reading performance of data and the maintainability of database, it is more to solve items type, items attribute is more, The versions of data not fixed sum data value satellite information data modeling and database design problem when storing simultaneously, achieves the object of the present invention.
Description
Technical field
The present invention relates to a kind of modeling of parameter and storage method, in particular to a kind of items attribute for software development
The modeling and storage method of parameter.
Background technique
It is usually right with conceptual model (usually E-R figure or class figure, the two form is different but expression is identical) when software development
Entity class, attribute and connection are modeled, and are then described to after the logical transition of " relationship " with physical model by E-R figure
The realization (i.e. the detailed description of tables of data) of conceptual model in the database.In general, one of conceptual model entity class,
A tables of data in corresponding physical model, wherein one of each field (or being column) correspondent entity class of tables of data belongs to
Property, and every example for recording a corresponding entity class.In addition, " many-to-many relationship " between entity class and entity class, passes through
Create tables of data individually to realize.
Above-mentioned this " entity class one opens tables of data (hereinafter referred to as entity table) " and " number is contacted between a kind of entity
According to table (hereinafter referred to as contacts list) " mode, although be widely applied, for the data management system of enterprise, exist with
Lower problem:
It is hundreds and thousands of if 1) entity class is very more, and all there may be connections between every two kinds of entities, then needing to create
The entity table of O (N) order of magnitude and the contacts list of O (N × N) order of magnitude are built, and with the developing of business event or enterprise's number
According to the intensification of combing, connection may be continuously increased or modify between above-mentioned entity class and entity, to cause the dynamic of database
Table is built, very big challenge is all brought to database maintenance and software development.
2) if the attribute (or being member variable) of entity class has up to a hundred, and the example number of the entity class is very
Few, then the corresponding entity table of the entity class occurs as soon as the situation of " the few column of row are more ", this aspect makes database build the work of table
Measure heavy (to describe a fields up to a hundred), be on the other hand unable to give full play out database data " increasing is looked into change and be deleted " (create,
Retrieve, update, delete, CRUD) in terms of advantage.
3) attribute value of the example stored in above-mentioned entity table can only be a data, in other words the number of a version
According to, and the data of all versions cannot be stored.If software systems will store the number that some entity attribute is formed in different phase
According to value, then multiple tables of data (i.e. a stage one opens table) are established, however due to " stage " or " version " of each attribute
Number be indefinite and differ, therefore the storage problem of indefinite edition data can not be solved.
4) in above-mentioned entity table, the attribute value of the only items of storage.A but software systems, in addition to store
Except attribute value, to store other information relevant to the value toward contact, as data entry time, versions of data, typing stream
Journey information, data source, security classification of data etc..Although these information can also be deposited by design contacts list or log
Storage, but if if these information itself are also critically important, then the database designed in this way, " E-R " can very
It is complicated.
In conclusion in the data management system of undertaking of construction, if entity class is very more, each entity attributes
It is also very more with relationship, it to store the data value of indefinite version and to store " the ins and outs " of each data value simultaneously,
In this case, traditional data modeling and storage mode just seem " unable to do what one wishes ".
It is accordingly required in particular to a kind of modeling and storage method of items property parameters, to solve above-mentioned existing ask
Topic.
Summary of the invention
The purpose of the present invention is to provide the modelings and storage method of a kind of items property parameters, not for the prior art
Foot solves more entity class, each entity attributes and relationship is more, versions of data fixed sum data value satellite information while not deposited
The case where storage, rationally, simple and efficiently the attribute and relationship of entity items are modeled and stored.
Technical problem solved by the invention can be realized using following technical scheme:
A kind of modeling and storage method of items property parameters, which is characterized in that it includes the following steps:
S1, it establishes including items class types Class, items class Item, unit class Unit and including enumerating class Enume
Class；Wherein, items class types Class carries out unified Modeling to all items type, items class Item to all items into
The unified modeling of row, unit class Unit carry out unified Modeling to all units, enumerate class Enume and carry out to all enumerated values
Unified Modeling；
S2, attribute-name class ParamName is established, unified Modeling is carried out to all entity attributes metadata；
S3, attribute value class ParamValue is established, unified Modeling is carried out to all entity attributes value related datas；
S4, opening relationships name class RelatName, from the visual angle of relationship one end items between first number of relationship all entities
According to carrying out unified modeling；
S5, opening relationships value class RelatValue, from the visual angle of relationship both ends items between the pass of relationship all entities
Set occurrence carries out unified modeling；
After S6, conceptual model are all established, conceptual model can be converted to the physical model of database structure, wherein generally
Read the tables of data that class in model is converted into database；Reference connection between class, the primary key-foreign key being converted between tables of data
Relationship.
In one embodiment of the invention, attribute-name class ParamName include at least member variable id, class,
Name, code, unit, dataType, enume and fields；Wherein, id is the identification code of the attribute metadata, types of variables
It is long or UUID；Class is the entity class of the attribute metadata institute subordinate, and types of variables is the items class established in step S1
Type class Class；Name is the title of the attribute, and types of variables is String；Code is the coding of the attribute, and types of variables is
String；DataType is the data type of the attribute, and types of variables is int or String；Unit is the unit of the attribute, is become
Amount type is the unit class Unit that S1 is established；Enume is the enumerated value of the attribute, and types of variables is enumerating of establishing in step S1
Class Enume；Fields is the column information of array type attribute, and types of variables is List<ParamName>.
Further, user can increase and decrease required member variable, to describe the metadata information of an attribute, but not include
The relevant member variable of the attribute value of the attribute.
In one embodiment of the invention, attribute value class ParamValue include at least member variable id, item,
ParamName, value, values, date, version, desFlow and QAFlow；Wherein, id is the mark of the attribute value
Code, types of variables is long or UUID；Item is the example items of the attribute value institute subordinate, and types of variables is built in step S1
Vertical items class Item；ParamName is attribute-name metadata corresponding to the attribute value, and types of variables is established in step S2
Attribute-name class ParamName；Value is the specific value (corresponding one-parameter) of the attribute value, and types of variables is String；
Values is also the specific value (parameter of corresponding array type) of the attribute value, and types of variables is JSONArray or String
[][]；Date is the issuing time of the attribute value, and types of variables is Date；Version is the version number of the attribute value, variable
Type is Char；DesFlow is the generation process of the attribute value, and QAFlow is the quality guarantee process of the attribute value.
In one embodiment of the invention, relationship name class RelatName include at least member variable id, leftClass,
Name, code, oneToMany and rightCategory；Wherein, id is the identifier of the relationship name metadata, and types of variables is
Long or UUID；LeftClass is the items class types of the visual angle end items institute subordinate of the relationship, and types of variables is step S1
The items class types Class of middle foundation；Name is the title of the relationship, and types of variables is String；Code is relationship coding,
Types of variables is String；OneToMany is the permitted most items example numbers of the other end of the relationship, and types of variables is
int；RightCategory is the scope of the items type of the other end items of the relationship, and types of variables is int or String.
In one embodiment of the invention, relation value class RelatValue include at least member variable leftItem,
LeftRelat, leftOrder, rightItem, rightRelat and rightOrder；Wherein, leftItem is the one of relationship
The items at end, types of variables are the items class Item established in step S1；LeftRelat is the relationship name member number of one end of relationship
According to types of variables is the relationship name class RelatName established in step S4；LeftOrderr is the items time of one end of relationship
Sequence, types of variables are int；RightItem is the items of the other end of relationship, and types of variables is the items class established in step S1
Item；RightRelat is the relationship name metadata of the other end of relationship, and types of variables is the relationship name class established in step S4
RelatName；RightOrder is the items order of the other end of relationship, and types of variables is int.
The modeling and storage method of items property parameters of the invention, compared with prior art, using " name-reality separate " into
Row data modeling is all properties and relationship being able to achieve to all items by the class of four cores and several non-core classes
It is modeled, and realizes the storage to all edition datas and its satellite information, in relationship metadata modeling, it is only necessary to from pass
One end of system, which is set out, to be defined, and the items type without defining relationship both ends simultaneously, model is simple, dramatically reduces
The workload of contextual definition, while in relation value storage by specifying the relationship metadata at both ends, so that relation information is complete,
And relationship lookup and statistics can be carried out from any end, it can be realized distributed storage, while being conducive to implement search mechanism, improve
The reading performance of data and the maintainability of database, solve that items type is more, items attribute is more, the indefinite sum number of versions of data
Data modeling and database design problem when storing simultaneously according to value satellite information, achieve the object of the present invention.
The features of the present invention sees the detailed description of the drawings of the present case and following preferable embodiment and obtains clearly
Solution.
Detailed description of the invention
Fig. 1 is the schematic diagram of the relevant conceptual model of items attribute of the invention；
Fig. 2 is the schematic diagram of the relevant conceptual model of object inter-item relationship of the invention；
Fig. 3 is the schematic diagram of the relevant physical model of items attribute of the invention；
Fig. 4 is the schematic diagram of the relevant physical model of object inter-item relationship of the invention.
Specific embodiment
In order to be easy to understand the technical means, the creative features, the aims and the efficiencies achieved by the present invention, tie below
Conjunction is specifically illustrating, and the present invention is further explained.
Embodiment
As shown in Figures 1 to 4, the modeling and storage method of items property parameters of the invention, it is comprised the following steps that
S1, establish including items class types Class, items class Item, unit class Unit, enumerate class Enume etc. including
Class, wherein items class types Class carries out unified Modeling to all items types.Items class Item carries out all items
Unified modeling.Unit class Unit carries out unified Modeling to all units.Class Enume is enumerated to unite to all enumerated values
One modeling.
S2, attribute-name class (ParamName) is established, such carries out unified Modeling to all entity attributes metadata,
As shown in Figure 1.Such includes at least member variable id, class, name, code, unit, dataType, enume, fields
Deng.Wherein id is the identification code of the attribute metadata, and types of variables is long or UUID；Class be the attribute metadata institute from
The entity class of category, types of variables are the items class types Class that S1 is established；Name is the title of the attribute, and types of variables is
String；Code is the coding of the attribute, and types of variables is String；DataType is the data type of the attribute, variable class
Type is int or String；Unit is the unit of the attribute, and types of variables is the unit class Unit that S1 is established；Enume is the attribute
Enumerated value, types of variables be S1 establish enumerate class Enume；Fields is the column information of array type attribute, types of variables
Can be List<ParamName>.User can increase and decrease required member variable, to describe the metadata information of an attribute, but
It does not include the relevant member variable of attribute value of the attribute.
S3, attribute value class (ParamValue) is established, such carries out unification to all entity attributes value related datas
Modeling, as shown in Figure 1.Such include at least member variable id, item, paramName, value, values, date,
Version, desFlow, QAFlow etc..Wherein id is the identification code of the attribute value, and types of variables is long or UUID；item
It is the example items of the attribute value institute subordinate, types of variables is the items class Item that S1 is established；ParamName is the attribute value institute
Corresponding " attribute-name " metadata, types of variables are the attribute-name class ParamName that S2 is established；Value is the tool of the attribute value
Body numerical value (corresponding one-parameter), types of variables is String；Values is also specific value (the corresponding array type of the attribute value
Parameter), types of variables is JSONArray or String [] []；Date is the issuing time of the attribute value, and types of variables is
Date；Version is the version number of the attribute value, and types of variables is Char；DesFlow is the generation process of the attribute value,
QAFlow is the quality guarantee process of the attribute value.
S4, opening relationships name class (RelatName), such be from the visual angle of relationship one end (rather than both ends) items, it is right
The metadata of relationship carries out unified modeling between all entities, as shown in Figure 2.Such include at least member variable id,
LeftClass, name, code, oneToMany, rightCategory etc..Wherein id is the identifier of the relationship name metadata,
Types of variables is long or UUID；LeftClass is the items class types of the visual angle end items institute subordinate of the relationship, variable class
Type is the items class types Class that S1 is established；Name is the title of the relationship, and types of variables is String；Code is the relationship
Coding, types of variables is String；OneToMany is the permitted most items example numbers of the other end of the relationship, variable
Type is int；RightCategory is the scope of the items type of the other end items of the relationship, types of variables be int or
String。
S5, opening relationships value class (RelatValue), such is from the visual angle of relationship both ends items, between all entities
The relation value of relationship carries out unified modeling, as shown in Figure 2.Such include at least member variable leftItem, leftRelat,
LeftOrder, rightItem, rightRelat, rightOrder etc..Wherein leftItem is the items of one end of relationship, is become
Amount type is the items class Item that S1 is established；LeftRelat is the relationship name metadata of one end of relationship, and types of variables is that S4 is built
Vertical relationship name class RelatName；LeftOrderr is the items order of one end of relationship, and types of variables is int；
RightItem is the items of the other end of relationship, and types of variables is the items class Item that S1 is established；RightRelat is relationship
The relationship name metadata of the other end, types of variables are the relationship name class RelatName that S4 is established；RightOrder is the another of relationship
The items order of one end, types of variables are int.
After conceptual model is all established, conceptual model can be converted to the physical model of database structure.Wherein concept
Class is converted into the tables of data in database in model；Reference connection between class, the primary key-foreign key being converted between tables of data close
System.As shown in Figure 3 and Figure 4.
S6, in software development, class and data structure of the invention can be directlyed adopt, as to items attribute and relationship into
The foundation of row modeling and storage.Certainly, appropriate adjustment is carried out according to actual software development language and database product.
Items type is more, items attribute is more, items relationship is more when from the aforegoing it can be seen that this method is suitable for data modeling,
The case where versions of data is indefinite and needs storing data procedure information simultaneously.Above situation not only can solve using this method
Data modeling and storage problem, return database maintenance, information retrieval etc. and provide convenience.
The above shows and describes the basic principles and main features of the present invention and the advantages of the present invention.The technology of the industry
Personnel are it should be appreciated that the present invention is not limited to the above embodiments, and the above embodiments and description only describe this
The principle of invention, without departing from the spirit and scope of the present invention, various changes and improvements may be made to the invention, these changes
Change and improvement all fall within the protetion scope of the claimed invention, the claimed scope of the invention by appended claims and its
Equivalent thereof.
Claims (6)
1. a kind of modeling and storage method of items property parameters, which is characterized in that it includes the following steps:
S1, it establishes including items class types Class, items class Item, unit class Unit and the class including enumerating class Enume；Its
In, items class types Class carries out unified Modeling to all items types, and items class Item carries out unification to all items
Modeling, unit class Unit carries out unified Modeling to all unit, enumerates class Enume and uniformly built to all enumerated values
Mould；
S2, attribute-name class ParamName is established, unified Modeling is carried out to all entity attributes metadata；
S3, attribute value class ParamValue is established, unified Modeling is carried out to all entity attributes value related datas；
S4, opening relationships name class RelatName, from the visual angle of relationship one end items between the metadata of relationship all entities into
The unified modeling of row；
S5, opening relationships value class RelatValue, from the visual angle of relationship both ends items between the relation value of relationship all entities
Carry out unified modeling；
After S6, conceptual model are all established, conceptual model can be converted to the physical model of database structure, wherein concept mould
Class is converted into the tables of data in database in type；Reference connection between class, the primary key-foreign key being converted between tables of data close
System.
2. the modeling and storage method of items property parameters as described in claim 1, which is characterized in that attribute-name class
ParamName includes at least member variable id, class, name, code, unit, dataType, enume and fields；Wherein,
Id is the identification code of the attribute metadata, and types of variables is long or UUID；Class is the entity of the attribute metadata institute subordinate
Class, types of variables are the items class types Class established in step S1；Name is the title of the attribute, and types of variables is
String；Code is the coding of the attribute, and types of variables is String；DataType is the data type of the attribute, variable class
Type is int or String；Unit is the unit of the attribute, and types of variables is the unit class Unit that S1 is established；Enume is the attribute
Enumerated value, types of variables be established in step S1 enumerate class Enume；Fields is the column information of array type attribute, is become
Amount type is List<ParamName>.
3. the modeling and storage method of items property parameters as claimed in claim 2, which is characterized in that user can increase and decrease institute
The member variable needed to describe the metadata information of an attribute, but does not include the relevant member variable of attribute value of the attribute.
4. the modeling and storage method of items property parameters as described in claim 1, which is characterized in that attribute value class
ParamValue includes at least member variable id, item, paramName, value, values, date, version, desFlow
And QAFlow；Wherein, id is the identification code of the attribute value, and types of variables is long or UUID；Item be the attribute value institute from
The example items of category, types of variables are the items class Item established in step S1；ParamName is category corresponding to the attribute value
Property name metadata, types of variables is the attribute-name class ParamName established in step S2；Value is the specific number of the attribute value
Value (corresponding one-parameter), types of variables is String；Values is also the specific value (ginseng of corresponding array type of the attribute value
Number), types of variables is JSONArray or String [] []；Date is the issuing time of the attribute value, and types of variables is Date；
Version is the version number of the attribute value, and types of variables is Char；DesFlow is the generation process of the attribute value, and QAFlow is
The quality guarantee process of the attribute value.
5. the modeling and storage method of items property parameters as described in claim 1, which is characterized in that relationship name class
RelatName includes at least member variable id, leftClass, name, code, oneToMany and rightCategory；Its
In, id is the identifier of the relationship name metadata, and types of variables is long or UUID；LeftClass is the visual angle of the relationship
The items class types of items institute subordinate are held, types of variables is the items class types Class established in step S1；Name is the relationship
Title, types of variables is String；Code is relationship coding, and types of variables is String；OneToMany is the relationship
The permitted most items example numbers of the other end, types of variables is int；RightCategory is the other end object of the relationship
The scope of the items type of item, types of variables is int or String.
6. the modeling and storage method of items property parameters as described in claim 1, which is characterized in that relation value class
RelatValue include at least member variable leftItem, leftRelat, leftOrder, rightItem, rightRelat and
rightOrder；Wherein, leftItem is the items of one end of relationship, and types of variables is the items class established in step S1
Item；LeftRelat is the relationship name metadata of one end of relationship, and types of variables is the relationship name class established in step S4
RelatName；LeftOrderr is the items order of one end of relationship, and types of variables is int；RightItem is the another of relationship
The items of one end, types of variables are the items class Item established in step S1；RightRelat is the relationship of the other end of relationship
Name metadata, types of variables is the relationship name class RelatName established in step S4；RightOrder is the other end of relationship
Items order, types of variables are int.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910104873.XA CN109947741B (en) | 2019-02-01 | 2019-02-01 | Method for modeling and storing attribute parameters of items |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910104873.XA CN109947741B (en) | 2019-02-01 | 2019-02-01 | Method for modeling and storing attribute parameters of items |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109947741A true CN109947741A (en) | 2019-06-28 |
| CN109947741B CN109947741B (en) | 2022-12-02 |
Family
ID=67007962
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910104873.XA Active CN109947741B (en) | 2019-02-01 | 2019-02-01 | Method for modeling and storing attribute parameters of items |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109947741B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110711389A (en) * | 2019-09-29 | 2020-01-21 | 上海莉莉丝科技股份有限公司 | Data processing method, device, equipment and computer readable medium |
| CN111198870A (en) * | 2019-12-23 | 2020-05-26 | 浙江中控技术股份有限公司 | Modeling method and system of process equipment |
| CN112416949A (en) * | 2020-12-15 | 2021-02-26 | 上海核工程研究设计院有限公司 | Structure data packaging method based on digital delivery |
| CN113721897A (en) * | 2021-08-03 | 2021-11-30 | 中国航空工业集团公司沈阳飞机设计研究所 | Modeling method based on OPM |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH07129445A (en) * | 1993-10-29 | 1995-05-19 | Hitachi Ltd | Method for generating logical configuration of data base file |
| CN103186628A (en) * | 2011-12-31 | 2013-07-03 | 上海可鲁系统软件有限公司 | Method for mapping between common information model and relational database |
| CN105630500A (en) * | 2015-12-25 | 2016-06-01 | 江苏东大金智信息系统有限公司 | CIM object model for data processing and programming frame thereof |
| CN108710660A (en) * | 2018-05-11 | 2018-10-26 | 上海核工程研究设计院有限公司 | A kind of items property parameters modeling of database and storage method |
-
2019
- 2019-02-01 CN CN201910104873.XA patent/CN109947741B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH07129445A (en) * | 1993-10-29 | 1995-05-19 | Hitachi Ltd | Method for generating logical configuration of data base file |
| CN103186628A (en) * | 2011-12-31 | 2013-07-03 | 上海可鲁系统软件有限公司 | Method for mapping between common information model and relational database |
| CN105630500A (en) * | 2015-12-25 | 2016-06-01 | 江苏东大金智信息系统有限公司 | CIM object model for data processing and programming frame thereof |
| CN108710660A (en) * | 2018-05-11 | 2018-10-26 | 上海核工程研究设计院有限公司 | A kind of items property parameters modeling of database and storage method |
Non-Patent Citations (3)
| Title |
|---|
| PIERRE DE VETTOR等: "Models and Adaptive Architecture for Smart Data Management", 《 2015 IEEE 24TH INTERNATIONAL CONFERENCE ON ENABLING TECHNOLOGIES: INFRASTRUCTURE FOR COLLABORATIVE ENTERPRISES》 * |
| 申屠军等: "核电数字化设计体系的组成和数据管理", 《仪器仪表用户》 * |
| 邓婧等: ""数字城市"土地利用空间数据库建库方法研究", 《中国山区土地资源开发利用与人地协调发展研究》 * |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110711389A (en) * | 2019-09-29 | 2020-01-21 | 上海莉莉丝科技股份有限公司 | Data processing method, device, equipment and computer readable medium |
| CN110711389B (en) * | 2019-09-29 | 2023-03-07 | 上海莉莉丝科技股份有限公司 | Data processing method, device, equipment and computer readable medium |
| CN111198870A (en) * | 2019-12-23 | 2020-05-26 | 浙江中控技术股份有限公司 | Modeling method and system of process equipment |
| CN111198870B (en) * | 2019-12-23 | 2024-04-02 | 浙江中控技术股份有限公司 | Modeling method and system for process equipment |
| CN112416949A (en) * | 2020-12-15 | 2021-02-26 | 上海核工程研究设计院有限公司 | Structure data packaging method based on digital delivery |
| CN113721897A (en) * | 2021-08-03 | 2021-11-30 | 中国航空工业集团公司沈阳飞机设计研究所 | Modeling method based on OPM |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109947741B (en) | 2022-12-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6970882B2 (en) | Unified relational database model for data mining selected model scoring results, model training results where selection is based on metadata included in mining model control table | |
| US6662188B1 (en) | Metadata model | |
| CN109947741A (en) | A kind of modeling and storage method of items property parameters | |
| US6636845B2 (en) | Generating one or more XML documents from a single SQL query | |
| CN101727478B (en) | Method and system for dynamically building and populating data marts with data stored in repositories | |
| CA2318299C (en) | Metadata exchange | |
| AU764720B2 (en) | Method and system for fast memory-resident processing of transaction data | |
| US20030105745A1 (en) | Text-file based relational database | |
| CN110134671B (en) | Traceability application-oriented block chain database data management system and method | |
| US8010905B2 (en) | Open model ingestion for master data management | |
| US20110231359A1 (en) | Synchronization of relational databases with olap cubes | |
| JPH1115867A (en) | Design information management system, design information access device and program storing medium | |
| US6470343B1 (en) | Method, computer program product, system, and data structure for database data model extension | |
| KR20060045622A (en) | Extraction, transformation and loading designer module of a computerized financial system | |
| CN112199433A (en) | Data management system for city-level data middling station | |
| CN102893281A (en) | Information retrieval device, information retrieval method, computer program, and data structure | |
| US6823334B2 (en) | Metadata system for managing data mining environments | |
| US8200668B2 (en) | Scalar representation for a logical group of columns in relational databases | |
| Do et al. | On metadata interoperability in data warehouses | |
| CN112699100A (en) | Management and analysis system based on metadata | |
| Staudt et al. | The role of metadata for data warehousing | |
| EP2343658A1 (en) | Federation as a process | |
| Paim et al. | Enhancing Data Warehouse Design with the NFR Framework. | |
| Taktak et al. | Toward propagating the evolution of data warehouse on data marts | |
| Auth et al. | A software architecture for XML-based metadata interchange in data warehouse systems |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP01 | Change in the name or title of a patent holder |
Address after: No. 29 Hong Cao Road, Xuhui District, Shanghai Patentee after: Shanghai Nuclear Engineering Research and Design Institute Co.,Ltd. Address before: No. 29 Hong Cao Road, Xuhui District, Shanghai Patentee before: SHANGHAI NUCLEAR ENGINEERING RESEARCH & DESIGN INSTITUTE Co.,Ltd. |
|
| CP01 | Change in the name or title of a patent holder |