Author: stliu
Date: 2010-02-03 01:51:48 -0500 (Wed, 03 Feb 2010)
New Revision: 18685
Modified:
core/trunk/documentation/manual/src/main/docbook/en-US/content/best_practices.xml
Log:
HHH-4824 localpath appeared in the doc xml
Modified:
core/trunk/documentation/manual/src/main/docbook/en-US/content/best_practices.xml
===================================================================
---
core/trunk/documentation/manual/src/main/docbook/en-US/content/best_practices.xml 2010-02-03
05:16:26 UTC (rev 18684)
+++
core/trunk/documentation/manual/src/main/docbook/en-US/content/best_practices.xml 2010-02-03
06:51:48 UTC (rev 18685)
@@ -125,7 +125,7 @@
In performance-critical areas of the system, some kinds of operations
might benefit from
direct JDBC. Do not assume, however, that JDBC is necessarily faster.
Please wait until you <emphasis>know</emphasis> something is a bottleneck.
If you need to use direct JDBC,
- you can open a Hibernate <literal>Session</literal> and
usingfile:///usr/share/doc/HTML/en-US/index.html that JDBC connection. This
+ you can open a Hibernate <literal>Session</literal>, wrap
your JDBC operation as a <literal>org.hibernate.jdbc.Work</literal> object and
using that JDBC connection. This
way you can still use the same transaction strategy and underlying
connection provider.
</para>
</listitem>
Show replies by date