WO2007137468A1 - Procédé et système de création automatique de modèle relationnel - Google Patents

Procédé et système de création automatique de modèle relationnel Download PDF

Info

Publication number
WO2007137468A1
WO2007137468A1 PCT/CN2007/000218 CN2007000218W WO2007137468A1 WO 2007137468 A1 WO2007137468 A1 WO 2007137468A1 CN 2007000218 W CN2007000218 W CN 2007000218W WO 2007137468 A1 WO2007137468 A1 WO 2007137468A1
Authority
WO
WIPO (PCT)
Prior art keywords
class
primary key
object model
mapping
association
Prior art date
Application number
PCT/CN2007/000218
Other languages
English (en)
Chinese (zh)
Inventor
Qingguang Meng
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2007137468A1 publication Critical patent/WO2007137468A1/fr

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/289—Object oriented databases
    • 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

Definitions

  • the present invention relates to the field of database technology, and more particularly to a system and method for automatically establishing a relationship model. 'Invention background
  • J2EE JAVA2 Enterprise Edition
  • the presentation layer is used to provide the interface to the end user, and the business logic layer is used.
  • the data source layer is used to process connections with relational databases, message systems, and complete transaction management functions.
  • the data source layer is a very important level. In practical applications, most of the application scenarios of data sources are relational databases.
  • the relational database can be accessed directly through JAVA database connection technology (JDBC), which is also the data access method adopted by most applications, but using JDBC to access the database in the application will lead to business processing logic.
  • JDBC JAVA database connection technology
  • Object/relational mapping technology is a good alternative. Object/relational mapping technology can be used to shield the background database system differences through the object-oriented (00) model, and the system data model is easy to understand. It helps to improve the efficiency of programming, and also improves the readability and maintainability of the code.
  • the first category is an object model-based modeling scheme.
  • the object model-based modeling scheme is completely centered on the object model, and is mainly a graphical modeling tool represented by the Unified Modeling Language (UML).
  • UML Unified Modeling Language
  • this type of solution does not reduce the application scenario of the data access layer. It is more complicated to use; and this kind of scheme does not provide mapping tool from object model to relational model.
  • the maintenance of relational model needs to be realized by another tool with low integration; and the scheme has no integration for object/relational mapping technology, manual The integration is a lot of work.
  • the second category is a modeling model based on a relational model.
  • the solution based on the relational model is completely centered on the relational model, and is mainly a graphical modeling tool represented by the entity relationship (ER) diagram.
  • ER entity relationship
  • Such a scheme does not provide a mapping tool from the object model to the relational model.
  • the maintenance of the object model needs to be implemented by another tool with low integration; and there is no integration of object/relational mapping technology, and manual integration has a large workload.
  • the third category is a profile-based object-relational mapping scheme.
  • This solution is represented by Hibernate technology.
  • This mapping scheme users need to provide a large number of configuration files. Users need to understand the association, inheritance, and combination of classes, and manually write the mapping rules of these classes and relationships into corresponding configuration files and mapping files.
  • the disadvantage of this technical solution is that it does not provide automated development tools, completely dependent on the manual labor of the user; difficult to maintain, configuration files, mapping rules, database construction scripts need to be written manually, any local modification will involve other places Modifications, errors can easily lead to errors during the modification process. Summary of the invention
  • a system for automatically establishing a relationship model comprising:
  • An object model information collection engine configured to obtain object model association information from the object model, and send the object model association information to an automatic conversion engine;
  • An automatic conversion engine configured to define a file according to a preset mapping rule, the object model Correlate information and object models to generate a relational model.
  • a method of automatically establishing a relationship model comprising the steps of:
  • a relationship model is automatically generated based on the mapping rules and object model association information and the object model.
  • the present invention collects object model association information from the object model and sets mapping rules, automatically generates a relation model according to the object model association information and mapping rules and the object model, and automatically generates a mapping file, thereby improving the object model to
  • the degree of automation of relational model mapping increases system integration, reduces manual integration effort, simplifies developer work, improves development efficiency, and reduces the error rate due to manual definition by developers.
  • only a simple mapping rule setting is required, and even if the default rule is not used, the automatic generation of the relational model and the automatic generation of the mapping file can be completed, and the work efficiency is greatly improved.
  • FIG. 1 is a structural diagram of a system according to an embodiment of the present invention.
  • FIG. 2 is a structural diagram of another system according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of an object model used in an embodiment of the present invention.
  • Figures 4a and 4b are schematic diagrams of a single-key entity class and a corresponding relational model, respectively.
  • Figures 5a and 5b are schematic diagrams of a composite primary key entity class, and
  • Figure 5c is a corresponding relational model.
  • Figure 6a is a schematic diagram of one-to-one entity classes and value types
  • Figure 6b and Figure 6c are diagrams
  • FIG. 7a is a schematic diagram of a one-way one-to-one relationship
  • FIG. 7b is a schematic diagram of a primary key-based relationship model corresponding to FIG. 7a.
  • Fig. 8a is a schematic diagram of a one-way one-to-many relationship
  • Fig. 8b, Fig. 8c and Fig. 8d are schematic diagrams of the relationship model corresponding to Fig. 8a, respectively.
  • Fig. 9a is a schematic diagram of a one-way multi-one relationship
  • Fig. 9b, Fig. 9c and Fig. 9d are schematic diagrams of the relationship model corresponding to Fig. 9a, respectively.
  • Figure 10a is a schematic diagram of a one-way many-to-many association relationship
  • Figure 10b is a schematic diagram of a relationship model corresponding to Figure 10a.
  • Fig. 11a is a schematic diagram of the inheritance relationship
  • Fig. 11b, Fig. 11c and Fig. lid are respectively schematic diagrams of the relationship model corresponding to Fig. 11a. Mode for carrying out the invention
  • FIG. 1 is a schematic diagram of an integrated development environment (IDE) system for automatically establishing a relationship model according to an embodiment of the present invention.
  • the system mainly includes an object model information collection engine and an automatic conversion engine.
  • the object model information collection engine collects the object model association information from the object model, and then sends the object model association information to the automatic conversion engine; the automatic conversion engine defines the file, the object model association information, and the object model according to the preset mapping rule. Generate mapping files and relational models, and users can use the resulting relational model to access the database.
  • the acquisition process of the object model information collection engine may be: traversing the object model and obtaining object model association information.
  • the object model association information includes an association relationship, an inheritance relationship, a combination relationship, a class name and a property list thereof, an attribute name and a type thereof, and the like;
  • the mapping rule definition file includes a class mapping rule, an attribute mapping rule, an association mapping rule, and an inheritance. Mapping rules, combination mapping rules, and so on.
  • FIG. 2 is another system structure of an embodiment of the present invention.
  • the system includes an object model information collection engine and an automatic conversion engine.
  • the automatic conversion engine includes a first automatic engine conversion and a model output tool, wherein the object model information collection engine The object model association information is collected from the object model, and then the object model association information is sent to the automatic conversion engine, and the automatic conversion engine generates the relationship model and the mapping file according to the preset mapping rule definition file and the object model association information and the object model.
  • the first automatic conversion engine generates a mapping file according to a preset mapping rule definition file, object model association information, and an object model
  • the model output tool generates a relational model according to the mapping file, and the user can utilize the obtained relational model to Access the database.
  • the model output tool is a Hibernate model output tool
  • the mapping file includes a Hibernate mapping file and a Hibernate configuration file.
  • the relational model exported by the Hibernate model output tool in the system shown in Figure 2 can only be a table-building script for data definition language (DDL) statements.
  • DDL data definition language
  • the embodiment of the invention adopts the above IDE system for automatically establishing a relationship model, and realizes the automatic establishment of a relationship model.
  • the method of the embodiment of the invention comprises the following steps:
  • Step S1 setting a mapping rule of the object model to the relational model to form a mapping rule definition file, and the object model information collecting engine collects the object model association information from the object model, and sends the object model association information to the automatic conversion engine.
  • the process of collecting the object model association information from the object model by the object model information collection engine may be: traversing the object model, and acquiring the object model association information.
  • Step S2 The automatic conversion engine automatically generates the relationship model according to the mapping rule and the object model association information and the object model. If the system shown in Figure 1 is used, the automatic conversion engine can further generate a mapping file. If the system shown in FIG. 2 is adopted, step S2 can be divided into the following two steps: The first automatic conversion engine generates a mapping file according to the mapping rule and the model association information and the object model; the model output tool generates the mapping file according to the mapping file. Relationship model. The implementation of the present invention is described below by a specific object model.
  • Fig. 3 is a UML diagram of an object model used in the embodiment of the present invention, and the legend used in the figure is a standard UML diagram legend.
  • the object model can be a domain object model designed in advance by the IDE.
  • the object model shown is divided into a customer domain, a user domain, an account domain, and a product domain.
  • the customer has a unique customer ID (customerld), the customer has multiple addresses (Address), each address includes two fields: country (country) and postal code (zipCode); one customer owns 0 ⁇ m accounts (Account), that is, a one-to-many relationship between the client and the account, where m is any positive integer.
  • the user group ( UserGroup ) uses a unique user group ID
  • the association between the user group and the client is a many-to-many association.
  • the attributes of the association are identified by the customer user group relationship (CustomerUserGroupRela); the user group and the user (User) are one-to-many associations. ; the user uses a unique user ID
  • a user contains 0 ⁇ n service numbers ( ServiceNumber ), 0 ⁇ i product ordering relationships ( ProductOrder ), and 0 ⁇ j payment relationships
  • n, i, and j are arbitrary positive integers; the service number uses a unique service number identifier ( serviceNumberid ), and the service number is divided into phone numbers.
  • OrderParameters and uniquely associated with a product ( Product ), where k is any positive integer.
  • the account uses a unique account ID ( accountld ); each payment relationship is uniquely associated with one account and is uniquely associated with an expense item (Feeitem ); Use a unique expense item identifier (f ee ltemld ).
  • the product uses a unique product identifier (productId).
  • the object model information collection engine collects the following object model association information from the above object model: 1) entity model, including entity type and value type (or structure type), entity type such as user, customer, etc., value type such as address, product Ordering relationship parameters, etc.; 2) Attribute model, according to the type of attribute can be divided into basic type and extended type, extended type includes extended type and structure type based on basic type; 3) association relationship, divided into one-way association and two-way association, The one-way association includes one-to-one association, one-to-many association, and many-to-one association.
  • the two-way association includes one-to-one association, one-to-many association, many-to-one association, many-to-many association, and the association may have its own Attributes; 4) inheritance relationship, only supports single-root inheritance; 5) combination relationship, including one-to-one combination and one-to-many combination.
  • mapping rules are described for these object model association information as well as the object model.
  • mapping rules of the entity model This includes mapping rules for entity types and mapping rules for value types.
  • the entity type mapping includes a mapping of a single key entity class ( SingleKeyEntity ) and a composite primary key (also known as a multi-primary key) entity class ( MuMKeyEntity ).
  • the mapping rules for single-key entity classes are: The class maps to a table of the same name or different name; the primary key attribute maps to the primary key of the table; the non-primary key attribute maps to the field of the table, and the type and constraints of the field can be set in the IDE.
  • the single-key entity class shown in Figure 4a maps to the relational model shown in Figure 4b according to the mapping rule.
  • the class and table name are single-key entities (SingleKeyEntity), the primary key attribute is the long (Long) identifier (id), and the non-primary key attribute includes the string (String) name (name) And description ( description ).
  • the mapping rules of the composite primary key entity class are: The class maps to the table, the table name corresponding to the class can be the same name or set in the IDE; the primary key attribute is mapped to the primary key of the table, if the primary key is the primary key class, Then all the attributes of the primary key class are mapped to the composite primary key field of the table; the non-primary key attributes are mapped to the fields of the table, and the type and constraints of the field can be set in the IDE.
  • the composite primary key entity class includes two forms as shown in FIG. 5a and FIG. 5b.
  • the entity class primary key is a composite primary key based on the entity attribute; in FIG.
  • the entity class The primary key is a composite primary key based on a separate primary key class.
  • both of the composite primary key class entities shown in Fig. 5a and Fig. 5b are mapped to the relational model as shown in Fig. 5c.
  • value type refers to the structure type axe custom type, which usually exists as an attribute of an entity, and is divided into a single member attribute and a collection attribute. Therefore, the relationship between the value type and the entity type is one-way ( From entity type to value type) One-to-one or one-to-many association.
  • mapping rules mapped to the same table can be used:
  • the entity class maps to the table, and the table name corresponding to the class can be the same name or set in the IDE; the entity primary key attribute is mapped to the primary key of the table; Multiple attributes of a value type are mapped to multiple fields of the table corresponding to the entity class; non-primary key attributes are mapped to fields of the table, where the type and constraints of the field can be set in the IDE.
  • the mapping rule 1 the object model as shown in Fig. 6a can be mapped to the relational model as shown in Fig. 6b.
  • mapping rules 2 Entity classes and value types are mapped to two separate tables; the table corresponding to the value type adds the primary key field of the entity class as the primary and foreign keys of the value type. It can be seen that, according to mapping rule 2, the entity class and the value type are respectively mapped into two tables, and the primary key and the foreign key are used for association, so that the object model shown in FIG. 6a can be mapped to the relationship shown in FIG. 6c according to the mapping rule 2. model.
  • mapping rules For a mapping of a multi-value type, the following mapping rules can be used: The entity class and the value type are respectively mapped into two independent tables; the primary key field of the entity class is added to the table corresponding to the value type, as a foreign key of the value type, Value types have separate primary key fields. Using this mapping rule, the resulting object model map is shown in Figure 6d.
  • the class and table names include Customer entity type ( CustomerEntityType ), address value type ( Address ValueType ), attributes include id, name, description ( desc ), country, address, zipcode, etc.
  • the mapping rules of the attribute model As mentioned earlier, depending on the type of the attribute, it can be divided into a basic type and an extended type, and the extended type includes an extended type and a structure type based on the basic type.
  • the basic types include primitive types and big data types.
  • the primitive types include integer ( integer ), long ( long ), short ( short ), float ( float ) string ( string ), date (date ), time, etc.
  • Big data types include binary, text, and so on.
  • the basic types are mapped to the fields of the database, and the type of each primitive type mapped to the field can be specified by using the given default value or by the user, such as the length of the string.
  • the mapping rules are the same as the corresponding basic types.
  • the mapping rules of associations are the mapping rules of associations.
  • One-way association mapping rules can be divided into one-way one-to-one associations, one-way one-to-many associations, one-way many-to-one associations, and one-way many-to-many associations. Their mapping rules are described below.
  • the associated class refers to the class pointed to by the associated arrow in the 1JML graph, and the associated class refers to the class corresponding to the other side of the associated line in the UML graph.
  • the one-way one-to-one association relationship can adopt the following three mapping rules.
  • the first mapping rule is the same as the one-to-one value type mapping rule described above, and the associated class and the associated class are merged into one table, specifically: the associated class maps to the table, and the table name can have the same name or in the IDE. Set; the properties of the associated class and the associated class are mapped to the fields of the table, where the type and constraints of the field can be set in the IDE.
  • the second mapping rule is based on the primary key's association mapping implementation, the primary key of a table as another I, a unique foreign key of a table, according to which the association relationship as shown in Fig. 7a can be mapped to the relational model as shown in Fig. 7b.
  • the second mapping rule is: the associated class and the associated class are respectively mapped to two tables; the table corresponding to the associated class uses the primary key of the associated class as its primary key and foreign key field, as shown in Figure 7b (orderld) Field.
  • the class and table names include the order relationship entity type (ProductOrderEntityType), the order relationship description type (ProductOrder DexcriptionType), and the attributes include orderld, user ID (userld), productId> description, and so on.
  • the third mapping rule is based on the association mapping of foreign keys.
  • the third mapping rule is: The associated class and the associated class are mapped to two tables respectively; the table corresponding to the associated class uses the primary key of the associated class as its own foreign key field, and uses a separate primary key field. Based on the association table mapping implementation, considering the performance issues of multi-table association, the third mapping rule is not recommended.
  • the first mapping rule implements association by a foreign key, maps the object relationship as shown in FIG. 8a to the relational model as shown in FIG. 8b, and adds a foreign key field customerldo in the account entity type (AccountEntityType) 4 table.
  • the mapping rules are as follows: The associated class and the associated class are mapped to two tables respectively; the table corresponding to the associated class uses the primary key of the associated class as its foreign key field, as shown in the customei'Id field in Figure 8b, the associated class has its own Primary key attribute.
  • the attributes also include title (title), balance, and so on.
  • the second mapping rule and the third mapping rule both use the connection table to implement association, and respectively map the object relationships as shown in FIG. 8a as shown in FIG. 8c and FIG. 8d.
  • a connection table customer account association CustomerAccountAssoc
  • the association table does not have its own primary key, all of which use the foreign key unique identifier, and do not need to specify the primary key generation manner.
  • the second mapping rule is: the association class and the associated class are respectively mapped to two Table; create a new join table, the fields in the table only contain the associated class and the associated class Primary key field.
  • the association table has its own primary key association identifier.
  • the third mapping rule is: The associated class and the associated class are mapped to two tables respectively; Create a new connection In the table, the fields in the table contain only the primary key fields of the associated class and the associated class, and the associated table has its own primary key field.
  • a third mapping rule is used.
  • mapping rules can be used for one-way many-to-one association.
  • the first mapping rule is based on the implementation of a foreign key, and the object relationship of Figure 9a is mapped to the relational model as shown in Figure 9b.
  • the first mapping rule is: The associated class and the associated class are mapped to two tables respectively; the associated class uses the primary key attribute of the associated class as the foreign key field.
  • the second mapping rule and the third mapping rule are based on the implementation of the association table.
  • a new association table is created to order the product association (OrderProductAssoc), and two foreign keys are used to implement the association.
  • the association of the table, the association table obtained according to the second mapping rule shown in FIG. 9c does not belong to its own primary key, and the association table obtained according to the third mapping rule shown in FIG. 9d has its own primary key assocld, which needs to be specified.
  • the second mapping rule is: The associated class and the associated class are mapped to two tables respectively; a new join table is created, and the fields in the table only contain the primary key fields of the associated class and the associated class.
  • the third mapping rule is: The associated class and the associated class are mapped to two tables respectively; a new connection table is created, and the fields in the table only contain the primary key fields of the associated class and the associated class, and the connection table has its own primary key at the same time. Field.
  • the class and table name also includes the product order entity type (Product OrderEntityType) 5, product type (ProductType) 5 and so on.
  • One-way many-to-many association uses the following mapping rules: The associated class and the associated class are mapped to two tables respectively, the attribute object is mapped to a connection table; a new connection table is created, and the fields in the table only contain the association class And the primary key field of the associated class, a field of the join table and the previous one The primary key fields are combined as a primary key.
  • mapping rule the object relationship as shown in FIG. 10a is mapped to the relationship model as shown in FIG. 10b.
  • a one-way many-to-many association can be converted into two one-to-many associations, so a one-way many-to-many association must be implemented using the join table as shown in Figure 10b, especially if the association itself has some Some properties.
  • connection table-based mapping rules there is a value object user group association type.
  • AssociationType 4, user group entity type ( UserGroupEntityType ) 4, user entity type ( UserEntityType ) 4, attributes also include status (status) and so on.
  • the two-way association mapping rule is the same as the one-way association mapping rule, and is not described here. Specifically:
  • Two-way one-to-one association mapping rules are the same as one-to-one one-to-one association mapping rules;
  • the bidirectional one-to-many association mapping rule is the same as the one-way one-to-many association mapping rule, and the Han-to-many-to-one association mapping rule is the same as the one-to-many association mapping rule;
  • mapping rule of the Han-to-many-to-many association is the same as the rule mapping of the one-way many-to-many association.
  • mapping rules of the inheritance relationship is the same as the rule mapping of the one-way many-to-many association.
  • the embodiment of the present invention provides three mapping rules for inheriting the mapping to the relational model.
  • the first mapping rule uses each class hierarchy to map to one table, and the second mapping rule uses each subclass to map to one table.
  • the third mapping rule maps to a table using each concrete class.
  • the first mapping rule is: All attributes of each level of the class are superimposed into a table; the parent class uses the type field to indicate the level in which it is located; the table corresponding to all the sub-class levels shares the parent class's primary key as a foreign key. Uniquely identifies a record.
  • the object model shown in Figure 11a only needs three table implementations. As shown in Figure ib, the attributes of the class of the same inheritance hierarchy are implemented in a table, which inevitably leads to redundant attributes. The table corresponding to the subclass hierarchy and the parent class hierarchy are one-to-one. There are many things to consider in the first mapping rule, such as the field name of the same hierarchical class cannot be duplicated, the encoding of the subclass type, and many different types of fields are mixed and stored in one table, which is not easy to manage.
  • the second mapping rule is: Each subclass maps to a separate table; the table corresponding to each subclass uses the parent class's primary key as a foreign key to uniquely identify a record.
  • the second mapping rule is used to obtain the relational model as shown in Figure 11c.
  • the advantages of the second mapping rule are: It can clearly express the inheritance relationship between classes. It is more suitable for inheritance relationships with more than three layers, and each subclass can have its own primary key generation strategy. The disadvantages are: Multi-table operations are required and performance is degraded.
  • the third mapping rule is: Each concrete class maps to a table containing the union of all the fields from the topmost parent class to the child class.
  • the relationship model obtained by using the third mapping rule as shown in FIG. 11a is shown in FIG.
  • the limitation of the third mapping rule is: When there are more inheritance levels of the class, there are more redundant fields in the subclass table; the generation of the primary key needs to consider a unified generation strategy, and the subclass does not allow its own primary key generation strategy; Subclasses cannot have fields with the same name. Fifth, the mapping rules of the combination relationship.
  • the combination relationship between objects includes a one-to-one combination relationship and a one-to-many combination relationship, and the mapping rules of the two types are similar to the mapping rules of value types.
  • the first mapping rule mapped to the same table may be used: the associated attribute class is mapped to the table, and the table name corresponding to the class may have the same name or
  • the primary key attribute of the associated attribute class is mapped to the primary key of the table; multiple attributes of the associated attribute class are mapped to multiple fields of the table corresponding to the associated attribute class; the non-primary key attribute is mapped to the field of the table, wherein the type of the field and Constraints can be set in the IDE.
  • the second mapping rule can also be used: the associated attribute class and the associated attribute class are respectively mapped into two independent tables; the primary key field of the associated attribute class is added to the table corresponding to the associated attribute class. , as the primary and foreign keys of the associated attribute class.
  • the associated attribute class and the associated attribute class are respectively mapped into two tables, and the primary key and the foreign key are used for association.
  • mapping rules may be adopted: the associated attribute class and the associated attribute class are respectively mapped into two independent tables; the primary key field of the associated attribute class is added to the table corresponding to the associated attribute class, As a foreign key of the associated attribute class, the associated attribute class has a separate primary key field.

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)

Abstract

Un procédé de création automatique de modèle relationnel consiste à fixer une règle de mappage d'un modèle d'objet vers un modèle relationnel, et à recueillir des informations relatives à ce modèle d'objet, à créer automatiquement un modèle relationnel fondé sur la règle de mappage, sur les informations relatives au modèle objet recueillies et sur le modèle d'objet. Un système de création automatique de modèle relationnel comprend: un moteur de recueil d'informations de modèle d'objet destiné à recueillir des informations relationnelles parmi les objets, l'envoi de ces informations relationnelles de modèle d'objet au moteur de conversion automatique, un moteur de conversion automatique destiné à créer automatiquement un modèle relationnel fondé sur le fichier définissant la règle de mappage prédéfini et sur les informations relatives au modèle d'objet et sur le modèle d'objet.
PCT/CN2007/000218 2006-05-26 2007-01-19 Procédé et système de création automatique de modèle relationnel WO2007137468A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200610078423.0 2006-05-26
CN2006100784230A CN101046810B (zh) 2006-05-26 2006-05-26 自动建立关系模型的系统及其方法

Publications (1)

Publication Number Publication Date
WO2007137468A1 true WO2007137468A1 (fr) 2007-12-06

Family

ID=38771426

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/000218 WO2007137468A1 (fr) 2006-05-26 2007-01-19 Procédé et système de création automatique de modèle relationnel

Country Status (2)

Country Link
CN (1) CN101046810B (fr)
WO (1) WO2007137468A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110955736A (zh) * 2019-11-06 2020-04-03 科大国创软件股份有限公司 一种基础数据的管理模型建模方法
CN110955805A (zh) * 2019-12-18 2020-04-03 重庆大数据研究院有限公司 一种基于映射关系的数据自动化处理方法
CN111008189A (zh) * 2019-11-26 2020-04-14 浙江电子口岸有限公司 一种动态数据模型构建方法
CN111382198A (zh) * 2018-12-28 2020-07-07 中国移动通信集团山西有限公司 数据还原方法、装置、设备及存储介质
CN113377871A (zh) * 2021-06-22 2021-09-10 特赞（上海）信息科技有限公司 数据同步方法、装置及存储介质

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102541867A (zh) * 2010-12-15 2012-07-04 金蝶软件（中国）有限公司 数据字典生成方法及系统
CN103186620A (zh) * 2011-12-31 2013-07-03 上海可鲁系统软件有限公司 一种cim模型映射方法
CN103186628B (zh) * 2011-12-31 2016-09-28 上海可鲁系统软件有限公司 一种公共信息模型与关系型数据库之间的映射方法
CN102999575B (zh) * 2012-11-12 2015-10-14 北京华通伟业科技发展有限公司 一种Hibernate映射配置文件的配置方法及系统
CN105956054A (zh) * 2016-04-27 2016-09-21 国家电网公司 基于关系型数据库的电网cim模型数据实现存储的方法
CN108630319A (zh) * 2017-03-21 2018-10-09 中国移动通信有限公司研究院 一种基于医疗数据建模的预测方法及装置
CN108491364A (zh) * 2018-01-25 2018-09-04 苏州麦迪斯顿医疗科技股份有限公司 医疗护理文书管理系统
CN108509485B (zh) * 2018-02-07 2021-06-22 深圳壹账通智能科技有限公司 数据的预处理方法、装置、计算机设备和存储介质
CN109542409B (zh) * 2018-11-28 2022-09-30 中国海洋石油集团有限公司 一种基于面向对象设计思想的存储方法及装置
CN110826151B (zh) * 2019-11-15 2023-01-24 国家电网有限公司 电动汽车模型设计方法
CN111506640B (zh) * 2020-04-21 2023-06-30 北京中电普华信息技术有限公司 映射方法及装置
CN111797278A (zh) * 2020-05-19 2020-10-20 武汉乐程软工科技有限公司 一种映射关联对象与关系的方法
CN111797277A (zh) * 2020-05-19 2020-10-20 武汉乐程软工科技有限公司 映射对象系统与关系系统的方法、装置、计算机读存储介质及终端设备
CN112199254B (zh) * 2020-10-12 2022-05-17 平安科技（深圳）有限公司 数据模型的扫描方法、系统、计算机设备及存储介质
CN114547085B (zh) * 2022-03-22 2023-05-05 中国铁塔股份有限公司 一种数据处理方法、装置、电子设备及存储介质
CN115185982A (zh) * 2022-09-14 2022-10-14 浩鲸云计算科技股份有限公司 一种基于数据集编排的数据准备方法及系统
US11973660B1 (en) * 2022-12-09 2024-04-30 Arista Networks, Inc. Method and system for data model mapping for network management

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1137320A (zh) * 1993-10-29 1996-12-04 瓦尔数据公司 用于建立关系型数据库模式的语义目标模型化系统
WO1996041282A1 (fr) * 1995-06-07 1996-12-19 Wall Data Incorporated Systeme informatique de creation de modeles d'objets semantiques a partir de schemas de bases de donnees relationnelles existantes
CN1773453A (zh) * 2004-11-10 2006-05-17 东软集团有限公司 基于数据定义的系统构建方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1137320A (zh) * 1993-10-29 1996-12-04 瓦尔数据公司 用于建立关系型数据库模式的语义目标模型化系统
WO1996041282A1 (fr) * 1995-06-07 1996-12-19 Wall Data Incorporated Systeme informatique de creation de modeles d'objets semantiques a partir de schemas de bases de donnees relationnelles existantes
CN1773453A (zh) * 2004-11-10 2006-05-17 东软集团有限公司 基于数据定义的系统构建方法

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111382198A (zh) * 2018-12-28 2020-07-07 中国移动通信集团山西有限公司 数据还原方法、装置、设备及存储介质
CN111382198B (zh) * 2018-12-28 2023-09-19 中国移动通信集团山西有限公司 数据还原方法、装置、设备及存储介质
CN110955736A (zh) * 2019-11-06 2020-04-03 科大国创软件股份有限公司 一种基础数据的管理模型建模方法
CN110955736B (zh) * 2019-11-06 2023-05-12 科大国创软件股份有限公司 一种基础数据的管理模型建模方法
CN111008189A (zh) * 2019-11-26 2020-04-14 浙江电子口岸有限公司 一种动态数据模型构建方法
CN111008189B (zh) * 2019-11-26 2023-08-25 浙江电子口岸有限公司 一种动态数据模型构建方法
CN110955805A (zh) * 2019-12-18 2020-04-03 重庆大数据研究院有限公司 一种基于映射关系的数据自动化处理方法
CN110955805B (zh) * 2019-12-18 2023-08-25 重庆大数据研究院有限公司 一种基于映射关系的数据自动化处理方法
CN113377871A (zh) * 2021-06-22 2021-09-10 特赞（上海）信息科技有限公司 数据同步方法、装置及存储介质
CN113377871B (zh) * 2021-06-22 2024-03-22 特赞（上海）信息科技有限公司 数据同步方法、装置及存储介质

Also Published As

Publication number Publication date
CN101046810A (zh) 2007-10-03
CN101046810B (zh) 2010-09-08

Similar Documents

Publication Publication Date Title
WO2007137468A1 (fr) Procédé et système de création automatique de modèle relationnel
JP5964027B2 (ja) ビジネスネットワーク管理発見およびビジネスネットワーク管理集約のためのシステムおよび方法
US20080222192A1 (en) Method and system for transferring information using metabase
CN100484039C (zh) 网络管理装置与网络管理方法
EP1604486B1 (fr) Modele relationnel pour information de gestion dans des dispositifs de reseau
US20040201600A1 (en) Methods and system for providing an XML-based interface description language
US20090154363A1 (en) Method of resolving network address to host names in network flows for network device
JP2005182835A (ja) 異種のデータソースのためのデータサーバを生成する方法
CN102567026B (zh) 移动应用构建系统和移动应用构建方法
WO2015062182A1 (fr) Procédé de virtualisation de données hétérogènes réparties à grande échelle
CN110298189A (zh) 数据库权限管理方法及设备
US8380549B2 (en) Architectural design for embedded support application software
CN104680303A (zh) 一种基于snmp的业务指标监控系统的构建方法
CN112685032A (zh) 一种基于spring boot框架的动态api可视化生成方法
CN115617776A (zh) 一种数据管理系统及方法
US7970867B2 (en) Hypermedia management system
CN106657282B (zh) 一种换流站设备运行状态信息的集成方法及装置
CN101312457A (zh) 在发行-预订网络中使用的方法、路由器、设备和该网络
CN100369443C (zh) 遵循snmp/cim协议中间件映射的方法
WO2017000678A1 (fr) Procédé et système de communication par paquets entre des systèmes de gestion de réseau
WO2012167657A1 (fr) Procédé de transfert d'évènement et serveur de modèle d'information commun (cim)
CN108388809A (zh) 一种数据范围控制方法和系统
CN112182305A (zh) 一种基于xml规则的xml解析模块、解析方法和配置数据的管理方法
US10496557B1 (en) Transport protocol for disparate entity applications
WO2012083631A1 (fr) Procédé permettant de gérer des paramètres de dispositif d'un système d'identification radiofréquence (rfid) et système rfid

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07702149

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 07702149

Country of ref document: EP

Kind code of ref document: A1