[hibernate-commits] Hibernate SVN: r12715 - in core/trunk/documentation/manual: ja-JP/src/main/docbook/modules and 3 other directories.

Author: d.plentz Date: 2007-07-04 00:55:21 -0400 (Wed, 04 Jul 2007) New Revision: 12715 Modified: core/trunk/documentation/manual/en-US/src/main/docbook/modules/transactions.xml core/trunk/documentation/manual/ja-JP/src/main/docbook/modules/transactions.xml core/trunk/documentation/manual/ko-KR/src/main/docbook/modules/transactions.xml core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/transactions.xml core/trunk/documentation/manual/zh-CN/src/main/docbook/modules/transactions.xml Log: [HHH-2567] Update reference to use FlushMode.MANUAL Modified: core/trunk/documentation/manual/en-US/src/main/docbook/modules/transactions.xml =================================================================== --- core/trunk/documentation/manual/en-US/src/main/docbook/modules/transactions.xml 2007-07-03 18:13:56 UTC (rev 12714) +++ core/trunk/documentation/manual/en-US/src/main/docbook/modules/transactions.xml 2007-07-04 04:55:21 UTC (rev 12715) @@ -802,7 +802,7 @@ force a version check on data you aren't updating, you may call <literal>Session.lock()</literal> with <literal>LockMode.READ</literal> on any objects that might have been updated by another transaction. You don't need to lock any data that you <emphasis>are</emphasis> updating. - Usually you would set <literal>FlushMode.NEVER</literal> on an extended <literal>Session</literal>, + Usually you would set <literal>FlushMode.MANUAL</literal> on an extended <literal>Session</literal>, so that only the last database transaction cycle is allowed to actually persist all modifications made in this conversation. Hence, only this last database transaction would include the <literal>flush()</literal> operation, and then also Modified: core/trunk/documentation/manual/ja-JP/src/main/docbook/modules/transactions.xml =================================================================== --- core/trunk/documentation/manual/ja-JP/src/main/docbook/modules/transactions.xml 2007-07-03 18:13:56 UTC (rev 12714) +++ core/trunk/documentation/manual/ja-JP/src/main/docbook/modules/transactions.xml 2007-07-04 04:55:21 UTC (rev 12715) @@ -937,7 +937,7 @@ ��Ăяo�����Ƃ��ł��܂��B �X�V���� <emphasis>����</emphasis> �f�[�^���b�N����K�v�͂���܂���B - �ʏ�A�g�� <literal>Session</literal> �� <literal>FlushMode.NEVER</literal> + �ʏ�A�g�� <literal>Session</literal> �� <literal>FlushMode.MANUAL</literal> ��Z�b�g���܂��B �Ō�̃f�[�^�x�[�X�g�����U�N�V�����̎����ł̂݁A �Θb�̒��ŕύX���ꂽ���ׂĂ���ۂɉi���������邽�߂ł��B Modified: core/trunk/documentation/manual/ko-KR/src/main/docbook/modules/transactions.xml =================================================================== --- core/trunk/documentation/manual/ko-KR/src/main/docbook/modules/transactions.xml 2007-07-03 18:13:56 UTC (rev 12714) +++ core/trunk/documentation/manual/ko-KR/src/main/docbook/modules/transactions.xml 2007-07-04 04:55:21 UTC (rev 12715) @@ -721,7 +721,7 @@ 또 다른 트랜잭션에 의해 업데이트되었을 수도 있는 임의의 객체들에 대해 <literal>LockMode.READ</literal>로서 <literal>Session.lock()</literal>을 호출할 수도 있다. 당신은 당신이 업데이트 중인 임의의 데이터를 잠금할 필요가 없다. 대개 당신은 마지막 데이터베이스 트랜잭션 주기만이 이 대화 내에서 행해진 모든 변경들을 실제로 영속화시키는 것이 허용되도록 하기 위해, - 하나의 확장된 <literal>Session</literal>에 대해 <literal>FlushMode.NEVER</literal>를 설정할 것이다. + 하나의 확장된 <literal>Session</literal>에 대해 <literal>FlushMode.MANUAL</literal>를 설정할 것이다. 그러므로 오직 이 마지막 데이터베이스 트랜잭션 만이 <literal>flush()</literal> 오퍼레이션을 포함할 것이고, 또한 대화를 종료시키기 위해 세션을 <literal>close()</literal>할 것이다. </para> Modified: core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/transactions.xml =================================================================== --- core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/transactions.xml 2007-07-03 18:13:56 UTC (rev 12714) +++ core/trunk/documentation/manual/pt-BR/src/main/docbook/modules/transactions.xml 2007-07-04 04:55:21 UTC (rev 12715) @@ -829,7 +829,7 @@ forçar uma checagem de versão em dados que você não está atualizando, você pode chamar <literal>Session.lock()</literal> com o <literal>LockMode.READ</literal> em todos os objetos que possam ter sido atualizados por uma outra transação. Você não necessita bloquear nenhum - dado para atualizar. Geralmente você configuraria <literal>FlushMode.NEVER</literal> em uma + dado para atualizar. Geralmente você configuraria <literal>FlushMode.MANUAL</literal> em uma <literal>Session</literal> estendida, de modo que somente o último ciclo da transação tenha permissão de persistir todas as modificações feitas nesta conversação. Disso, somente esta última transação incluiria a operação <literal>flush()</literal> e então chamar também <literal>close()</literal> Modified: core/trunk/documentation/manual/zh-CN/src/main/docbook/modules/transactions.xml =================================================================== --- core/trunk/documentation/manual/zh-CN/src/main/docbook/modules/transactions.xml 2007-07-03 18:13:56 UTC (rev 12714) +++ core/trunk/documentation/manual/zh-CN/src/main/docbook/modules/transactions.xml 2007-07-04 04:55:21 UTC (rev 12715) @@ -618,7 +618,7 @@ session.close(); // Only for last transaction in conversation]]></programlisting> <para> - <literal>foo</literal>对象知道它是在哪个<literal>Session</literal>中被装入的。在一个旧session中开启一个新的数据库事务，会导致session获取一个新的连接，并恢复session的功能。将数据库事务提交，使得session从JDBC连接断开，并将此连接交还给连接池。在重新连接之后，要强制对你没有更新的数据进行一次版本检查，你可以对所有可能被其他事务修改过的对象，使用参数<literal>LockMode.READ</literal>来调用<literal>Session.lock()</literal>。你不用lock任何你<emphasis>正在</emphasis>更新的数据。一般你会在扩展的<literal>Session</literal>上设置<literal>FlushMode.NEVER</literal>，因此只有最后一个数据库事务循环才会真正的吧整个对话中发生的修改发送到数据库。因此，只有这最后一次数据库事务才会包含<literal>flush()</literal>操作，然后在整个对话结束后，还要<literal! + <literal>foo</literal>对象知道它是在哪个<literal>Session</literal>中被装入的。在一个旧session中开启一个新的数据库事务，会导致session获取一个新的连接，并恢复session的功能。将数据库事务提交，使得session从JDBC连接断开，并将此连接交还给连接池。在重新连接之后，要强制对你没有更新的数据进行一次版本检查，你可以对所有可能被其他事务修改过的对象，使用参数<literal>LockMode.READ</literal>来调用<literal>Session.lock()</literal>。你不用lock任何你<emphasis>正在</emphasis>更新的数据。一般你会在扩展的<literal>Session</literal>上设置<literal>FlushMode.MANUAL</literal>，因此只有最后一个数据库事务循环才会真正的吧整个对话中发生的修改发送到数据库。因此，只有这最后一次数据库事务才会包含<literal>flush()</literal>操作，然后在整个对话结束后，还要<litera! l>close()</literal>这个session。 </para> <para>