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
parent
841cd58cdf
commit
5705431a07
|
|
@ -585,7 +585,7 @@ create table Address ( addressId bigint not null primary key )
|
|||
</property>
|
||||
</properties>
|
||||
<property name="effectiveEndDate" type="date"/>
|
||||
<property name="effectiveStartDate" type="date" not-null="true"/>]]></programlisting>
|
||||
<property name="effectiveStateDate" type="date" not-null="true"/>]]></programlisting>
|
||||
|
||||
<para>
|
||||
alors nous pouvons mapper une association à l'instance <emphasis>courante</emphasis>
|
||||
|
|
|
|||
|
|
@ -574,7 +574,7 @@ create table Address ( addressId bigint not null primary key )
|
|||
</property>
|
||||
</properties>
|
||||
<property name="effectiveEndDate" type="date"/>
|
||||
<property name="effectiveStartDate" type="date" not-null="true"/>]]></programlisting>
|
||||
<property name="effectiveStateDate" type="date" not-null="true"/>]]></programlisting>
|
||||
|
||||
<para>
|
||||
そして、関連を <emphasis>現時点の</emphasis> インスタンス
|
||||
|
|
|
|||
|
|
@ -560,7 +560,7 @@ create table Address ( addressId bigint not null primary key )
|
|||
</property>
|
||||
</properties>
|
||||
<property name="effectiveEndDate" type="date"/>
|
||||
<property name="effectiveStartDate" type="date" not-null="true"/>]]></programlisting>
|
||||
<property name="effectiveStateDate" type="date" not-null="true"/>]]></programlisting>
|
||||
|
||||
<para>
|
||||
그때 우리는 다음을 사용하여 하나의 연관을 <emphasis>현재</emphasis> 인스턴스
|
||||
|
|
|
|||
|
|
@ -588,7 +588,7 @@ Joins de associações mais complexas são extremamente raros. O Hibernate torna
|
|||
</property>
|
||||
</properties>
|
||||
<property name="effectiveEndDate" type="date"/>
|
||||
<property name="effectiveStartDate" type="date" not-null="true"/>]]></programlisting>
|
||||
<property name="effectiveStateDate" type="date" not-null="true"/>]]></programlisting>
|
||||
|
||||
<para>
|
||||
Then we can map an association to the <emphasis>current</emphasis> instance
|
||||
|
|
|
|||
|
|
@ -1444,7 +1444,7 @@ out.close();]]></programlisting>
|
|||
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
|
||||
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.
|
||||
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
|
||||
|
|
|
|||
|
|
@ -541,7 +541,7 @@ create table Address ( addressId bigint not null primary key )
|
|||
</property>
|
||||
</properties>
|
||||
<property name="effectiveEndDate" type="date"/>
|
||||
<property name="effectiveStartDate" type="date" not-null="true"/>]]></programlisting>
|
||||
<property name="effectiveStateDate" type="date" not-null="true"/>]]></programlisting>
|
||||
|
||||
<para>
|
||||
那么我们可以对<emphasis>目前(current)</emphasis>实例(其<literal>effectiveEndDate</literal>为null)使用这样的关联映射:
|
||||
|
|
|
|||
|
|
@ -603,7 +603,7 @@ create table Address ( addressId bigint not null primary key )
|
|||
</property>
|
||||
</properties>
|
||||
<property name="effectiveEndDate" type="date"/>
|
||||
<property name="effectiveStartDate" type="date" not-null="true"/>]]></programlisting>
|
||||
<property name="effectiveStateDate" type="date" not-null="true"/>]]></programlisting>
|
||||
|
||||
<para>
|
||||
Then we can map an association to the <emphasis>current</emphasis> instance
|
||||
|
|
|
|||
|
|
@ -126,7 +126,7 @@
|
|||
<para>
|
||||
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
|
||||
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.
|
||||
|
|
|
|||
|
|
@ -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
|
||||
property aliases in the where clause if we like.</para>
|
||||
|
||||
<programlisting><![CDATA[String sql = "SELECT ID as {cat.id}, NAME as {cat.name}, " +
|
||||
"BIRTHDATE as {cat.birthDate}, MOTHER_ID as {cat.mother}, {mother.*} " +
|
||||
"FROM CAT_LOG cat, CAT_LOG mother WHERE {cat.mother} = cat.ID";
|
||||
<programlisting><![CDATA[String sql = "SELECT ID as {c.id}, NAME as {c.name}, " +
|
||||
"BIRTHDATE as {c.birthDate}, MOTHER_ID as {c.mother}, {mother.*} " +
|
||||
"FROM CAT_LOG c, CAT_LOG m WHERE {c.mother} = c.ID";
|
||||
|
||||
List loggedCats = sess.createSQLQuery(sql)
|
||||
.addEntity("cat", Cat.class)
|
||||
|
|
|
|||
|
|
@ -1566,9 +1566,8 @@ out.close();]]></programlisting>
|
|||
|
||||
<para>
|
||||
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,
|
||||
if you don't have this library already, get it from the
|
||||
<ulink url="http://java.sun.com/products/servlet/archive.html">Sun website</ulink> and copy it to
|
||||
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 Sun website and copy it to
|
||||
your library directory. However, it will be only used for compilation and excluded
|
||||
from the WAR package.
|
||||
</para>
|
||||
|
|
|
|||
|
|
@ -1028,7 +1028,7 @@ msgid ""
|
|||
" </property>\n"
|
||||
"</properties>\n"
|
||||
"<property name=\"effectiveEndDate\" type=\"date\"/>\n"
|
||||
"<property name=\"effectiveStartDate\" type=\"date\" not-null=\"true\"/>]]>"
|
||||
"<property name=\"effectiveStateDate\" type=\"date\" not-null=\"true\"/>]]>"
|
||||
msgstr ""
|
||||
"<![CDATA[<properties name=\"currentAccountKey\">\n"
|
||||
" <property name=\"accountNumber\" type=\"string\" "
|
||||
|
|
@ -1040,7 +1040,7 @@ msgstr ""
|
|||
" </property>\n"
|
||||
" </properties>\n"
|
||||
" <property name=\"effectiveEndDate\" type=\"date\"/>\n"
|
||||
" <property name=\"effectiveStartDate\" type=\"date\" not-"
|
||||
" <property name=\"effectiveStateDate\" type=\"date\" not-"
|
||||
"null=\"true\"/>]]>"
|
||||
|
||||
#: index.docbook:266
|
||||
|
|
|
|||
|
|
@ -197,7 +197,7 @@ msgstr ""
|
|||
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 "
|
||||
"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 "
|
||||
|
|
|
|||
|
|
@ -439,21 +439,21 @@ msgstr ""
|
|||
|
||||
#: index.docbook:192
|
||||
msgid ""
|
||||
"<![CDATA[String sql = \"SELECT ID as {cat.id}, NAME as {cat.name}, \" + \n"
|
||||
" \"BIRTHDATE as {cat.birthDate}, MOTHER_ID as {cat.mother}, {mother.*} "
|
||||
"<![CDATA[String sql = \"SELECT ID as {c.id}, NAME as {c.name}, \" + \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"
|
||||
"List loggedCats = sess.createSQLQuery(sql)\n"
|
||||
" .addEntity(\"cat\", Cat.class)\n"
|
||||
" .addEntity(\"mother\", Cat.class).list()\n"
|
||||
"]]>"
|
||||
msgstr ""
|
||||
"<![CDATA[String sql = \"SELECT ID as {cat.id}, NAME as {cat.name}, \" + \n"
|
||||
" \"BIRTHDATE as {cat."
|
||||
"birthDate}, MOTHER_ID as {cat.mother}, {mother.*} \" +\n"
|
||||
" \"FROM CAT_LOG cat, "
|
||||
"CAT_LOG mother WHERE {cat.mother} = cat.ID\";\n"
|
||||
"<![CDATA[String sql = \"SELECT ID as {c.id}, NAME as {c.name}, \" + \n"
|
||||
" \"BIRTHDATE as {c."
|
||||
"birthDate}, MOTHER_ID as {c.mother}, {mother.*} \" +\n"
|
||||
" \"FROM CAT_LOG c, "
|
||||
"CAT_LOG m WHERE {c.mother} = c.ID\";\n"
|
||||
" \n"
|
||||
" List loggedCats = sess."
|
||||
"createSQLQuery(sql)\n"
|
||||
|
|
|
|||
|
|
@ -1464,7 +1464,7 @@ msgstr ""
|
|||
msgid ""
|
||||
"Clearly, manual version checking is only feasible in very trivial "
|
||||
"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 "
|
||||
"<literal>Session</literal> or detached instances as the design paradigm."
|
||||
msgstr ""
|
||||
|
|
|
|||
|
|
@ -2936,7 +2936,7 @@ msgid ""
|
|||
"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 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 "
|
||||
"<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 "
|
||||
|
|
@ -2945,7 +2945,7 @@ msgstr ""
|
|||
"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 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 "
|
||||
"<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 "
|
||||
|
|
|
|||
|
|
@ -838,7 +838,7 @@ msgid ""
|
|||
" </property>\n"
|
||||
"</properties>\n"
|
||||
"<property name=\"effectiveEndDate\" type=\"date\"/>\n"
|
||||
"<property name=\"effectiveStartDate\" type=\"date\" not-null=\"true\"/>]]>"
|
||||
"<property name=\"effectiveStateDate\" type=\"date\" not-null=\"true\"/>]]>"
|
||||
msgstr ""
|
||||
|
||||
#. Tag: para
|
||||
|
|
|
|||
|
|
@ -164,7 +164,7 @@ msgstr ""
|
|||
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 "
|
||||
"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 "
|
||||
|
|
|
|||
|
|
@ -476,10 +476,10 @@ msgstr ""
|
|||
#: query_sql.xml:192
|
||||
#, no-c-format
|
||||
msgid ""
|
||||
"<![CDATA[String sql = \"SELECT ID as {cat.id}, NAME as {cat.name}, \" + \n"
|
||||
" \"BIRTHDATE as {cat.birthDate}, MOTHER_ID as {cat.mother}, {mother.*} "
|
||||
"<![CDATA[String sql = \"SELECT ID as {c.id}, NAME as {c.name}, \" + \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"
|
||||
"List loggedCats = sess.createSQLQuery(sql)\n"
|
||||
" .addEntity(\"cat\", Cat.class)\n"
|
||||
|
|
|
|||
|
|
@ -1494,7 +1494,7 @@ msgstr ""
|
|||
msgid ""
|
||||
"Clearly, manual version checking is only feasible in very trivial "
|
||||
"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 "
|
||||
"<literal>Session</literal> or detached instances as the design paradigm."
|
||||
msgstr ""
|
||||
|
|
|
|||
|
|
@ -2669,7 +2669,7 @@ msgid ""
|
|||
"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 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 "
|
||||
"<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 "
|
||||
|
|
|
|||
|
|
@ -801,7 +801,7 @@ msgid ""
|
|||
" </property>\n"
|
||||
"</properties>\n"
|
||||
"<property name=\"effectiveEndDate\" type=\"date\"/>\n"
|
||||
"<property name=\"effectiveStartDate\" type=\"date\" not-null=\"true\"/>]]>"
|
||||
"<property name=\"effectiveStateDate\" type=\"date\" not-null=\"true\"/>]]>"
|
||||
msgstr ""
|
||||
|
||||
#. Tag: para
|
||||
|
|
|
|||
|
|
@ -162,7 +162,7 @@ msgstr ""
|
|||
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 "
|
||||
"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 "
|
||||
|
|
|
|||
|
|
@ -465,10 +465,10 @@ msgstr ""
|
|||
#: query_sql.xml:192
|
||||
#, no-c-format
|
||||
msgid ""
|
||||
"<![CDATA[String sql = \"SELECT ID as {cat.id}, NAME as {cat.name}, \" + \n"
|
||||
" \"BIRTHDATE as {cat.birthDate}, MOTHER_ID as {cat.mother}, {mother.*} "
|
||||
"<![CDATA[String sql = \"SELECT ID as {c.id}, NAME as {c.name}, \" + \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"
|
||||
"List loggedCats = sess.createSQLQuery(sql)\n"
|
||||
" .addEntity(\"cat\", Cat.class)\n"
|
||||
|
|
|
|||
|
|
@ -1418,7 +1418,7 @@ msgstr ""
|
|||
msgid ""
|
||||
"Clearly, manual version checking is only feasible in very trivial "
|
||||
"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 "
|
||||
"<literal>Session</literal> or detached instances as the design paradigm."
|
||||
msgstr ""
|
||||
|
|
|
|||
|
|
@ -2598,7 +2598,7 @@ msgid ""
|
|||
"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 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 "
|
||||
"<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 "
|
||||
|
|
|
|||
|
|
@ -811,7 +811,7 @@ msgid ""
|
|||
" </property>\n"
|
||||
"</properties>\n"
|
||||
"<property name=\"effectiveEndDate\" type=\"date\"/>\n"
|
||||
"<property name=\"effectiveStartDate\" type=\"date\" not-null=\"true\"/>]]>"
|
||||
"<property name=\"effectiveStateDate\" type=\"date\" not-null=\"true\"/>]]>"
|
||||
msgstr ""
|
||||
|
||||
#. Tag: para
|
||||
|
|
|
|||
|
|
@ -162,7 +162,7 @@ msgstr ""
|
|||
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 "
|
||||
"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 "
|
||||
|
|
|
|||
|
|
@ -466,10 +466,10 @@ msgstr ""
|
|||
#: query_sql.xml:192
|
||||
#, no-c-format
|
||||
msgid ""
|
||||
"<![CDATA[String sql = \"SELECT ID as {cat.id}, NAME as {cat.name}, \" + \n"
|
||||
" \"BIRTHDATE as {cat.birthDate}, MOTHER_ID as {cat.mother}, {mother.*} "
|
||||
"<![CDATA[String sql = \"SELECT ID as {c.id}, NAME as {c.name}, \" + \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"
|
||||
"List loggedCats = sess.createSQLQuery(sql)\n"
|
||||
" .addEntity(\"cat\", Cat.class)\n"
|
||||
|
|
|
|||
|
|
@ -1413,7 +1413,7 @@ msgstr ""
|
|||
msgid ""
|
||||
"Clearly, manual version checking is only feasible in very trivial "
|
||||
"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 "
|
||||
"<literal>Session</literal> or detached instances as the design paradigm."
|
||||
msgstr ""
|
||||
|
|
|
|||
|
|
@ -2616,7 +2616,7 @@ msgid ""
|
|||
"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 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 "
|
||||
"<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 "
|
||||
|
|
|
|||
|
|
@ -685,7 +685,7 @@ msgid ""
|
|||
" </property>\n"
|
||||
"</properties>\n"
|
||||
"<property name=\"effectiveEndDate\" type=\"date\"/>\n"
|
||||
"<property name=\"effectiveStartDate\" type=\"date\" not-null=\"true\"/>]]>"
|
||||
"<property name=\"effectiveStateDate\" type=\"date\" not-null=\"true\"/>]]>"
|
||||
msgstr ""
|
||||
|
||||
#. Tag: para
|
||||
|
|
|
|||
|
|
@ -136,7 +136,7 @@ msgstr ""
|
|||
#. Tag: para
|
||||
#: component_mapping.xml:70
|
||||
#, 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 ""
|
||||
|
||||
#. Tag: para
|
||||
|
|
|
|||
|
|
@ -310,9 +310,9 @@ msgstr ""
|
|||
#: query_sql.xml:216
|
||||
#, no-c-format
|
||||
msgid ""
|
||||
"<![CDATA[String sql = \"SELECT ID as {cat.id}, NAME as {cat.name}, \" + \n"
|
||||
" \"BIRTHDATE as {cat.birthDate}, MOTHER_ID as {cat.mother}, {mother.*} \" +\n"
|
||||
" \"FROM CAT_LOG cat, CAT_LOG mother WHERE {cat.mother} = cat.ID\";\n"
|
||||
"<![CDATA[String sql = \"SELECT ID as {c.id}, NAME as {c.name}, \" + \n"
|
||||
" \"BIRTHDATE as {c.birthDate}, MOTHER_ID as {c.mother}, {mother.*} \" +\n"
|
||||
" \"FROM CAT_LOG c, CAT_LOG m WHERE {c.mother} = c.ID\";\n"
|
||||
"\n"
|
||||
"List loggedCats = sess.createSQLQuery(sql)\n"
|
||||
" .addEntity(\"cat\", Cat.class)\n"
|
||||
|
|
|
|||
|
|
@ -833,7 +833,7 @@ msgid ""
|
|||
" </property>\n"
|
||||
"</properties>\n"
|
||||
"<property name=\"effectiveEndDate\" type=\"date\"/>\n"
|
||||
"<property name=\"effectiveStartDate\" type=\"date\" not-null=\"true\"/>]]>"
|
||||
"<property name=\"effectiveStateDate\" type=\"date\" not-null=\"true\"/>]]>"
|
||||
msgstr ""
|
||||
|
||||
#. Tag: para
|
||||
|
|
|
|||
|
|
@ -162,7 +162,7 @@ msgstr ""
|
|||
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 "
|
||||
"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 "
|
||||
|
|
|
|||
|
|
@ -474,10 +474,10 @@ msgstr ""
|
|||
#: query_sql.xml:192
|
||||
#, no-c-format
|
||||
msgid ""
|
||||
"<![CDATA[String sql = \"SELECT ID as {cat.id}, NAME as {cat.name}, \" + \n"
|
||||
" \"BIRTHDATE as {cat.birthDate}, MOTHER_ID as {cat.mother}, {mother.*} "
|
||||
"<![CDATA[String sql = \"SELECT ID as {c.id}, NAME as {c.name}, \" + \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"
|
||||
"List loggedCats = sess.createSQLQuery(sql)\n"
|
||||
" .addEntity(\"cat\", Cat.class)\n"
|
||||
|
|
|
|||
|
|
@ -1454,7 +1454,7 @@ msgstr ""
|
|||
msgid ""
|
||||
"Clearly, manual version checking is only feasible in very trivial "
|
||||
"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 "
|
||||
"<literal>Session</literal> or detached instances as the design paradigm."
|
||||
msgstr ""
|
||||
|
|
|
|||
|
|
@ -2652,7 +2652,7 @@ msgid ""
|
|||
"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 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 "
|
||||
"<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 "
|
||||
|
|
|
|||
|
|
@ -802,7 +802,7 @@ msgid ""
|
|||
" </property>\n"
|
||||
"</properties>\n"
|
||||
"<property name=\"effectiveEndDate\" type=\"date\"/>\n"
|
||||
"<property name=\"effectiveStartDate\" type=\"date\" not-null=\"true\"/>]]>"
|
||||
"<property name=\"effectiveStateDate\" type=\"date\" not-null=\"true\"/>]]>"
|
||||
msgstr ""
|
||||
|
||||
#. Tag: para
|
||||
|
|
|
|||
|
|
@ -161,7 +161,7 @@ msgstr ""
|
|||
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 "
|
||||
"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 "
|
||||
|
|
|
|||
|
|
@ -452,10 +452,10 @@ msgstr ""
|
|||
#: query_sql.xml:192
|
||||
#, no-c-format
|
||||
msgid ""
|
||||
"<![CDATA[String sql = \"SELECT ID as {cat.id}, NAME as {cat.name}, \" + \n"
|
||||
" \"BIRTHDATE as {cat.birthDate}, MOTHER_ID as {cat.mother}, {mother.*} "
|
||||
"<![CDATA[String sql = \"SELECT ID as {c.id}, NAME as {c.name}, \" + \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"
|
||||
"List loggedCats = sess.createSQLQuery(sql)\n"
|
||||
" .addEntity(\"cat\", Cat.class)\n"
|
||||
|
|
|
|||
|
|
@ -1318,7 +1318,7 @@ msgstr ""
|
|||
msgid ""
|
||||
"Clearly, manual version checking is only feasible in very trivial "
|
||||
"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 "
|
||||
"<literal>Session</literal> or detached instances as the design paradigm."
|
||||
msgstr ""
|
||||
|
|
|
|||
|
|
@ -2496,7 +2496,7 @@ msgid ""
|
|||
"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 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 "
|
||||
"<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 "
|
||||
|
|
|
|||
Loading…
Reference in New Issue