[ https://issues.jboss.org/browse/TEIID-2881?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2881: ------------------------------------ As I'm moving along on this, thought I would post my comments about the MetadataProcessor and what the object to relational mapping will be (which is slightly different than the object translator). * <p> * Here are the rules that are being followed to convert an Object to a row. * </p> * <li>Class</li> * Each class is mapped to a table. * </br> * <li>Attributes</li> * Get/Is methods will be become table columns. * </br> * <li>One-to-one association</li> * The classes on both sides will be merged into a one table. The nameInSource for the attributes in the class * contained within the root class will be assigned based on this format: "getMethod" name + "." + attribute * </br> * Example: Person contains Contact (getContact) and Contact has getter method getPhoneNumber * so the nameInSource for the column would become Contact.PhoneNumber * </br> * <li>One-to-many association</li> * The classes on both sides are mapped to two tables. The root class will have primary key created. The * table for the "many" side will have a foreign created. * </br> * When an attribute is included from the many side (children), the total number of rows will be multiplied by * by the number of children objects. * <p> * <b>Decisions</b> * <li>User will need to decide what will be the primary key. Will the key to the cache or a real attribute on the root class * will be used as the primary key.</li> * -- This message was sent by Atlassian JIRA (v6.2.3#6260)