Author: jdkim528 Date: 2010-01-12 07:01:32 -0500 (Tue, 12 Jan 2010) New Revision: 18513 Modified: core/trunk/documentation/manual/src/main/docbook/ko-KR/content/association_mapping.po Log: translated! Modified: core/trunk/documentation/manual/src/main/docbook/ko-KR/content/association_mapping.po =================================================================== --- core/trunk/documentation/manual/src/main/docbook/ko-KR/content/association_mapping.po 2010-01-12 11:36:49 UTC (rev 18512) +++ core/trunk/documentation/manual/src/main/docbook/ko-KR/content/association_mapping.po 2010-01-12 12:01:32 UTC (rev 18513) @@ -3,8 +3,8 @@ "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" "POT-Creation-Date: 2009-07-14 19:55+0000\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"PO-Revision-Date: 2010-01-12 20:59+0900\n" +"Last-Translator: Jongdae Kim <jdkim528(a)korea.com&gt;\n&quot; "Language-Team: LANGUAGE <LL(a)li.org&gt;\n&quot; "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -24,42 +24,21 @@ #. Tag: para #: association_mapping.xml:35 -#, fuzzy, no-c-format -msgid "" -"Association mappings are often the most difficult thing to implement " -"correctly. In this section we examine some canonical cases one by one, " -"starting with unidirectional mappings and then bidirectional cases. We will " -"use <literal>Person</literal> and <literal>Address</literal> in all the " -"examples." -msgstr "" -"연관 매핑들은 올바른 것을 얻기가 종종 가장 어려운 것이다. 이 절에서 우리는 단" -"방향 매핑들에서 시작하고, 그런 다음 양방향 경우들을 검토함으로써, 하나씩 표준" -"적인 경우들을 상세히 논의할 것이다. 우리는 모든 예제들에서 <literal>Person</" -"literal>과 <literal>Address</literal>를 사용할 것이다." +#, no-c-format +msgid "Association mappings are often the most difficult thing to implement correctly. In this section we examine some canonical cases one by one, starting with unidirectional mappings and then bidirectional cases. We will use <literal>Person</literal> and <literal>Address</literal> in all the examples." +msgstr "연관 매핑들은 종종 정확하게 구현하는 것이 가장 어려운 것이다. 이 절에서 우리는 단방향 매핑들에서 시작하여, 양방향 매핑의 경우까지 하나씩 몇몇 정규적인 경우들을 논의할 것이다. 우리는 모든 예제들에서 <literal>Person</literal>과 <literal>Address</literal>를 사용할 것이다." #. Tag: para #: association_mapping.xml:43 -#, fuzzy, no-c-format -msgid "" -"Associations will be classified by multiplicity and whether or not they map " -"to an intervening join table." -msgstr "" -"우리는 연관들을 중재하는 join 테이블로 매핑시킬 것인지 여부에 따라, 그리고 " -"multiplicity(다중성)에 따라 연관들을 분류할 것이다." +#, no-c-format +msgid "Associations will be classified by multiplicity and whether or not they map to an intervening join table." +msgstr "연관들은 다가성 그리고 중재하는 join 테이블로 매핑시킬 것인지 여부에 따라 분류될 것이다." #. Tag: para #: association_mapping.xml:48 -#, fuzzy, no-c-format -msgid "" -"Nullable foreign keys are not considered to be good practice in traditional " -"data modelling, so our examples do not use nullable foreign keys. This is " -"not a requirement of Hibernate, and the mappings will work if you drop the " -"nullability constraints." -msgstr "" -"null 허용 가능한 foreign 키들은 전통적인 데이터 모델링에서 좋은 실례로 간주되" -"지 않아서, 모든 우리의 예제들은 not null foreign 키들을 사용한다. 이것은 " -"Hibernate에서 필수가 아니고, 당신이 null 허용 가능 컨스트레인트들을 드롭시킬 " -"경우 매핑들은 모두 동작할 것이다." +#, no-c-format +msgid "Nullable foreign keys are not considered to be good practice in traditional data modelling, so our examples do not use nullable foreign keys. This is not a requirement of Hibernate, and the mappings will work if you drop the nullability constraints." +msgstr "널값이 허용되는 외래 키들은 전통적인 데이터 모델링에서 좋은 사례로 간주되지 않으므로, 우리의 예제들은 널 값이 허용되는 외래 키들을 사용하지 않는다. 이것은 하이버네이트의 사양이 아니며, 당신이 널 허용 컨스트레인트들을 드롭시킬 경우에 매핑들이 동작할 것이다." #. Tag: title #: association_mapping.xml:58 @@ -68,20 +47,17 @@ msgstr "단방향 연관들" #. Tag: title -#: association_mapping.xml:61 association_mapping.xml:132 -#, fuzzy, no-c-format +#: association_mapping.xml:61 +#: association_mapping.xml:132 +#, no-c-format msgid "Many-to-one" -msgstr "many to one" +msgstr "다-대-일" #. Tag: para #: association_mapping.xml:63 #, no-c-format -msgid "" -"A <emphasis>unidirectional many-to-one association</emphasis> is the most " -"common kind of unidirectional association." -msgstr "" -"<emphasis>단방향 many-to-one 연관</emphasis>은 가장 공통적인 종류의 단방향 연" -"관이다." +msgid "A <emphasis>unidirectional many-to-one association</emphasis> is the most common kind of unidirectional association." +msgstr "<emphasis>단방향 many-to-one 연관</emphasis>은 가장 공통적인 종류의 단방향 연관이다." #. Tag: programlisting #: association_mapping.xml:68 @@ -102,35 +78,49 @@ " </id>\n" "</class>]]>" msgstr "" +"<![CDATA[<class name=\"Person\">\n" +" <id name=\"id\" column=\"personId\">\n" +" <generator class=\"native\"/>\n" +" </id>\n" +" <many-to-one name=\"address\" \n" +" column=\"addressId\"\n" +" not-null=\"true\"/>\n" +"</class>\n" +"\n" +"<class name=\"Address\">\n" +" <id name=\"id\" column=\"addressId\">\n" +" <generator class=\"native\"/>\n" +" </id>\n" +"</class>]]>" #. Tag: programlisting -#: association_mapping.xml:69 association_mapping.xml:185 +#: association_mapping.xml:69 +#: association_mapping.xml:185 #, no-c-format msgid "" "<![CDATA[\n" -"create table Person ( personId bigint not null primary key, addressId bigint " -"not null )\n" +"create table Person ( personId bigint not null primary key, addressId bigint not null )\n" "create table Address ( addressId bigint not null primary key )\n" " ]]>" msgstr "" +"<![CDATA[\n" +"create table Person ( personId bigint not null primary key, addressId bigint not null )\n" +"create table Address ( addressId bigint not null primary key )\n" +" ]]>" #. Tag: title -#: association_mapping.xml:74 association_mapping.xml:145 +#: association_mapping.xml:74 +#: association_mapping.xml:145 #: association_mapping.xml:210 -#, fuzzy, no-c-format +#, no-c-format msgid "One-to-one" -msgstr "one to one" +msgstr "일-대-일" #. Tag: para #: association_mapping.xml:76 #, no-c-format -msgid "" -"A <emphasis>unidirectional one-to-one association on a foreign key</" -"emphasis> is almost identical. The only difference is the column unique " -"constraint." -msgstr "" -"<emphasis>foreign 키에 대한 단방향 one-to-one 연관은 대개 아주 동일하다.</" -"emphasis> 유일한 차이점은 컬럼 유일(unique) 컨스트레인트이다." +msgid "A <emphasis>unidirectional one-to-one association on a foreign key</emphasis> is almost identical. The only difference is the column unique constraint." +msgstr "<emphasis>foreign 키에 대한 단방향 one-to-one 연관은 대개 아주 동일하다.</emphasis> 유일한 차이점은 컬럼 유일(unique) 컨스트레인트이다." #. Tag: programlisting #: association_mapping.xml:81 @@ -152,29 +142,42 @@ " </id>\n" "</class>]]>" msgstr "" +"<![CDATA[<class name=\"Person\">\n" +" <id name=\"id\" column=\"personId\">\n" +" <generator class=\"native\"/>\n" +" </id>\n" +" <many-to-one name=\"address\" \n" +" column=\"addressId\" \n" +" unique=\"true\"\n" +" not-null=\"true\"/>\n" +"</class>\n" +"\n" +"<class name=\"Address\">\n" +" <id name=\"id\" column=\"addressId\">\n" +" <generator class=\"native\"/>\n" +" </id>\n" +"</class>]]>" #. Tag: programlisting -#: association_mapping.xml:82 association_mapping.xml:218 +#: association_mapping.xml:82 +#: association_mapping.xml:218 #, no-c-format msgid "" "<![CDATA[\n" -"create table Person ( personId bigint not null primary key, addressId bigint " -"not null unique )\n" +"create table Person ( personId bigint not null primary key, addressId bigint not null unique )\n" "create table Address ( addressId bigint not null primary key )\n" " ]]>" msgstr "" +"<![CDATA[\n" +"create table Person ( personId bigint not null primary key, addressId bigint not null unique )\n" +"create table Address ( addressId bigint not null primary key )\n" +" ]]>" #. Tag: para #: association_mapping.xml:84 -#, fuzzy, no-c-format -msgid "" -"A <emphasis>unidirectional one-to-one association on a primary key</" -"emphasis> usually uses a special id generator In this example, however, we " -"have reversed the direction of the association:" -msgstr "" -"<emphasis>하나의 프라이머리 키에 대한 단방향 one-to-one 연관</emphasis>은 대" -"개 특별한 id 생성기를 사용한다. (이 예제에서 연관의 방향이 역전되었음을 주목" -"하라.)" +#, no-c-format +msgid "A <emphasis>unidirectional one-to-one association on a primary key</emphasis> usually uses a special id generator In this example, however, we have reversed the direction of the association:" +msgstr "<emphasis>프라이머리 키에 대한 단방향 일-대-일 연관</emphasis>은 대개 특별한 id 생성자를 사용한다. 하지만 이 예제에서 우리는 연관의 방향을 역전시켰다:" #. Tag: programlisting #: association_mapping.xml:90 @@ -195,9 +198,24 @@ " <one-to-one name=\"person\" constrained=\"true\"/>\n" "</class>]]>" msgstr "" +"<![CDATA[<class name=\"Person\">\n" +" <id name=\"id\" column=\"personId\">\n" +" <generator class=\"native\"/>\n" +" </id>\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\" constrained=\"true\"/>\n" +"</class>]]>" #. Tag: programlisting -#: association_mapping.xml:91 association_mapping.xml:226 +#: association_mapping.xml:91 +#: association_mapping.xml:226 #, no-c-format msgid "" "<![CDATA[\n" @@ -205,22 +223,23 @@ "create table Address ( personId bigint not null primary key )\n" " ]]>" msgstr "" +"<![CDATA[\n" +"create table Person ( personId bigint not null primary key )\n" +"create table Address ( personId bigint not null primary key )\n" +" ]]>" #. Tag: title -#: association_mapping.xml:96 association_mapping.xml:118 -#, fuzzy, no-c-format +#: association_mapping.xml:96 +#: association_mapping.xml:118 +#, no-c-format msgid "One-to-many" -msgstr "one to many" +msgstr "일-대-다 " #. Tag: para #: association_mapping.xml:98 -#, fuzzy, no-c-format -msgid "" -"A <emphasis>unidirectional one-to-many association on a foreign key</" -"emphasis> is an unusual case, and is not recommended." -msgstr "" -"<emphasis>하나의 foreign 키에 대한 단방향 one-to-many 연관</emphasis>은 매우 " -"색다른 경우이고, 실제로 권장되지 않는다." +#, no-c-format +msgid "A <emphasis>unidirectional one-to-many association on a foreign key</emphasis> is an unusual case, and is not recommended." +msgstr "<emphasis>외래 키에 대한 단방향 일-대-다 연관</emphasis>은 색다른 경우이며, 권장되지 않는다." #. Tag: programlisting #: association_mapping.xml:103 @@ -243,6 +262,22 @@ " </id>\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" +" not-null=\"true\"/>\n" +" <one-to-many class=\"Address\"/>\n" +" </set>\n" +"</class>\n" +"\n" +"<class name=\"Address\">\n" +" <id name=\"id\" column=\"addressId\">\n" +" <generator class=\"native\"/>\n" +" </id>\n" +"</class>]]>" #. Tag: programlisting #: association_mapping.xml:104 @@ -250,18 +285,19 @@ msgid "" "<![CDATA[\n" "create table Person ( personId bigint not null primary key )\n" -"create table Address ( addressId bigint not null primary key, personId " -"bigint not null )\n" +"create table Address ( addressId bigint not null primary key, personId bigint not null )\n" " ]]>" msgstr "" +"<![CDATA[\n" +"create table Person ( personId bigint not null primary key )\n" +"create table Address ( addressId bigint not null primary key, personId bigint not null )\n" +" ]]>" #. Tag: para #: association_mapping.xml:106 -#, fuzzy, no-c-format +#, no-c-format msgid "You should instead use a join table for this kind of association." -msgstr "" -"우리는 이런 종류의 연관에 대해 하나의 join 테이블을 사용하는 것이 더 좋다고 " -"생각한다." +msgstr "대신에 당신은 이런 종류의 연관에 대해 하나의 join 테이블을 사용해야 한다." #. Tag: title #: association_mapping.xml:115 @@ -271,15 +307,9 @@ #. Tag: para #: association_mapping.xml:120 -#, fuzzy, no-c-format -msgid "" -"A <emphasis>unidirectional one-to-many association on a join table</" -"emphasis> is the preferred option. Specifying <literal>unique=\"true\"</" -"literal>, changes the multiplicity from many-to-many to one-to-many." -msgstr "" -"<emphasis>하나의 join 테이블에 대한 단방향 one-to-many 연관</emphasis>이 보" -"다 더 선호된다. <literal>unique=\"true\"</literal>를 지정함으로써 우리는 " -"many-to-many에서 one-to-many로 아중성(multiplicity)를 변경시켰음을 주목하라." +#, no-c-format +msgid "A <emphasis>unidirectional one-to-many association on a join table</emphasis> is the preferred option. Specifying <literal>unique=\"true\"</literal>, changes the multiplicity from many-to-many to one-to-many." +msgstr "<emphasis>join 테이블에 대한 단방향 일-대-다 연관</emphasis>은 선호되는 옵션이다. <literal>unique=\"true\"</literal>를 지정하여, 다-대-다에서 일-대-다로 다중값을 변경시켜라." #. Tag: programlisting #: association_mapping.xml:126 @@ -303,6 +333,23 @@ " </id>\n" "</class>]]>" msgstr "" +"<![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" +" 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" +"</class>]]>" #. Tag: programlisting #: association_mapping.xml:127 @@ -310,21 +357,21 @@ msgid "" "<![CDATA[\n" "create table Person ( personId bigint not null primary key )\n" -"create table PersonAddress ( personId not null, addressId bigint not null " -"primary key )\n" +"create table PersonAddress ( personId 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 not null, addressId bigint not null primary key )\n" +"create table Address ( addressId bigint not null primary key )\n" +" ]]>" #. Tag: para #: association_mapping.xml:134 -#, fuzzy, no-c-format -msgid "" -"A <emphasis>unidirectional many-to-one association on a join table</" -"emphasis> is common when the association is optional. For example:" -msgstr "" -"<emphasis>하나의 join 테이블에 대한 단방향 many-to-one 연관</emphasis>은 그 " -"연관이 선택적일 때 매우 공통적이다." +#, no-c-format +msgid "A <emphasis>unidirectional many-to-one association on a join table</emphasis> is common when the association is optional. For example:" +msgstr "<emphasis>join 테이블에 대한 단방향 다-대-일 연관</emphasis>은 그 연관이 선택적일 때 공통적이다. 예를 들면:" #. Tag: programlisting #: association_mapping.xml:139 @@ -349,6 +396,24 @@ " </id>\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\" unique=\"true\"/>\n" +" <many-to-one name=\"address\"\n" +" column=\"addressId\" \n" +" not-null=\"true\"/>\n" +" </join>\n" +"</class>\n" +"\n" +"<class name=\"Address\">\n" +" <id name=\"id\" column=\"addressId\">\n" +" <generator class=\"native\"/>\n" +" </id>\n" +"</class>]]>" #. Tag: programlisting #: association_mapping.xml:140 @@ -356,21 +421,21 @@ msgid "" "<![CDATA[\n" "create table Person ( personId bigint not null primary key )\n" -"create table PersonAddress ( personId bigint not null primary key, addressId " -"bigint not null )\n" +"create table PersonAddress ( personId bigint not null primary key, addressId bigint not null )\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 primary key, addressId bigint not null )\n" +"create table Address ( addressId bigint not null primary key )\n" +" ]]>" #. Tag: para #: association_mapping.xml:147 -#, fuzzy, no-c-format -msgid "" -"A <emphasis>unidirectional one-to-one association on a join table</emphasis> " -"is possible, but extremely unusual." -msgstr "" -"<emphasis>하나의 join 테이블에 대한 단방향 one-to-one 연관</emphasis>은 극히 " -"통상적이지 않지만 가능하다." +#, no-c-format +msgid "A <emphasis>unidirectional one-to-one association on a join table</emphasis> is possible, but extremely unusual." +msgstr "<emphasis>join 테이블에 대한 단방향 일-대-일 연관</emphasis>은 가능하지만, 극히 통상적이지 않다." #. Tag: programlisting #: association_mapping.xml:152 @@ -397,33 +462,56 @@ " </id>\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" +"</class>]]>" #. Tag: programlisting -#: association_mapping.xml:153 association_mapping.xml:258 +#: association_mapping.xml:153 +#: association_mapping.xml:258 #, no-c-format msgid "" "<![CDATA[\n" "create table Person ( personId bigint not null primary key )\n" -"create table PersonAddress ( personId bigint not null primary key, addressId " -"bigint not null unique )\n" +"create table PersonAddress ( personId bigint not null primary key, addressId bigint not null unique )\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 primary key, addressId bigint not null unique )\n" +"create table Address ( addressId bigint not null primary key )\n" +" ]]>" #. Tag: title -#: association_mapping.xml:158 association_mapping.xml:263 -#, fuzzy, no-c-format +#: association_mapping.xml:158 +#: association_mapping.xml:263 +#, no-c-format msgid "Many-to-many" -msgstr "many to many" +msgstr "다-대-다" #. Tag: para #: association_mapping.xml:160 -#, fuzzy, no-c-format -msgid "" -"Finally, here is an example of a <emphasis>unidirectional many-to-many " -"association</emphasis>." -msgstr "" -"마지막으로, 우리는 <emphasis>단방향 many-to-many 연관</emphasis>을 갖는다." +#, no-c-format +msgid "Finally, here is an example of a <emphasis>unidirectional many-to-many association</emphasis>." +msgstr "마지막으로, 다음은 <emphasis>단방향 다-대-다 연관</emphasis>에 대한 예제이다." #. Tag: programlisting #: association_mapping.xml:164 @@ -446,18 +534,39 @@ " </id>\n" "</class>]]>" msgstr "" +"<![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" +"</class>]]>" #. Tag: programlisting -#: association_mapping.xml:165 association_mapping.xml:271 +#: association_mapping.xml:165 +#: association_mapping.xml:271 #, no-c-format 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 (personId, addressId) )\n" +"create table PersonAddress ( personId bigint not null, addressId bigint not null, primary key (personId, addressId) )\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 (personId, addressId) )\n" +"create table Address ( addressId bigint not null primary key )\n" +" ]]>" #. Tag: title #: association_mapping.xml:172 @@ -466,21 +575,17 @@ msgstr "양방향 연관들" #. Tag: title -#: association_mapping.xml:175 association_mapping.xml:236 -#, fuzzy, no-c-format +#: association_mapping.xml:175 +#: association_mapping.xml:236 +#, no-c-format msgid "one-to-many / many-to-one" -msgstr "one to many / many to one" +msgstr "일-대-다 / 다-대-일" #. Tag: para #: association_mapping.xml:177 -#, fuzzy, no-c-format -msgid "" -"A <emphasis>bidirectional many-to-one association</emphasis> is the most " -"common kind of association. The following example illustrates the standard " -"parent/child relationship." -msgstr "" -"<emphasis>양방향 many-to-one 연관</emphasis>은 가장 공통된 종류의 연관이다." -"(이것은 표준 부모/자식 관계이다. )" +#, no-c-format +msgid "A <emphasis>bidirectional many-to-one association</emphasis> is the most common kind of association. The following example illustrates the standard parent/child relationship." +msgstr "<emphasis>양방향 다-대-일 연관</emphasis>은 가장 공통된 종류의 연관이다. 다음 예제는 표준 부모/자식 관계를 설명한다." #. Tag: programlisting #: association_mapping.xml:183 @@ -505,24 +610,30 @@ " </set>\n" "</class>]]>" msgstr "" +"<![CDATA[<class name=\"Person\">\n" +" <id name=\"id\" column=\"personId\">\n" +" <generator class=\"native\"/>\n" +" </id>\n" +" <many-to-one name=\"address\" \n" +" column=\"addressId\"\n" +" not-null=\"true\"/>\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" +" <one-to-many class=\"Person\"/>\n" +" </set>\n" +"</class>]]>" #. Tag: para #: association_mapping.xml:187 -#, fuzzy, no-c-format -msgid "" -"If you use a <literal>List</literal>, or other indexed collection, set the " -"<literal>key</literal> column of the foreign key to <literal>not null</" -"literal>. Hibernate will manage the association from the collections side to " -"maintain the index of each element, making the other side virtually inverse " -"by setting <literal>update=\"false\"</literal> and <literal>insert=\"false" -"\"</literal>:" -msgstr "" -"만일 당신이 <literal>List</literal>(또는 다른 인덱싱 된 콜렉션)을 사용할 경" -"우 당신은 foreign key의 <literal>key</literal> 컬럼을 <literal>not null</" -"literal>로 설정하고, Hibernate로 하여금 각각의 요소의 인덱스를 유지관리하기 " -"위해 (<literal>update=\"false\"</literal>와 <literal>insert=\"false\"</" -"literal>를 설정함으로써 다른 측을 가상적으로 inverse로 만들어) 그 콜렉션들 측" -"으로부터 연관을 관리하도록 할 필요가 있다:" +#, no-c-format +msgid "If you use a <literal>List</literal>, or other indexed collection, set the <literal>key</literal> column of the foreign key to <literal>not null</literal>. Hibernate will manage the association from the collections side to maintain the index of each element, making the other side virtually inverse by setting <literal>update=\"false\"</literal> and <literal>insert=\"false\"</literal>:" +msgstr "만일 당신이 <literal>List</literal>, 또는 다른 인덱싱 된 콜렉션을 사용할 경우, 외래 키의 <literal>key</literal> 컬럼을 <literal>not null</literal>로 설정하라. 하이버네이트는 각각의 요소의 인덱스를 관리하기 위해 <literal>update=\"false\"</literal>와 <literal>insert=\"false\"</literal>를 설정하여 다른 측을 가상적으로 역행시킴으로서 콜렉션들 측에서 그 연관을 관리할 것이다:" #. Tag: programlisting #: association_mapping.xml:195 @@ -548,32 +659,37 @@ " </list>\n" "</class>]]>" msgstr "" +"<![CDATA[<class name=\"Person\">\n" +" <id name=\"id\"/>\n" +" ...\n" +" <many-to-one name=\"address\"\n" +" column=\"addressId\"\n" +" not-null=\"true\"\n" +" insert=\"false\"\n" +" update=\"false\"/>\n" +"</class>\n" +"\n" +"<class name=\"Address\">\n" +" <id name=\"id\"/>\n" +" ...\n" +" <list name=\"people\">\n" +" <key column=\"addressId\" not-null=\"true\"/>\n" +" <list-index column=\"peopleIdx\"/>\n" +" <one-to-many class=\"Person\"/>\n" +" </list>\n" +"</class>]]>" #. Tag: para #: association_mapping.xml:197 -#, fuzzy, no-c-format -msgid "" -"If the underlying foreign key column is <literal>NOT NULL</literal>, it is " -"important that you define <literal>not-null=\"true\"</literal> on the " -"<literal>&lt;key&gt;</literal> element of the collection mapping. Do not " -"only declare <literal>not-null=\"true\"</literal> on a possible nested " -"<literal>&lt;column&gt;</literal> element, but on the <literal>&lt;key&gt;</" -"literal> element." -msgstr "" -"만일 기본 외래 키 컬럼이 <literal>NOT NULL</literal>일 경우 콜렉션 매핑의 " -"<literal>&lt;key&gt;</literal> 요소 상에 <literal>not-null=\"true\"</literal>" -"를 정의하는 것이 중요하다. 내포된 <literal>&lt;column&gt;</literal> 요소 상" -"에 <literal>not-null=\"true\"</literal>를 선언하지 말고, <literal>&lt;key&gt;" -"</literal> 요소 상에 선언하라." +#, no-c-format +msgid "If the underlying foreign key column is <literal>NOT NULL</literal>, it is important that you define <literal>not-null=\"true\"</literal> on the <literal>&lt;key&gt;</literal> element of the collection mapping. Do not only declare <literal>not-null=\"true\"</literal> on a possible nested <literal>&lt;column&gt;</literal> element, but on the <literal>&lt;key&gt;</literal> element." +msgstr "만일 기본 외래 키 컬럼이 <literal>NOT NULL</literal>일 경우, 당신이 콜렉션 매핑의 <literal>&lt;key&gt;</literal>에 <literal>not-null=\"true\"</literal>를 정의하는 것이 중요하다. <literal>not-null=\"true\"</literal>를 가능한 내포된 <literal>&lt;column&gt;</literal> 요소 뿐만 아니라, <literal>&lt;key&gt;</literal> 요소 상에도 선언하라." #. Tag: para #: association_mapping.xml:212 -#, fuzzy, no-c-format -msgid "" -"A <emphasis>bidirectional one-to-one association on a foreign key</emphasis> " -"is common:" -msgstr "" -"<emphasis>foreign에 대한 양방향 one-to-one 연관</emphasis>은 꽤 공통적이다." +#, no-c-format +msgid "A <emphasis>bidirectional one-to-one association on a foreign key</emphasis> is common:" +msgstr "<emphasis>외래 키에 대한 양방향일-대-일 연관</emphasis>은 공통적이다:" #. Tag: programlisting #: association_mapping.xml:217 @@ -597,16 +713,29 @@ " property-ref=\"address\"/>\n" "</class>]]>" msgstr "" +"<![CDATA[<class name=\"Person\">\n" +" <id name=\"id\" column=\"personId\">\n" +" <generator class=\"native\"/>\n" +" </id>\n" +" <many-to-one name=\"address\" \n" +" column=\"addressId\" \n" +" unique=\"true\"\n" +" not-null=\"true\"/>\n" +"</class>\n" +"\n" +"<class name=\"Address\">\n" +" <id name=\"id\" column=\"addressId\">\n" +" <generator class=\"native\"/>\n" +" </id>\n" +" <one-to-one name=\"person\" \n" +" property-ref=\"address\"/>\n" +"</class>]]>" #. Tag: para #: association_mapping.xml:220 -#, fuzzy, no-c-format -msgid "" -"A <emphasis>bidirectional one-to-one association on a primary key</emphasis> " -"uses the special id generator:" -msgstr "" -"<emphasis>하나의 프라이머리 키에 대한 양방향 one-to-one 연관</emphasis>은 특" -"별한 id 생성기를 사용한다." +#, no-c-format +msgid "A <emphasis>bidirectional one-to-one association on a primary key</emphasis> uses the special id generator:" +msgstr "<emphasis>프라이머리 키에 대한 양방향 일-대-일 연관</emphasis>은 특별한 id 생성자를 사용한다:" #. Tag: programlisting #: association_mapping.xml:225 @@ -629,6 +758,22 @@ " 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>]]>" #. Tag: title #: association_mapping.xml:233 @@ -638,16 +783,9 @@ #. Tag: para #: association_mapping.xml:238 -#, fuzzy, no-c-format -msgid "" -"The following is an example of a <emphasis>bidirectional one-to-many " -"association on a join table</emphasis>. The <literal>inverse=\"true\"</" -"literal> can go on either end of the association, on the collection, or on " -"the join." -msgstr "" -"<emphasis>하나의 join 테이블에 대한 양방향 one-to-many 연관</emphasis>. " -"<literal>inverse=\"true\"</literal>는 연관의 어느 쪽 끝이든 콜렉션 측으로 또" -"는 join 측으로 갈 수 있다." +#, no-c-format +msgid "The following is an example of a <emphasis>bidirectional one-to-many association on a join table</emphasis>. The <literal>inverse=\"true\"</literal> can go on either end of the association, on the collection, or on the join." +msgstr "다음은 <emphasis>join 테이블에 대한 양방향 일-대-다 연관</emphasis>에 대한 예제이다. <literal>inverse=\"true\"</literal>는 연관의 어느 측이든지, 콜렉션 측에도, 또는 join 측에도 쓸 수 있다." #. Tag: programlisting #: association_mapping.xml:244 @@ -680,6 +818,32 @@ " </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>]]>" #. Tag: programlisting #: association_mapping.xml:245 @@ -687,11 +851,15 @@ 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 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" +" ]]>" #. Tag: title #: association_mapping.xml:250 @@ -701,13 +869,9 @@ #. Tag: para #: association_mapping.xml:252 -#, fuzzy, no-c-format -msgid "" -"A <emphasis>bidirectional one-to-one association on a join table</emphasis> " -"is possible, but extremely unusual." -msgstr "" -"<emphasis>하나의 join 테이블에 대한 양방향 one-to-one 연관</emphasis>은 극히 " -"통상적이지 않지만, 가능하다." +#, no-c-format +msgid "A <emphasis>bidirectional one-to-one association on a join table</emphasis> is possible, but extremely unusual." +msgstr "<emphasis>join 테이블에 대한 양방향 일-대-일 연관</emphasis>이 가능하지만, 극히 통상적이지 않다." #. Tag: programlisting #: association_mapping.xml:257 @@ -744,16 +908,42 @@ " </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=\"person\"\n" +" column=\"personId\" \n" +" not-null=\"true\"\n" +" unique=\"true\"/>\n" +" </join>\n" +"</class>]]>" #. Tag: para #: association_mapping.xml:265 -#, fuzzy, no-c-format -msgid "" -"Here is an example of a <emphasis>bidirectional many-to-many association</" -"emphasis>." -msgstr "" -"마지막으로, 우리는 하나의 <emphasis>양방향 many-to-many 연관</emphasis>을 갖" -"는다." +#, no-c-format +msgid "Here is an example of a <emphasis>bidirectional many-to-many association</emphasis>." +msgstr "이것은 <emphasis>양방향 다-대-다 연관</emphasis>에 대한 예제이다." #. Tag: programlisting #: association_mapping.xml:269 @@ -781,6 +971,27 @@ " </set>\n" "</class>]]>" msgstr "" +"<![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>]]>" #. Tag: title #: association_mapping.xml:278 @@ -790,21 +1001,9 @@ #. Tag: para #: association_mapping.xml:280 -#, fuzzy, no-c-format -msgid "" -"More complex association joins are <emphasis>extremely</emphasis> rare. " -"Hibernate handles more complex situations by 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, it would be mapped as follows:" -msgstr "" -"보다 복잡한 연관 조인들은 <emphasis>극기</emphasis> 드물다. Hibernate는 매핑 " -"문서들 내에 삽입된 SQL 조각들을 사용하여 보다 복잡한 상황을 처리하는 것을 가" -"능하도록 해준다. 예를 들어, 만일 계좌 내역 정보 데이터를 가진 하나이 테이블" -"이 <literal>accountNumber</literal>, <literal>effectiveEndDate</literal> 그리" -"고 <literal>effectiveStartDate</literal> 컬럼들을 정의할 경우, 다음과 같이 매" -"핑된다:" +#, no-c-format +msgid "More complex association joins are <emphasis>extremely</emphasis> rare. Hibernate handles more complex situations by 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, it would be mapped as follows:" +msgstr "보다 복잡한 연관 join들은 <emphasis>극히</emphasis> 드물다. 하이버네이트는 매핑 문서들 내에 삽입된 SQL 조각들을 사용하여 보다 복잡한 상황들을 처리한다. 예를 들어, 만일 계좌 내역 정보 데이터를 가진 테이블이 <literal>accountNumber</literal>, <literal>effectiveEndDate</literal> 그리고 <literal>effectiveStartDate</literal> 컬럼들을 정의하고 있다면, 그것은 다음과 같이 매핑될 것이다:" #. Tag: programlisting #: association_mapping.xml:289 @@ -813,24 +1012,26 @@ "<![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" +" <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\"/>]]>" #. Tag: para #: association_mapping.xml:291 -#, fuzzy, no-c-format -msgid "" -"You can then map an association to the <emphasis>current</emphasis> " -"instance, the one with null <literal>effectiveEndDate</literal>, by using:" -msgstr "" -"그때 우리는 다음을 사용하여 하나의 연관을 <emphasis>현재</emphasis> 인스턴스 " -"(null <literal>effectiveEndDate</literal>을 가진 인스턴스)로 매핑시킬 수 있" -"다:" +#, no-c-format +msgid "You can then map an association to the <emphasis>current</emphasis> instance, the one with null <literal>effectiveEndDate</literal>, by using:" +msgstr "그때 당신은 다음을 사용하여 하나의 연관을 널이 허용되는 <literal>effectiveEndDate</literal>를 가진, <emphasis>current</emphasis> 인스턴스에 매핑시킬 수 있다:" #. Tag: programlisting #: association_mapping.xml:296 @@ -843,23 +1044,18 @@ " <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>]]>" #. Tag: para #: association_mapping.xml:298 -#, fuzzy, no-c-format -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. An association to the employee's <emphasis>most recent</" -"emphasis> employer, the one with the most recent <literal>startDate</" -"literal>, could be mapped in the following way:" -msgstr "" -"보다 복잡한 예제에서, <literal>Employee</literal>와 <literal>Organization</" -"literal> 사이의 연관이 전체 고용 내역 데이터를 가진 <literal>Employment</" -"literal> 테이블 내에 유지된다고 가정하자. 그때 종업원의 <emphasis>가장 최근의" -"</emphasis> 고용주에 대한 하나의 연관(가장 최근의 <literal>startDate</" -"literal>를 갖고 있는 것)이 다음 방법으로 매핑될 수 있다:" +#, no-c-format +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. An association to the employee's <emphasis>most recent</emphasis> employer, the one with the most recent <literal>startDate</literal>, could be mapped in the following way:" +msgstr "보다 복잡한 예제에서, <literal>Employee</literal>와 <literal>Organization</literal> 사이의 연관이 전체 고용 내역 데이터를 가진 <literal>Employment</literal> 테이블 내에 유지된다고 가정하자. 종업원의 <emphasis>가장 최근의</emphasis> 고용주에 대한 연관, 가장 최근의 <literal>startDate</literal>를 가진 연관이 다음 방법으로 매핑될 수 있다:" #. Tag: programlisting #: association_mapping.xml:306 @@ -878,13 +1074,22 @@ " 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>]]>" #. Tag: para #: association_mapping.xml:308 -#, fuzzy, no-c-format -msgid "" -"This functionality allows a degree of creativity and flexibility, but it is " -"more practical to handle these kinds of cases using HQL or a criteria query." -msgstr "" -"당신은 이 기능으로 아주 생산성을 얻을 수 있지만, 그것은 대개 HQL 또는 " -"criteria 질의를 사용하여 이들 종류의 경우들을 처리하는 것이 보다 실용적이다." +#, no-c-format +msgid "This functionality allows a degree of creativity and flexibility, but it is more practical to handle these kinds of cases using HQL or a criteria query." +msgstr "이 기능은 생산성과 유연성 제고를 허용하지만, HQL이나 criteria 질의를 사용하여 이들 종류의 경우들을 처리하는 것이 보다 실용적이다." +