📄 inheritance_mapping.po
字号:
" <subclass name=\"CashPayment\" discriminator-value=\"CASH\">\n"" <join table=\"CASH_PAYMENT\">\n"" <key column=\"PAYMENT_ID\"/>\n"" ...\n"" </join>\n"" </subclass>\n"" <subclass name=\"ChequePayment\" discriminator-value=\"CHEQUE\">\n"" <join table=\"CHEQUE_PAYMENT\" fetch=\"select\">\n"" <key column=\"PAYMENT_ID\"/>\n"" ...\n"" </join>\n"" </subclass>\n""</class>]]>"msgstr """<![CDATA[<class name=\"Payment\" table=\"PAYMENT\">\n"" <id name=\"id\" type=\"long\" column=\"PAYMENT_ID\">\n"" <generator class=\"native\"/>\n"" </id>\n"" <discriminator column=\"PAYMENT_TYPE\" type=\"string\"/>\n"" <property name=\"amount\" column=\"AMOUNT\"/>\n"" ...\n"" <subclass name=\"CreditCardPayment\" discriminator-value=\"CREDIT\">\n"" <join table=\"CREDIT_PAYMENT\">\n"" <key column=\"PAYMENT_ID\"/>\n"" <property name=\"creditCardType\" column=\"CCTYPE\"/>\n"" ...\n"" </join>\n"" </subclass>\n"" <subclass name=\"CashPayment\" discriminator-value=\"CASH\">\n"" <join table=\"CASH_PAYMENT\">\n"" <key column=\"PAYMENT_ID\"/>\n"" ...\n"" </join>\n"" </subclass>\n"" <subclass name=\"ChequePayment\" discriminator-value=\"CHEQUE\">\n"" <join table=\"CHEQUE_PAYMENT\" fetch=\"select\">\n"" <key column=\"PAYMENT_ID\"/>\n"" ...\n"" </join>\n"" </subclass>\n""</class>]]>"#: index.docbook:127msgid """The optional <literal>fetch=\"select\"</literal> declaration tells Hibernate ""not to fetch the <literal>ChequePayment</literal> subclass data using an ""outer join when querying the superclass."msgstr """la declaración opcional <literal>fetch=\"select\"</literal> dice a ""Hibernate que no recupere los datos de la subclase <literal>ChequePayment</""literal> usando una unión externa (outer join) al consultar la ""superclase."#: index.docbook:136msgid "Mixing table per class hierarchy with table per subclass"msgstr "Mezclando tabla por jerarquía de clases con tabla por subclase"#: index.docbook:138msgid """You may even mix the table per hierarchy and table per subclass strategies ""using this approach:"msgstr """Puedes incluso mezclar las estrategias de tabla po jerarquía y tabla ""por subclase usando este enfoque:"#: index.docbook:143msgid """<![CDATA[<class name=\"Payment\" table=\"PAYMENT\">\n"" <id name=\"id\" type=\"long\" column=\"PAYMENT_ID\">\n"" <generator class=\"native\"/>\n"" </id>\n"" <discriminator column=\"PAYMENT_TYPE\" type=\"string\"/>\n"" <property name=\"amount\" column=\"AMOUNT\"/>\n"" ...\n"" <subclass name=\"CreditCardPayment\" discriminator-value=\"CREDIT\">\n"" <join table=\"CREDIT_PAYMENT\">\n"" <property name=\"creditCardType\" column=\"CCTYPE\"/>\n"" ...\n"" </join>\n"" </subclass>\n"" <subclass name=\"CashPayment\" discriminator-value=\"CASH\">\n"" ...\n"" </subclass>\n"" <subclass name=\"ChequePayment\" discriminator-value=\"CHEQUE\">\n"" ...\n"" </subclass>\n""</class>]]>"msgstr """<![CDATA[<class name=\"Payment\" table=\"PAYMENT\">\n"" <id name=\"id\" type=\"long\" column=\"PAYMENT_ID\">\n"" <generator class=\"native\"/>\n"" </id>\n"" <discriminator column=\"PAYMENT_TYPE\" type=\"string\"/>\n"" <property name=\"amount\" column=\"AMOUNT\"/>\n"" ...\n"" <subclass name=\"CreditCardPayment\" discriminator-value=\"CREDIT\">\n"" <join table=\"CREDIT_PAYMENT\">\n"" <property name=\"creditCardType\" column=\"CCTYPE\"/>\n"" ...\n"" </join>\n"" </subclass>\n"" <subclass name=\"CashPayment\" discriminator-value=\"CASH\">\n"" ...\n"" </subclass>\n"" <subclass name=\"ChequePayment\" discriminator-value=\"CHEQUE\">\n"" ...\n"" </subclass>\n""</class>]]>"#: index.docbook:145msgid """For any of these mapping strategies, a polymorphic association to the root ""<literal>Payment</literal> class is mapped using <literal><many-to-one>""</literal>."msgstr """Para cualquiera de estas estrategias de mapeo, una asociación ""polimórfica a la clase raíz <literal>Payment</literal> es ""mapeada usando <literal><many-to-one></literal>."#: index.docbook:151msgid """<![CDATA[<many-to-one name=\"payment\" column=\"PAYMENT_ID\" class=\"Payment""\"/>]]>"msgstr """<![CDATA[<many-to-one name=\"payment\" column=\"PAYMENT_ID\" class=\"Payment""\"/>]]>"#: index.docbook:156msgid "Table per concrete class"msgstr "Tabla por clase concreta"#: index.docbook:158msgid """There are two ways we could go about mapping the table per concrete class ""strategy. The first is to use <literal><union-subclass></literal>."msgstr """Podríamos ir de dos maneras a la estrategia de mapeo de tabla por ""clase concreta. La primera es usar <literal><union-subclass></literal>."#: index.docbook:163msgid """<![CDATA[<class name=\"Payment\">\n"" <id name=\"id\" type=\"long\" column=\"PAYMENT_ID\">\n"" <generator class=\"sequence\"/>\n"" </id>\n"" <property name=\"amount\" column=\"AMOUNT\"/>\n"" ...\n"" <union-subclass name=\"CreditCardPayment\" table=\"CREDIT_PAYMENT\">\n"" <property name=\"creditCardType\" column=\"CCTYPE\"/>\n"" ...\n"" </union-subclass>\n"" <union-subclass name=\"CashPayment\" table=\"CASH_PAYMENT\">\n"" ...\n"" </union-subclass>\n"" <union-subclass name=\"ChequePayment\" table=\"CHEQUE_PAYMENT\">\n"" ...\n"" </union-subclass>\n""</class>]]>"msgstr """<![CDATA[<class name=\"Payment\">\n"" <id name=\"id\" type=\"long\" column=\"PAYMENT_ID\">\n"" <generator class=\"sequence\"/>\n"" </id>\n"" <property name=\"amount\" column=\"AMOUNT\"/>\n"" ...\n"" <union-subclass name=\"CreditCardPayment\" table=\"CREDIT_PAYMENT\">\n"" <property name=\"creditCardType\" column=\"CCTYPE\"/>\n"" ...\n"" </union-subclass>\n"" <union-subclass name=\"CashPayment\" table=\"CASH_PAYMENT\">\n"" ...\n"" </union-subclass>\n"" <union-subclass name=\"ChequePayment\" table=\"CHEQUE_PAYMENT\">\n"" ...\n"" </union-subclass>\n""</class>]]>"#: index.docbook:165msgid """Three tables are involved for the subclasses. Each table defines columns for ""all properties of the class, including inherited properties."msgstr """Están implicadas tres tablas. Cada tabla define columnas para todas ""las propiedades de la clase, inccluyendo las propiedades heredadas."#: index.docbook:170msgid """The limitation of this approach is that if a property is mapped on the ""superclass, the column name must be the same on all subclass tables. (We ""might relax this in a future release of Hibernate.) The identity generator ""strategy is not allowed in union subclass inheritance, indeed the primary ""key seed has to be shared accross all unioned subclasses of a hierarchy."msgstr """La limitación de este enfoque es que si una propiedad es mapeada en ""la superclase, el nombre de columna debe ser el mismo en todas las tablas de ""subclase. (Podríamos relajar esto en un lanzamiento futuro de ""Hibernate.) La estrategia de generador de indentidad no está ""permitida en la herencia de unión de subclase, de hecho la semilla de ""clave primaria tiene que ser compartida a través de todas las ""subclases unidas de una jerarquía."#: index.docbook:179msgid """If your superclass is abstract, map it with <literal>abstract=\"true\"</""literal>. Of course, if it is not abstract, an additional table (defaults to ""<literal>PAYMENT</literal> in the example above) is needed to hold instances ""of the superclass."msgstr """UNTRANSLATED! If your superclass is abstract, map it with <literal>abstract=""\"true\"</literal>. Of course, if it is not abstract, an additional table ""(defaults to <literal>PAYMENT</literal> in the example above) is needed to ""hold instances of the superclass."#: index.docbook:189msgid "Table per concrete class, using implicit polymorphism"msgstr "Tabla por clase concreta, usando polimorfismo implícito"#: index.docbook:191msgid "An alternative approach is to make use of implicit polymorphism:"msgstr "Un enfoque alternativo es hacer uso de polimorfismo implícito:"#: index.docbook:195msgid """<![CDATA[<class name=\"CreditCardPayment\" table=\"CREDIT_PAYMENT\">\n"" <id name=\"id\" type=\"long\" column=\"CREDIT_PAYMENT_ID\">\n"" <generator class=\"native\"/>\n"" </id>\n"" <property name=\"amount\" column=\"CREDIT_AMOUNT\"/>\n"" ...\n""</class>\n""\n""<class name=\"CashPayment\" table=\"CASH_PAYMENT\">\n"" <id name=\"id\" type=\"long\" column=\"CASH_PAYMENT_ID\">\n"" <generator class=\"native\"/>\n"" </id>\n"" <property name=\"amount\" column=\"CASH_AMOUNT\"/>\n"" ...\n""</class>\n""\n""<class name=\"ChequePayment\" table=\"CHEQUE_PAYMENT\">\n"" <id name=\"id\" type=\"long\" column=\"CHEQUE_PAYMENT_ID\">\n"" <generator class=\"native\"/>\n"" </id>\n"" <property name=\"amount\" column=\"CHEQUE_AMOUNT\"/>\n"" ...\n""</class>]]>"msgstr """<![CDATA[<class name=\"CreditCardPayment\" table=\"CREDIT_PAYMENT\">\n"" <id name=\"id\" type=\"long\" column=\"CREDIT_PAYMENT_ID\">\n"" <generator class=\"native\"/>\n"" </id>\n"" <property name=\"amount\" column=\"CREDIT_AMOUNT\"/>\n"" ...\n""</class>\n""\n""<class name=\"CashPayment\" table=\"CASH_PAYMENT\">\n"" <id name=\"id\" type=\"long\" column=\"CASH_PAYMENT_ID\">\n"" <generator class=\"native\"/>\n"" </id>\n"" <property name=\"amount\" column=\"CASH_AMOUNT\"/>\n"" ...\n""</class>\n""\n""<class name=\"ChequePayment\" table=\"CHEQUE_PAYMENT\">\n"" <id name=\"id\" type=\"long\" column=\"CHEQUE_PAYMENT_ID\">\n"" <generator class=\"native\"/>\n"" </id>\n"" <property name=\"amount\" column=\"CHEQUE_AMOUNT\"/>\n"" ...\n""</class>]]>"#: index.docbook:197msgid """Notice that nowhere do we mention the <literal>Payment</literal> interface ""explicitly. Also notice that properties of <literal>Payment</literal> are ""mapped in each of the subclasses. If you want to avoid duplication, consider ""using XML entities (e.g. <literal>[ <!ENTITY allproperties SYSTEM ""\"allproperties.xml\"> ]</literal> in the <literal>DOCTYPE</literal> ""declartion and <literal>&allproperties;</literal> in the mapping)."msgstr """Nota que en ningún sitio mencionamos la interface <literal>Payment</""literal> explícitamente. Nota además que las propiedades de "
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -