Hibernate
/
hibernate-orm
mirror of https://github.com/hibernate/hibernate-orm
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

undo fixes for HHH-3080,HHH-3190,HHH-2976,HHH-3397 

git-svn-id: https://svn.jboss.org/repos/hibernate/core/trunk@15064 1b8cb986-b30d-0410-93ca-fae66ebed9b2
This commit is contained in:
Steve Ebersole 2008-08-14 14:03:09 +00:00
parent 841cd58cdf
commit 5705431a07
43 changed files with 75 additions and 76 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
documentation/manual/old/fr-FR/src/main/docbook/content/association_mapping.xml
View File

@ -585,7 +585,7 @@ create table Address ( addressId bigint not null primary key )
</property> </property>
</properties> </properties>
<property name="effectiveEndDate" type="date"/> <property name="effectiveEndDate" type="date"/>
<property name="effectiveStartDate" type="date" not-null="true"/>]]></programlisting> <property name="effectiveStateDate" type="date" not-null="true"/>]]></programlisting>
<para> <para>
alors nous pouvons mapper une association à l'instance <emphasis>courante</emphasis> alors nous pouvons mapper une association à l'instance <emphasis>courante</emphasis>

2
documentation/manual/old/ja-JP/src/main/docbook/content/association_mapping.xml
View File

@ -574,7 +574,7 @@ create table Address ( addressId bigint not null primary key )
</property> </property>
</properties> </properties>
<property name="effectiveEndDate" type="date"/> <property name="effectiveEndDate" type="date"/>
<property name="effectiveStartDate" type="date" not-null="true"/>]]></programlisting> <property name="effectiveStateDate" type="date" not-null="true"/>]]></programlisting>
<para> <para>
そして、関連を <emphasis>現時点の</emphasis> インスタンス そして、関連を <emphasis>現時点の</emphasis> インスタンス

2
documentation/manual/old/ko-KR/src/main/docbook/content/association_mapping.xml
View File

@ -560,7 +560,7 @@ create table Address ( addressId bigint not null primary key )
</property> </property>
</properties> </properties>
<property name="effectiveEndDate" type="date"/> <property name="effectiveEndDate" type="date"/>
<property name="effectiveStartDate" type="date" not-null="true"/>]]></programlisting> <property name="effectiveStateDate" type="date" not-null="true"/>]]></programlisting>
<para> <para>
그때 우리는 다음을 사용하여 하나의 연관을 <emphasis>현재</emphasis> 인스턴스 그때 우리는 다음을 사용하여 하나의 연관을 <emphasis>현재</emphasis> 인스턴스

2
documentation/manual/old/pt-BR/src/main/docbook/content/association_mapping.xml
View File

@ -588,7 +588,7 @@ Joins de associações mais complexas são extremamente raros. O Hibernate torna
</property> </property>
</properties> </properties>
<property name="effectiveEndDate" type="date"/> <property name="effectiveEndDate" type="date"/>
<property name="effectiveStartDate" type="date" not-null="true"/>]]></programlisting> <property name="effectiveStateDate" type="date" not-null="true"/>]]></programlisting>
<para> <para>
Then we can map an association to the <emphasis>current</emphasis> instance Then we can map an association to the <emphasis>current</emphasis> instance

2
documentation/manual/old/pt-BR/src/main/docbook/content/tutorial1.xml
View File

@ -1444,7 +1444,7 @@ out.close();]]></programlisting>
That's it, the servlet is complete. A request to the servlet will be processed That's it, the servlet is complete. A request to the servlet will be processed
in a single <literal>Session</literal> and <literal>Transaction</literal>. As in a single <literal>Session</literal> and <literal>Transaction</literal>. As
earlier in the standalone application, Hibernate can automatically bind these earlier in the standalone application, Hibernate can automatically bind these
objects to the current thread of execution. This gives you the freedom to layer ojects to the current thread of execution. This gives you the freedom to layer
your code and access the <literal>SessionFactory</literal> in any way you like. your code and access the <literal>SessionFactory</literal> in any way you like.
Usually you'd use a more sophisticated design and move the data access code Usually you'd use a more sophisticated design and move the data access code
into data access objects (the DAO pattern). See the Hibernate Wiki for more into data access objects (the DAO pattern). See the Hibernate Wiki for more

2
documentation/manual/old/zh-CN/src/main/docbook/content/association_mapping.xml
View File

@ -541,7 +541,7 @@ create table Address ( addressId bigint not null primary key )
</property> </property>
</properties> </properties>
<property name="effectiveEndDate" type="date"/> <property name="effectiveEndDate" type="date"/>
<property name="effectiveStartDate" type="date" not-null="true"/>]]></programlisting> <property name="effectiveStateDate" type="date" not-null="true"/>]]></programlisting>
<para> <para>
那么我们可以对<emphasis>目前(current)</emphasis>实例(其<literal>effectiveEndDate</literal>为null)使用这样的关联映射: 那么我们可以对<emphasis>目前(current)</emphasis>实例(其<literal>effectiveEndDate</literal>为null)使用这样的关联映射:

2
documentation/manual/src/main/docbook/en-US/content/association_mapping.xml
View File

@ -603,7 +603,7 @@ create table Address ( addressId bigint not null primary key )
</property> </property>
</properties> </properties>
<property name="effectiveEndDate" type="date"/> <property name="effectiveEndDate" type="date"/>
<property name="effectiveStartDate" type="date" not-null="true"/>]]></programlisting> <property name="effectiveStateDate" type="date" not-null="true"/>]]></programlisting>
<para> <para>
Then we can map an association to the <emphasis>current</emphasis> instance Then we can map an association to the <emphasis>current</emphasis> instance

2
documentation/manual/src/main/docbook/en-US/content/component_mapping.xml
View File

@ -126,7 +126,7 @@
<para> <para>
Like all value types, components do not support shared references. In other words, two Like all value types, components do not support shared references. In other words, two
persons could have the same name, but the two person objects would contain two independent persons could have the same name, but the two person objects would contain two independent
name objects, only "the same" by value. The null value semantics of a component are name ojects, only "the same" by value. The null value semantics of a component are
<emphasis>ad hoc</emphasis>. When reloading the containing object, Hibernate will assume <emphasis>ad hoc</emphasis>. When reloading the containing object, Hibernate will assume
that if all component columns are null, then the entire component is null. This should that if all component columns are null, then the entire component is null. This should
be okay for most purposes. be okay for most purposes.

6
documentation/manual/src/main/docbook/en-US/content/query_sql.xml
View File

@ -238,9 +238,9 @@ sess.createSQLQuery("SELECT ID, NAME, BIRTHDATE FROM CATS").addEntity(Cat.class)
declared in the mapping metadata. Notice that we may even use the declared in the mapping metadata. Notice that we may even use the
property aliases in the where clause if we like.</para> property aliases in the where clause if we like.</para>
<programlisting><![CDATA[String sql = "SELECT ID as {cat.id}, NAME as {cat.name}, " + <programlisting><![CDATA[String sql = "SELECT ID as {c.id}, NAME as {c.name}, " +
"BIRTHDATE as {cat.birthDate}, MOTHER_ID as {cat.mother}, {mother.*} " + "BIRTHDATE as {c.birthDate}, MOTHER_ID as {c.mother}, {mother.*} " +
"FROM CAT_LOG cat, CAT_LOG mother WHERE {cat.mother} = cat.ID"; "FROM CAT_LOG c, CAT_LOG m WHERE {c.mother} = c.ID";
List loggedCats = sess.createSQLQuery(sql) List loggedCats = sess.createSQLQuery(sql)
.addEntity("cat", Cat.class) .addEntity("cat", Cat.class)

5
documentation/manual/src/main/docbook/en-US/content/tutorial.xml
View File

@ -1566,9 +1566,8 @@ out.close();]]></programlisting>
<para> <para>
Before you compile and deploy the web application, note that an additional library Before you compile and deploy the web application, note that an additional library
is required: <literal>servlet.jar</literal>. This is the Java Servlet Development Kit, is required: <literal>jsdk.jar</literal>. This is the Java servlet development kit,
if you don't have this library already, get it from the if you don't have this library already, get it from the Sun website and copy it to
<ulink url="http://java.sun.com/products/servlet/archive.html">Sun website</ulink> and copy it to
your library directory. However, it will be only used for compilation and excluded your library directory. However, it will be only used for compilation and excluded
from the WAR package. from the WAR package.
</para> </para>

4
documentation/manual/src/main/docbook/es-ES/content/association_mapping.po
View File

@ -1028,7 +1028,7 @@ msgid ""
" </property>\n" " </property>\n"
"</properties>\n" "</properties>\n"
"<property name=\"effectiveEndDate\" type=\"date\"/>\n" "<property name=\"effectiveEndDate\" type=\"date\"/>\n"
"<property name=\"effectiveStartDate\" type=\"date\" not-null=\"true\"/>]]>" "<property name=\"effectiveStateDate\" type=\"date\" not-null=\"true\"/>]]>"
msgstr "" msgstr ""
"<![CDATA[<properties name=\"currentAccountKey\">\n" "<![CDATA[<properties name=\"currentAccountKey\">\n"
" <property name=\"accountNumber\" type=\"string\" " " <property name=\"accountNumber\" type=\"string\" "
@ -1040,7 +1040,7 @@ msgstr ""
" </property>\n" " </property>\n"
" </properties>\n" " </properties>\n"
" <property name=\"effectiveEndDate\" type=\"date\"/>\n" " <property name=\"effectiveEndDate\" type=\"date\"/>\n"
" <property name=\"effectiveStartDate\" type=\"date\" not-" " <property name=\"effectiveStateDate\" type=\"date\" not-"
"null=\"true\"/>]]>" "null=\"true\"/>]]>"
#: index.docbook:266 #: index.docbook:266

2
documentation/manual/src/main/docbook/es-ES/content/component_mapping.po
View File

@ -197,7 +197,7 @@ msgstr ""
msgid "" msgid ""
"Like all value types, components do not support shared references. In other " "Like all value types, components do not support shared references. In other "
"words, two persons could have the same name, but the two person objects " "words, two persons could have the same name, but the two person objects "
"would contain two independent name objects, only \"the same\" by value. The " "would contain two independent name ojects, only \"the same\" by value. The "
"null value semantics of a component are <emphasis>ad hoc</emphasis>. When " "null value semantics of a component are <emphasis>ad hoc</emphasis>. When "
"reloading the containing object, Hibernate will assume that if all component " "reloading the containing object, Hibernate will assume that if all component "
"columns are null, then the entire component is null. This should be okay for " "columns are null, then the entire component is null. This should be okay for "

16
documentation/manual/src/main/docbook/es-ES/content/query_sql.po
View File

@ -439,21 +439,21 @@ msgstr ""
#: index.docbook:192 #: index.docbook:192
msgid "" msgid ""
"<![CDATA[String sql = \"SELECT ID as {cat.id}, NAME as {cat.name}, \" + \n" "<![CDATA[String sql = \"SELECT ID as {c.id}, NAME as {c.name}, \" + \n"
" \"BIRTHDATE as {cat.birthDate}, MOTHER_ID as {cat.mother}, {mother.*} " " \"BIRTHDATE as {c.birthDate}, MOTHER_ID as {c.mother}, {mother.*} "
"\" +\n" "\" +\n"
" \"FROM CAT_LOG cat, CAT_LOG mother WHERE {cat.mother} = cat.ID\";\n" " \"FROM CAT_LOG c, CAT_LOG m WHERE {c.mother} = c.ID\";\n"
"\n" "\n"
"List loggedCats = sess.createSQLQuery(sql)\n" "List loggedCats = sess.createSQLQuery(sql)\n"
" .addEntity(\"cat\", Cat.class)\n" " .addEntity(\"cat\", Cat.class)\n"
" .addEntity(\"mother\", Cat.class).list()\n" " .addEntity(\"mother\", Cat.class).list()\n"
"]]>" "]]>"
msgstr "" msgstr ""
"<![CDATA[String sql = \"SELECT ID as {cat.id}, NAME as {cat.name}, \" + \n" "<![CDATA[String sql = \"SELECT ID as {c.id}, NAME as {c.name}, \" + \n"
" \"BIRTHDATE as {cat." " \"BIRTHDATE as {c."
"birthDate}, MOTHER_ID as {cat.mother}, {mother.*} \" +\n" "birthDate}, MOTHER_ID as {c.mother}, {mother.*} \" +\n"
" \"FROM CAT_LOG cat, " " \"FROM CAT_LOG c, "
"CAT_LOG mother WHERE {cat.mother} = cat.ID\";\n" "CAT_LOG m WHERE {c.mother} = c.ID\";\n"
" \n" " \n"
" List loggedCats = sess." " List loggedCats = sess."
"createSQLQuery(sql)\n" "createSQLQuery(sql)\n"

2
documentation/manual/src/main/docbook/es-ES/content/transactions.po
View File

@ -1464,7 +1464,7 @@ msgstr ""
msgid "" msgid ""
"Clearly, manual version checking is only feasible in very trivial " "Clearly, manual version checking is only feasible in very trivial "
"circumstances and not practical for most applications. Often not only single " "circumstances and not practical for most applications. Often not only single "
"instances, but complete graphs of modified objects have to be checked. " "instances, but complete graphs of modified ojects have to be checked. "
"Hibernate offers automatic version checking with either an extended " "Hibernate offers automatic version checking with either an extended "
"<literal>Session</literal> or detached instances as the design paradigm." "<literal>Session</literal> or detached instances as the design paradigm."
msgstr "" msgstr ""

4
documentation/manual/src/main/docbook/es-ES/content/tutorial.po
View File

@ -2936,7 +2936,7 @@ msgid ""
"That's it, the servlet is complete. A request to the servlet will be " "That's it, the servlet is complete. A request to the servlet will be "
"processed in a single <literal>Session</literal> and <literal>Transaction</" "processed in a single <literal>Session</literal> and <literal>Transaction</"
"literal>. As earlier in the standalone application, Hibernate can " "literal>. As earlier in the standalone application, Hibernate can "
"automatically bind these objects to the current thread of execution. This " "automatically bind these ojects to the current thread of execution. This "
"gives you the freedom to layer your code and access the " "gives you the freedom to layer your code and access the "
"<literal>SessionFactory</literal> in any way you like. Usually you'd use a " "<literal>SessionFactory</literal> in any way you like. Usually you'd use a "
"more sophisticated design and move the data access code into data access " "more sophisticated design and move the data access code into data access "
@ -2945,7 +2945,7 @@ msgstr ""
"That's it, the servlet is complete. A request to the servlet will be " "That's it, the servlet is complete. A request to the servlet will be "
"processed in a single <literal>Session</literal> and <literal>Transaction</" "processed in a single <literal>Session</literal> and <literal>Transaction</"
"literal>. As earlier in the standalone application, Hibernate can " "literal>. As earlier in the standalone application, Hibernate can "
"automatically bind these objects to the current thread of execution. This " "automatically bind these ojects to the current thread of execution. This "
"gives you the freedom to layer your code and access the " "gives you the freedom to layer your code and access the "
"<literal>SessionFactory</literal> in any way you like. Usually you'd use a " "<literal>SessionFactory</literal> in any way you like. Usually you'd use a "
"more sophisticated design and move the data access code into data access " "more sophisticated design and move the data access code into data access "

2
documentation/manual/src/main/docbook/fr-FR/content/association_mapping.po
View File

@ -838,7 +838,7 @@ msgid ""
" </property>\n" " </property>\n"
"</properties>\n" "</properties>\n"
"<property name=\"effectiveEndDate\" type=\"date\"/>\n" "<property name=\"effectiveEndDate\" type=\"date\"/>\n"
"<property name=\"effectiveStartDate\" type=\"date\" not-null=\"true\"/>]]>" "<property name=\"effectiveStateDate\" type=\"date\" not-null=\"true\"/>]]>"
msgstr "" msgstr ""
#. Tag: para #. Tag: para

2
documentation/manual/src/main/docbook/fr-FR/content/component_mapping.po
View File

@ -164,7 +164,7 @@ msgstr ""
msgid "" msgid ""
"Like all value types, components do not support shared references. In other " "Like all value types, components do not support shared references. In other "
"words, two persons could have the same name, but the two person objects " "words, two persons could have the same name, but the two person objects "
"would contain two independent name objects, only \"the same\" by value. The " "would contain two independent name ojects, only \"the same\" by value. The "
"null value semantics of a component are <emphasis>ad hoc</emphasis>. When " "null value semantics of a component are <emphasis>ad hoc</emphasis>. When "
"reloading the containing object, Hibernate will assume that if all component " "reloading the containing object, Hibernate will assume that if all component "
"columns are null, then the entire component is null. This should be okay for " "columns are null, then the entire component is null. This should be okay for "

6
documentation/manual/src/main/docbook/fr-FR/content/query_sql.po
View File

@ -476,10 +476,10 @@ msgstr ""
#: query_sql.xml:192 #: query_sql.xml:192
#, no-c-format #, no-c-format
msgid "" msgid ""
"<![CDATA[String sql = \"SELECT ID as {cat.id}, NAME as {cat.name}, \" + \n" "<![CDATA[String sql = \"SELECT ID as {c.id}, NAME as {c.name}, \" + \n"
" \"BIRTHDATE as {cat.birthDate}, MOTHER_ID as {cat.mother}, {mother.*} " " \"BIRTHDATE as {c.birthDate}, MOTHER_ID as {c.mother}, {mother.*} "
"\" +\n" "\" +\n"
" \"FROM CAT_LOG cat, CAT_LOG mother WHERE {cat.mother} = cat.ID\";\n" " \"FROM CAT_LOG c, CAT_LOG m WHERE {c.mother} = c.ID\";\n"
"\n" "\n"
"List loggedCats = sess.createSQLQuery(sql)\n" "List loggedCats = sess.createSQLQuery(sql)\n"
" .addEntity(\"cat\", Cat.class)\n" " .addEntity(\"cat\", Cat.class)\n"

2
documentation/manual/src/main/docbook/fr-FR/content/transactions.po
View File

@ -1494,7 +1494,7 @@ msgstr ""
msgid "" msgid ""
"Clearly, manual version checking is only feasible in very trivial " "Clearly, manual version checking is only feasible in very trivial "
"circumstances and not practical for most applications. Often not only single " "circumstances and not practical for most applications. Often not only single "
"instances, but complete graphs of modified objects have to be checked. " "instances, but complete graphs of modified ojects have to be checked. "
"Hibernate offers automatic version checking with either an extended " "Hibernate offers automatic version checking with either an extended "
"<literal>Session</literal> or detached instances as the design paradigm." "<literal>Session</literal> or detached instances as the design paradigm."
msgstr "" msgstr ""

2
documentation/manual/src/main/docbook/fr-FR/content/tutorial.po
View File

@ -2669,7 +2669,7 @@ msgid ""
"That's it, the servlet is complete. A request to the servlet will be " "That's it, the servlet is complete. A request to the servlet will be "
"processed in a single <literal>Session</literal> and <literal>Transaction</" "processed in a single <literal>Session</literal> and <literal>Transaction</"
"literal>. As earlier in the standalone application, Hibernate can " "literal>. As earlier in the standalone application, Hibernate can "
"automatically bind these objects to the current thread of execution. This " "automatically bind these ojects to the current thread of execution. This "
"gives you the freedom to layer your code and access the " "gives you the freedom to layer your code and access the "
"<literal>SessionFactory</literal> in any way you like. Usually you'd use a " "<literal>SessionFactory</literal> in any way you like. Usually you'd use a "
"more sophisticated design and move the data access code into data access " "more sophisticated design and move the data access code into data access "

2
documentation/manual/src/main/docbook/ja-JP/content/association_mapping.po
View File

@ -801,7 +801,7 @@ msgid ""
" </property>\n" " </property>\n"
"</properties>\n" "</properties>\n"
"<property name=\"effectiveEndDate\" type=\"date\"/>\n" "<property name=\"effectiveEndDate\" type=\"date\"/>\n"
"<property name=\"effectiveStartDate\" type=\"date\" not-null=\"true\"/>]]>" "<property name=\"effectiveStateDate\" type=\"date\" not-null=\"true\"/>]]>"
msgstr "" msgstr ""
#. Tag: para #. Tag: para

2
documentation/manual/src/main/docbook/ja-JP/content/component_mapping.po
View File

@ -162,7 +162,7 @@ msgstr ""
msgid "" msgid ""
"Like all value types, components do not support shared references. In other " "Like all value types, components do not support shared references. In other "
"words, two persons could have the same name, but the two person objects " "words, two persons could have the same name, but the two person objects "
"would contain two independent name objects, only \"the same\" by value. The " "would contain two independent name ojects, only \"the same\" by value. The "
"null value semantics of a component are <emphasis>ad hoc</emphasis>. When " "null value semantics of a component are <emphasis>ad hoc</emphasis>. When "
"reloading the containing object, Hibernate will assume that if all component " "reloading the containing object, Hibernate will assume that if all component "
"columns are null, then the entire component is null. This should be okay for " "columns are null, then the entire component is null. This should be okay for "

6
documentation/manual/src/main/docbook/ja-JP/content/query_sql.po
View File

@ -465,10 +465,10 @@ msgstr ""
#: query_sql.xml:192 #: query_sql.xml:192
#, no-c-format #, no-c-format
msgid "" msgid ""
"<![CDATA[String sql = \"SELECT ID as {cat.id}, NAME as {cat.name}, \" + \n" "<![CDATA[String sql = \"SELECT ID as {c.id}, NAME as {c.name}, \" + \n"
" \"BIRTHDATE as {cat.birthDate}, MOTHER_ID as {cat.mother}, {mother.*} " " \"BIRTHDATE as {c.birthDate}, MOTHER_ID as {c.mother}, {mother.*} "
"\" +\n" "\" +\n"
" \"FROM CAT_LOG cat, CAT_LOG mother WHERE {cat.mother} = cat.ID\";\n" " \"FROM CAT_LOG c, CAT_LOG m WHERE {c.mother} = c.ID\";\n"
"\n" "\n"
"List loggedCats = sess.createSQLQuery(sql)\n" "List loggedCats = sess.createSQLQuery(sql)\n"
" .addEntity(\"cat\", Cat.class)\n" " .addEntity(\"cat\", Cat.class)\n"

2
documentation/manual/src/main/docbook/ja-JP/content/transactions.po
View File

@ -1418,7 +1418,7 @@ msgstr ""
msgid "" msgid ""
"Clearly, manual version checking is only feasible in very trivial " "Clearly, manual version checking is only feasible in very trivial "
"circumstances and not practical for most applications. Often not only single " "circumstances and not practical for most applications. Often not only single "
"instances, but complete graphs of modified objects have to be checked. " "instances, but complete graphs of modified ojects have to be checked. "
"Hibernate offers automatic version checking with either an extended " "Hibernate offers automatic version checking with either an extended "
"<literal>Session</literal> or detached instances as the design paradigm." "<literal>Session</literal> or detached instances as the design paradigm."
msgstr "" msgstr ""

2
documentation/manual/src/main/docbook/ja-JP/content/tutorial.po
View File

@ -2598,7 +2598,7 @@ msgid ""
"That's it, the servlet is complete. A request to the servlet will be " "That's it, the servlet is complete. A request to the servlet will be "
"processed in a single <literal>Session</literal> and <literal>Transaction</" "processed in a single <literal>Session</literal> and <literal>Transaction</"
"literal>. As earlier in the standalone application, Hibernate can " "literal>. As earlier in the standalone application, Hibernate can "
"automatically bind these objects to the current thread of execution. This " "automatically bind these ojects to the current thread of execution. This "
"gives you the freedom to layer your code and access the " "gives you the freedom to layer your code and access the "
"<literal>SessionFactory</literal> in any way you like. Usually you'd use a " "<literal>SessionFactory</literal> in any way you like. Usually you'd use a "
"more sophisticated design and move the data access code into data access " "more sophisticated design and move the data access code into data access "

2
documentation/manual/src/main/docbook/ko-KR/content/association_mapping.po
View File

@ -811,7 +811,7 @@ msgid ""
" </property>\n" " </property>\n"
"</properties>\n" "</properties>\n"
"<property name=\"effectiveEndDate\" type=\"date\"/>\n" "<property name=\"effectiveEndDate\" type=\"date\"/>\n"
"<property name=\"effectiveStartDate\" type=\"date\" not-null=\"true\"/>]]>" "<property name=\"effectiveStateDate\" type=\"date\" not-null=\"true\"/>]]>"
msgstr "" msgstr ""
#. Tag: para #. Tag: para

2
documentation/manual/src/main/docbook/ko-KR/content/component_mapping.po
View File

@ -162,7 +162,7 @@ msgstr ""
msgid "" msgid ""
"Like all value types, components do not support shared references. In other " "Like all value types, components do not support shared references. In other "
"words, two persons could have the same name, but the two person objects " "words, two persons could have the same name, but the two person objects "
"would contain two independent name objects, only \"the same\" by value. The " "would contain two independent name ojects, only \"the same\" by value. The "
"null value semantics of a component are <emphasis>ad hoc</emphasis>. When " "null value semantics of a component are <emphasis>ad hoc</emphasis>. When "
"reloading the containing object, Hibernate will assume that if all component " "reloading the containing object, Hibernate will assume that if all component "
"columns are null, then the entire component is null. This should be okay for " "columns are null, then the entire component is null. This should be okay for "

6
documentation/manual/src/main/docbook/ko-KR/content/query_sql.po
View File

@ -466,10 +466,10 @@ msgstr ""
#: query_sql.xml:192 #: query_sql.xml:192
#, no-c-format #, no-c-format
msgid "" msgid ""
"<![CDATA[String sql = \"SELECT ID as {cat.id}, NAME as {cat.name}, \" + \n" "<![CDATA[String sql = \"SELECT ID as {c.id}, NAME as {c.name}, \" + \n"
" \"BIRTHDATE as {cat.birthDate}, MOTHER_ID as {cat.mother}, {mother.*} " " \"BIRTHDATE as {c.birthDate}, MOTHER_ID as {c.mother}, {mother.*} "
"\" +\n" "\" +\n"
" \"FROM CAT_LOG cat, CAT_LOG mother WHERE {cat.mother} = cat.ID\";\n" " \"FROM CAT_LOG c, CAT_LOG m WHERE {c.mother} = c.ID\";\n"
"\n" "\n"
"List loggedCats = sess.createSQLQuery(sql)\n" "List loggedCats = sess.createSQLQuery(sql)\n"
" .addEntity(\"cat\", Cat.class)\n" " .addEntity(\"cat\", Cat.class)\n"

2
documentation/manual/src/main/docbook/ko-KR/content/transactions.po
View File

@ -1413,7 +1413,7 @@ msgstr ""
msgid "" msgid ""
"Clearly, manual version checking is only feasible in very trivial " "Clearly, manual version checking is only feasible in very trivial "
"circumstances and not practical for most applications. Often not only single " "circumstances and not practical for most applications. Often not only single "
"instances, but complete graphs of modified objects have to be checked. " "instances, but complete graphs of modified ojects have to be checked. "
"Hibernate offers automatic version checking with either an extended " "Hibernate offers automatic version checking with either an extended "
"<literal>Session</literal> or detached instances as the design paradigm." "<literal>Session</literal> or detached instances as the design paradigm."
msgstr "" msgstr ""

2
documentation/manual/src/main/docbook/ko-KR/content/tutorial.po
View File

@ -2616,7 +2616,7 @@ msgid ""
"That's it, the servlet is complete. A request to the servlet will be " "That's it, the servlet is complete. A request to the servlet will be "
"processed in a single <literal>Session</literal> and <literal>Transaction</" "processed in a single <literal>Session</literal> and <literal>Transaction</"
"literal>. As earlier in the standalone application, Hibernate can " "literal>. As earlier in the standalone application, Hibernate can "
"automatically bind these objects to the current thread of execution. This " "automatically bind these ojects to the current thread of execution. This "
"gives you the freedom to layer your code and access the " "gives you the freedom to layer your code and access the "
"<literal>SessionFactory</literal> in any way you like. Usually you'd use a " "<literal>SessionFactory</literal> in any way you like. Usually you'd use a "
"more sophisticated design and move the data access code into data access " "more sophisticated design and move the data access code into data access "

2
documentation/manual/src/main/docbook/pot/content/association_mapping.pot
View File

@ -685,7 +685,7 @@ msgid ""
" </property>\n" " </property>\n"
"</properties>\n" "</properties>\n"
"<property name=\"effectiveEndDate\" type=\"date\"/>\n" "<property name=\"effectiveEndDate\" type=\"date\"/>\n"
"<property name=\"effectiveStartDate\" type=\"date\" not-null=\"true\"/>]]>" "<property name=\"effectiveStateDate\" type=\"date\" not-null=\"true\"/>]]>"
msgstr "" msgstr ""
#. Tag: para #. Tag: para

2
documentation/manual/src/main/docbook/pot/content/component_mapping.pot
View File

@ -136,7 +136,7 @@ msgstr ""
#. Tag: para #. Tag: para
#: component_mapping.xml:70 #: component_mapping.xml:70
#, no-c-format #, no-c-format
msgid "Like all value types, components do not support shared references. In other words, two persons could have the same name, but the two person objects would contain two independent name objects, only \"the same\" by value. The null value semantics of a component are <emphasis>ad hoc</emphasis>. When reloading the containing object, Hibernate will assume that if all component columns are null, then the entire component is null. This should be okay for most purposes." msgid "Like all value types, components do not support shared references. In other words, two persons could have the same name, but the two person objects would contain two independent name ojects, only \"the same\" by value. The null value semantics of a component are <emphasis>ad hoc</emphasis>. When reloading the containing object, Hibernate will assume that if all component columns are null, then the entire component is null. This should be okay for most purposes."
msgstr "" msgstr ""
#. Tag: para #. Tag: para

6
documentation/manual/src/main/docbook/pot/content/query_sql.pot
View File

@ -310,9 +310,9 @@ msgstr ""
#: query_sql.xml:216 #: query_sql.xml:216
#, no-c-format #, no-c-format
msgid "" msgid ""
"<![CDATA[String sql = \"SELECT ID as {cat.id}, NAME as {cat.name}, \" + \n" "<![CDATA[String sql = \"SELECT ID as {c.id}, NAME as {c.name}, \" + \n"
" \"BIRTHDATE as {cat.birthDate}, MOTHER_ID as {cat.mother}, {mother.*} \" +\n" " \"BIRTHDATE as {c.birthDate}, MOTHER_ID as {c.mother}, {mother.*} \" +\n"
" \"FROM CAT_LOG cat, CAT_LOG mother WHERE {cat.mother} = cat.ID\";\n" " \"FROM CAT_LOG c, CAT_LOG m WHERE {c.mother} = c.ID\";\n"
"\n" "\n"
"List loggedCats = sess.createSQLQuery(sql)\n" "List loggedCats = sess.createSQLQuery(sql)\n"
" .addEntity(\"cat\", Cat.class)\n" " .addEntity(\"cat\", Cat.class)\n"

2
documentation/manual/src/main/docbook/pt-BR/content/association_mapping.po
View File

@ -833,7 +833,7 @@ msgid ""
" </property>\n" " </property>\n"
"</properties>\n" "</properties>\n"
"<property name=\"effectiveEndDate\" type=\"date\"/>\n" "<property name=\"effectiveEndDate\" type=\"date\"/>\n"
"<property name=\"effectiveStartDate\" type=\"date\" not-null=\"true\"/>]]>" "<property name=\"effectiveStateDate\" type=\"date\" not-null=\"true\"/>]]>"
msgstr "" msgstr ""
#. Tag: para #. Tag: para

2
documentation/manual/src/main/docbook/pt-BR/content/component_mapping.po
View File

@ -162,7 +162,7 @@ msgstr ""
msgid "" msgid ""
"Like all value types, components do not support shared references. In other " "Like all value types, components do not support shared references. In other "
"words, two persons could have the same name, but the two person objects " "words, two persons could have the same name, but the two person objects "
"would contain two independent name objects, only \"the same\" by value. The " "would contain two independent name ojects, only \"the same\" by value. The "
"null value semantics of a component are <emphasis>ad hoc</emphasis>. When " "null value semantics of a component are <emphasis>ad hoc</emphasis>. When "
"reloading the containing object, Hibernate will assume that if all component " "reloading the containing object, Hibernate will assume that if all component "
"columns are null, then the entire component is null. This should be okay for " "columns are null, then the entire component is null. This should be okay for "

6
documentation/manual/src/main/docbook/pt-BR/content/query_sql.po
View File

@ -474,10 +474,10 @@ msgstr ""
#: query_sql.xml:192 #: query_sql.xml:192
#, no-c-format #, no-c-format
msgid "" msgid ""
"<![CDATA[String sql = \"SELECT ID as {cat.id}, NAME as {cat.name}, \" + \n" "<![CDATA[String sql = \"SELECT ID as {c.id}, NAME as {c.name}, \" + \n"
" \"BIRTHDATE as {cat.birthDate}, MOTHER_ID as {cat.mother}, {mother.*} " " \"BIRTHDATE as {c.birthDate}, MOTHER_ID as {c.mother}, {mother.*} "
"\" +\n" "\" +\n"
" \"FROM CAT_LOG cat, CAT_LOG mother WHERE {cat.mother} = cat.ID\";\n" " \"FROM CAT_LOG c, CAT_LOG m WHERE {c.mother} = c.ID\";\n"
"\n" "\n"
"List loggedCats = sess.createSQLQuery(sql)\n" "List loggedCats = sess.createSQLQuery(sql)\n"
" .addEntity(\"cat\", Cat.class)\n" " .addEntity(\"cat\", Cat.class)\n"

2
documentation/manual/src/main/docbook/pt-BR/content/transactions.po
View File

@ -1454,7 +1454,7 @@ msgstr ""
msgid "" msgid ""
"Clearly, manual version checking is only feasible in very trivial " "Clearly, manual version checking is only feasible in very trivial "
"circumstances and not practical for most applications. Often not only single " "circumstances and not practical for most applications. Often not only single "
"instances, but complete graphs of modified objects have to be checked. " "instances, but complete graphs of modified ojects have to be checked. "
"Hibernate offers automatic version checking with either an extended " "Hibernate offers automatic version checking with either an extended "
"<literal>Session</literal> or detached instances as the design paradigm." "<literal>Session</literal> or detached instances as the design paradigm."
msgstr "" msgstr ""

2
documentation/manual/src/main/docbook/pt-BR/content/tutorial.po
View File

@ -2652,7 +2652,7 @@ msgid ""
"That's it, the servlet is complete. A request to the servlet will be " "That's it, the servlet is complete. A request to the servlet will be "
"processed in a single <literal>Session</literal> and <literal>Transaction</" "processed in a single <literal>Session</literal> and <literal>Transaction</"
"literal>. As earlier in the standalone application, Hibernate can " "literal>. As earlier in the standalone application, Hibernate can "
"automatically bind these objects to the current thread of execution. This " "automatically bind these ojects to the current thread of execution. This "
"gives you the freedom to layer your code and access the " "gives you the freedom to layer your code and access the "
"<literal>SessionFactory</literal> in any way you like. Usually you'd use a " "<literal>SessionFactory</literal> in any way you like. Usually you'd use a "
"more sophisticated design and move the data access code into data access " "more sophisticated design and move the data access code into data access "

2
documentation/manual/src/main/docbook/zh-CN/content/association_mapping.po
View File

@ -802,7 +802,7 @@ msgid ""
" </property>\n" " </property>\n"
"</properties>\n" "</properties>\n"
"<property name=\"effectiveEndDate\" type=\"date\"/>\n" "<property name=\"effectiveEndDate\" type=\"date\"/>\n"
"<property name=\"effectiveStartDate\" type=\"date\" not-null=\"true\"/>]]>" "<property name=\"effectiveStateDate\" type=\"date\" not-null=\"true\"/>]]>"
msgstr "" msgstr ""
#. Tag: para #. Tag: para

2
documentation/manual/src/main/docbook/zh-CN/content/component_mapping.po
View File

@ -161,7 +161,7 @@ msgstr ""
msgid "" msgid ""
"Like all value types, components do not support shared references. In other " "Like all value types, components do not support shared references. In other "
"words, two persons could have the same name, but the two person objects " "words, two persons could have the same name, but the two person objects "
"would contain two independent name objects, only \"the same\" by value. The " "would contain two independent name ojects, only \"the same\" by value. The "
"null value semantics of a component are <emphasis>ad hoc</emphasis>. When " "null value semantics of a component are <emphasis>ad hoc</emphasis>. When "
"reloading the containing object, Hibernate will assume that if all component " "reloading the containing object, Hibernate will assume that if all component "
"columns are null, then the entire component is null. This should be okay for " "columns are null, then the entire component is null. This should be okay for "

6
documentation/manual/src/main/docbook/zh-CN/content/query_sql.po
View File

@ -452,10 +452,10 @@ msgstr ""
#: query_sql.xml:192 #: query_sql.xml:192
#, no-c-format #, no-c-format
msgid "" msgid ""
"<![CDATA[String sql = \"SELECT ID as {cat.id}, NAME as {cat.name}, \" + \n" "<![CDATA[String sql = \"SELECT ID as {c.id}, NAME as {c.name}, \" + \n"
" \"BIRTHDATE as {cat.birthDate}, MOTHER_ID as {cat.mother}, {mother.*} " " \"BIRTHDATE as {c.birthDate}, MOTHER_ID as {c.mother}, {mother.*} "
"\" +\n" "\" +\n"
" \"FROM CAT_LOG cat, CAT_LOG mother WHERE {cat.mother} = cat.ID\";\n" " \"FROM CAT_LOG c, CAT_LOG m WHERE {c.mother} = c.ID\";\n"
"\n" "\n"
"List loggedCats = sess.createSQLQuery(sql)\n" "List loggedCats = sess.createSQLQuery(sql)\n"
" .addEntity(\"cat\", Cat.class)\n" " .addEntity(\"cat\", Cat.class)\n"

2
documentation/manual/src/main/docbook/zh-CN/content/transactions.po
View File

@ -1318,7 +1318,7 @@ msgstr ""
msgid "" msgid ""
"Clearly, manual version checking is only feasible in very trivial " "Clearly, manual version checking is only feasible in very trivial "
"circumstances and not practical for most applications. Often not only single " "circumstances and not practical for most applications. Often not only single "
"instances, but complete graphs of modified objects have to be checked. " "instances, but complete graphs of modified ojects have to be checked. "
"Hibernate offers automatic version checking with either an extended " "Hibernate offers automatic version checking with either an extended "
"<literal>Session</literal> or detached instances as the design paradigm." "<literal>Session</literal> or detached instances as the design paradigm."
msgstr "" msgstr ""

2
documentation/manual/src/main/docbook/zh-CN/content/tutorial.po
View File

@ -2496,7 +2496,7 @@ msgid ""
"That's it, the servlet is complete. A request to the servlet will be " "That's it, the servlet is complete. A request to the servlet will be "
"processed in a single <literal>Session</literal> and <literal>Transaction</" "processed in a single <literal>Session</literal> and <literal>Transaction</"
"literal>. As earlier in the standalone application, Hibernate can " "literal>. As earlier in the standalone application, Hibernate can "
"automatically bind these objects to the current thread of execution. This " "automatically bind these ojects to the current thread of execution. This "
"gives you the freedom to layer your code and access the " "gives you the freedom to layer your code and access the "
"<literal>SessionFactory</literal> in any way you like. Usually you'd use a " "<literal>SessionFactory</literal> in any way you like. Usually you'd use a "
"more sophisticated design and move the data access code into data access " "more sophisticated design and move the data access code into data access "