association_mapping.po

hibernate-distribution-3.3.1.GA-dist.zip源码

msgid ""
"<![CDATA[<class name=\"Person\">\n"
"    <id name=\"id\" column=\"personId\">\n"
"        <generator class=\"native\"/>\n"
"    </id>\n"
"    <one-to-one name=\"address\"/>\n"
"</class>\n"
"\n"
"<class name=\"Address\">\n"
"    <id name=\"id\" column=\"personId\">\n"
"        <generator class=\"foreign\">\n"
"            <param name=\"property\">person</param>\n"
"        </generator>\n"
"    </id>\n"
"    <one-to-one name=\"person\" \n"
"        constrained=\"true\"/>\n"
"</class>]]>"
msgstr ""
"<![CDATA[<class name=\"Person\">\n"
"    <id name=\"id\" column=\"personId\">\n"
"        <generator class=\"native\"/>\n"
"    </id>\n"
"    <one-to-one name=\"address\"/>\n"
"</class>\n"
"\n"
"<class name=\"Address\">\n"
"    <id name=\"id\" column=\"personId\">\n"
"        <generator class=\"foreign\">\n"
"            <param name=\"property\">person</param>\n"
"        </generator>\n"
"    </id>\n"
"    <one-to-one name=\"person\" \n"
"        constrained=\"true\"/>\n"
"</class>]]>"

#: index.docbook:208
msgid "Bidirectional associations with join tables"
msgstr "Asociaciones bidireccionales con tablas de uni&#x00f3;n"

#: index.docbook:213
msgid ""
"A <emphasis>bidirectional one-to-many association on a join table</"
"emphasis>. Note that the <literal>inverse=\"true\"</literal> can go on "
"either end of the association, on the collection, or on the join."
msgstr ""
"Una <emphasis>asociaci&#x00f3;n bidireccional uno-a-muchos en una tabla de "
"uni&#x00f3;n</emphasis>. Observa que el <literal>inverse=\"true\"</literal> "
"puede ir a cualquier lado de la asociaci&#x00f3;n, en la colecci&#x00f3;n, o "
"en la uni&#x00f3;n."

#: index.docbook:219
msgid ""
"<![CDATA[<class name=\"Person\">\n"
"    <id name=\"id\" column=\"personId\">\n"
"        <generator class=\"native\"/>\n"
"    </id>\n"
"    <set name=\"addresses\" \n"
"        table=\"PersonAddress\">\n"
"        <key column=\"personId\"/>\n"
"        <many-to-many column=\"addressId\"\n"
"            unique=\"true\"\n"
"            class=\"Address\"/>\n"
"    </set>\n"
"</class>\n"
"\n"
"<class name=\"Address\">\n"
"    <id name=\"id\" column=\"addressId\">\n"
"        <generator class=\"native\"/>\n"
"    </id>\n"
"    <join table=\"PersonAddress\" \n"
"        inverse=\"true\" \n"
"        optional=\"true\">\n"
"        <key column=\"addressId\"/>\n"
"        <many-to-one name=\"person\"\n"
"            column=\"personId\"\n"
"            not-null=\"true\"/>\n"
"    </join>\n"
"</class>]]>"
msgstr ""
"<![CDATA[<class name=\"Person\">\n"
"    <id name=\"id\" column=\"personId\">\n"
"        <generator class=\"native\"/>\n"
"    </id>\n"
"    <set name=\"addresses\" \n"
"        table=\"PersonAddress\">\n"
"        <key column=\"personId\"/>\n"
"        <many-to-many column=\"addressId\"\n"
"            unique=\"true\"\n"
"            class=\"Address\"/>\n"
"    </set>\n"
"</class>\n"
"\n"
"<class name=\"Address\">\n"
"    <id name=\"id\" column=\"addressId\">\n"
"        <generator class=\"native\"/>\n"
"    </id>\n"
"    <join table=\"PersonAddress\" \n"
"        inverse=\"true\" \n"
"        optional=\"true\">\n"
"        <key column=\"addressId\"/>\n"
"        <many-to-one name=\"person\"\n"
"            column=\"personId\"\n"
"            not-null=\"true\"/>\n"
"    </join>\n"
"</class>]]>"

#: index.docbook:220
msgid ""
"<![CDATA[\n"
"create table Person ( personId bigint not null primary key )\n"
"create table PersonAddress ( personId bigint not null, addressId bigint not "
"null primary key )\n"
"create table Address ( addressId bigint not null primary key )\n"
"        ]]>"
msgstr ""
"<![CDATA[\n"
"create table Person ( personId bigint not null primary key )\n"
"create table PersonAddress ( personId bigint not null, addressId bigint not "
"null primary key )\n"
"create table Address ( addressId bigint not null primary key )\n"
"        ]]>"

#: index.docbook:227
msgid ""
"A <emphasis>bidirectional one-to-one association on a join table</emphasis> "
"is extremely unusual, but possible."
msgstr ""
"Una <emphasis>asociaci&#x00f3;n bidireccional uno-a-uno en una tabla de "
"uni&#x00f3;n</emphasis> es inusual en extremo, pero posible."

#: index.docbook:232
msgid ""
"<![CDATA[<class name=\"Person\">\n"
"    <id name=\"id\" column=\"personId\">\n"
"        <generator class=\"native\"/>\n"
"    </id>\n"
"    <join table=\"PersonAddress\" \n"
"        optional=\"true\">\n"
"        <key column=\"personId\" \n"
"            unique=\"true\"/>\n"
"        <many-to-one name=\"address\"\n"
"            column=\"addressId\" \n"
"            not-null=\"true\"\n"
"            unique=\"true\"/>\n"
"    </join>\n"
"</class>\n"
"\n"
"<class name=\"Address\">\n"
"    <id name=\"id\" column=\"addressId\">\n"
"        <generator class=\"native\"/>\n"
"    </id>\n"
"    <join table=\"PersonAddress\" \n"
"        optional=\"true\"\n"
"        inverse=\"true\">\n"
"        <key column=\"addressId\" \n"
"            unique=\"true\"/>\n"
"        <many-to-one name=\"person\"\n"
"            column=\"personId\" \n"
"            not-null=\"true\"\n"
"            unique=\"true\"/>\n"
"    </join>\n"
"</class>]]>"
msgstr ""
"<![CDATA[<class name=\"Person\">\n"
"    <id name=\"id\" column=\"personId\">\n"
"        <generator class=\"native\"/>\n"
"    </id>\n"
"    <join table=\"PersonAddress\" \n"
"        optional=\"true\">\n"
"        <key column=\"personId\" \n"
"            unique=\"true\"/>\n"
"        <many-to-one name=\"address\"\n"
"            column=\"addressId\" \n"
"            not-null=\"true\"\n"
"            unique=\"true\"/>\n"
"    </join>\n"
"</class>\n"
"\n"
"<class name=\"Address\">\n"
"    <id name=\"id\" column=\"addressId\">\n"
"        <generator class=\"native\"/>\n"
"    </id>\n"
"    <join table=\"PersonAddress\" \n"
"        optional=\"true\"\n"
"        inverse=\"true\">\n"
"        <key column=\"addressId\" \n"
"            unique=\"true\"/>\n"
"        <many-to-one name=\"address\"\n"
"            column=\"personId\" \n"
"            not-null=\"true\"\n"
"            unique=\"true\"/>\n"
"    </join>\n"
"</class>]]>"

#: index.docbook:240
msgid ""
"Finally, we have a <emphasis>bidirectional many-to-many association</"
"emphasis>."
msgstr ""
"Finalmente, tenemos una <emphasis>asociaci&#x00f3;n bidireccional muchos-a-"
"muchos</emphasis>."

#: index.docbook:244
msgid ""
"<![CDATA[<class name=\"Person\">\n"
"    <id name=\"id\" column=\"personId\">\n"
"        <generator class=\"native\"/>\n"
"    </id>\n"
"    <set name=\"addresses\" table=\"PersonAddress\">\n"
"        <key column=\"personId\"/>\n"
"        <many-to-many column=\"addressId\"\n"
"            class=\"Address\"/>\n"
"    </set>\n"
"</class>\n"
"\n"
"<class name=\"Address\">\n"
"    <id name=\"id\" column=\"addressId\">\n"
"        <generator class=\"native\"/>\n"
"    </id>\n"
"    <set name=\"people\" inverse=\"true\" table=\"PersonAddress\">\n"
"        <key column=\"addressId\"/>\n"
"        <many-to-many column=\"personId\"\n"
"            class=\"Person\"/>\n"
"    </set>\n"
"</class>]]>"
msgstr ""
"<![CDATA[<class name=\"Person\">\n"
"    <id name=\"id\" column=\"personId\">\n"
"        <generator class=\"native\"/>\n"
"    </id>\n"
"    <set name=\"addresses\">\n"
"        <key column=\"personId\"/>\n"
"        <many-to-many column=\"addressId\"\n"
"            class=\"Address\"/>\n"
"    </set>\n"
"</class>\n"
"\n"
"<class name=\"Address\">\n"
"    <id name=\"id\" column=\"addressId\">\n"
"        <generator class=\"native\"/>\n"
"    </id>\n"
"    <set name=\"people\" inverse=\"true\">\n"
"        <key column=\"addressId\"/>\n"
"        <many-to-many column=\"personId\"\n"
"            class=\"Person\"/>\n"
"    </set>\n"
"</class>]]>"

#: index.docbook:253
msgid "More complex association mappings"
msgstr "UNTRANSLATED! More complex association mappings"

#: index.docbook:255
msgid ""
"More complex association joins are <emphasis>extremely</emphasis> rare. "
"Hibernate makes it possible to handle more complex situations using SQL "
"fragments embedded in the mapping document. For example, if a table with "
"historical account information data defines <literal>accountNumber</"
"literal>, <literal>effectiveEndDate</literal> and "
"<literal>effectiveStartDate</literal>columns, mapped as follows:"
msgstr ""
"More complex association joins are <emphasis>extremely</emphasis> rare. "
"Hibernate makes it possible to handle more complex situations using SQL "
"fragments embedded in the mapping document. For example, if a table with "
"historical account information data defines <literal>accountNumber</"
"literal>, <literal>effectiveEndDate</literal> and "
"<literal>effectiveStartDate</literal>columns, mapped as follows:"

#: index.docbook:264
msgid ""
"<![CDATA[<properties name=\"currentAccountKey\">\n"
"    <property name=\"accountNumber\" type=\"string\" not-null=\"true\"/>\n"
"    <property name=\"currentAccount\" type=\"boolean\">\n"
"        <formula>case when effectiveEndDate is null then 1 else 0 end</"
"formula>\n"
"    </property>\n"
"</properties>\n"
"<property name=\"effectiveEndDate\" type=\"date\"/>\n"
"<property name=\"effectiveStateDate\" type=\"date\" not-null=\"true\"/>]]>"
msgstr ""
"<![CDATA[<properties name=\"currentAccountKey\">\n"
"                            <property name=\"accountNumber\" type=\"string\" "
"not-null=\"true\"/>\n"
"                            <property name=\"currentAccount\" type=\"boolean"
"\">\n"
"                                    <formula>case when effectiveEndDate is "
"null then 1 else 0 end</formula>\n"
"                            </property>\n"
"                    </properties>\n"
"                    <property name=\"effectiveEndDate\" type=\"date\"/>\n"
"                    <property name=\"effectiveStateDate\" type=\"date\" not-"
"null=\"true\"/>]]>"

#: index.docbook:266
msgid ""
"Then we can map an association to the <emphasis>current</emphasis> instance "
"(the one with null <literal>effectiveEndDate</literal>) using:"
msgstr ""
"Then we can map an association to the <emphasis>current</emphasis> instance "
"(the one with null <literal>effectiveEndDate</literal>) using:"

#: index.docbook:271
msgid ""
"<![CDATA[<many-to-one name=\"currentAccountInfo\" \n"
"        property-ref=\"currentAccountKey\"\n"
"        class=\"AccountInfo\">\n"
"    <column name=\"accountNumber\"/>\n"
"    <formula>'1'</formula>\n"
"</many-to-one>]]>"
msgstr ""
"<![CDATA[<many-to-one name=\"currentAccountInfo\" \n"
"                                                  property-ref="
"\"currentAccountKey\"\n"
"                                                  class=\"AccountInfo\">\n"
"                            <column name=\"accountNumber\"/>\n"
"                            <formula>'1'</formula>\n"
"                    </many-to-one>]]>"

#: index.docbook:273
msgid ""
"In a more complex example, imagine that the association between "
"<literal>Employee</literal> and <literal>Organization</literal> is "
"maintained in an <literal>Employment</literal> table full of historical "
"employment data. Then an association to the employee's <emphasis>most "
"recent</emphasis> employer (the one with the most recent <literal>startDate</"
"literal>) might be mapped this way:"
msgstr ""
"In a more complex example, imagine that the association between "
"<literal>Employee</literal> and <literal>Organization</literal> is "
"maintained in an <literal>Employment</literal> table full of historical "
"employment data. Then an association to the employee's <emphasis>most "
"recent</emphasis> employer (the one with the most recent <literal>startDate</"
"literal>) might be mapped this way:"

#: index.docbook:281
msgid ""
"<![CDATA[<join>\n"
"    <key column=\"employeeId\"/>\n"
"    <subselect>\n"
"        select employeeId, orgId \n"
"        from Employments \n"
"        group by orgId \n"
"        having startDate = max(startDate)\n"
"    </subselect>\n"
"    <many-to-one name=\"mostRecentEmployer\" \n"
"            class=\"Organization\" \n"
"            column=\"orgId\"/>\n"
"</join>]]>"
msgstr ""
"<![CDATA[<join>\n"
"                            <key column=\"employeeId\"/>\n"
"                            <subselect>\n"
"                                    select employeeId, orgId \n"
"                                    from Employments \n"
"                                    group by orgId \n"
"                                    having startDate = max(startDate)\n"
"                            </subselect>\n"
"                            <many-to-one name=\"mostRecentEmployer\" \n"
"                                         class=\"Organization\" \n"
"                                         column=\"orgId\"/>\n"
"                    </join>]]>"

#: index.docbook:283
msgid ""
"You can get quite creative with this functionality, but it is usually more "
"practical to handle these kinds of cases using HQL or a criteria query."
msgstr ""
"You can get quite creative with this functionality, but it is usually more "
"practical to handle these kinds of cases using HQL or a criteria query."

msgid "ROLES_OF_TRANSLATORS"
msgstr "<!--TRANS:ROLES_OF_TRANSLATORS-->"

msgid "CREDIT_FOR_TRANSLATORS"
msgstr "<!--TRANS:CREDIT_FOR_TRANSLATORS-->"