Menu
▾
▴
[Nhibernate-commit] SF.net SVN: nhibernate:[5271] trunk/nhibernate/doc/reference/modules
|
From: <fab...@us...> - 2010-11-25 16:46:04
|
Revision: 5271
http://nhibernate.svn.sourceforge.net/nhibernate/?rev=5271&view=rev
Author: fabiomaulo
Date: 2010-11-25 16:45:58 +0000 (Thu, 25 Nov 2010)
Log Message:
-----------
Cleaned some reference to NH specific version
Modified Paths:
--------------
trunk/nhibernate/doc/reference/modules/architecture.xml
trunk/nhibernate/doc/reference/modules/filters.xml
trunk/nhibernate/doc/reference/modules/nhibernate_mapping_attributes.xml
trunk/nhibernate/doc/reference/modules/performance.xml
trunk/nhibernate/doc/reference/modules/query_sql.xml
trunk/nhibernate/doc/reference/modules/transactions.xml
Modified: trunk/nhibernate/doc/reference/modules/architecture.xml
===================================================================
--- trunk/nhibernate/doc/reference/modules/architecture.xml 2010-11-25 16:35:51 UTC (rev 5270)
+++ trunk/nhibernate/doc/reference/modules/architecture.xml 2010-11-25 16:45:58 UTC (rev 5271)
@@ -234,7 +234,7 @@
See the API documentation for the <literal>NHibernate.Context.ICurrentSessionContext</literal>
interface for a detailed discussion of its contract. It defines a single method,
<literal>CurrentSession()</literal>, by which the implementation is responsible for
- tracking the current contextual session. Out-of-the-box, NHibernate 1.2.1 comes with several
+ tracking the current contextual session. Out-of-the-box, NHibernate comes with several
implementations of this interface:
</para>
Modified: trunk/nhibernate/doc/reference/modules/filters.xml
===================================================================
--- trunk/nhibernate/doc/reference/modules/filters.xml 2010-11-25 16:35:51 UTC (rev 5270)
+++ trunk/nhibernate/doc/reference/modules/filters.xml 2010-11-25 16:45:58 UTC (rev 5271)
@@ -2,7 +2,7 @@
<title>Filtering data</title>
<para>
- NHibernate 1.2 provides an innovative new approach to handling data with "visibility" rules.
+ NHibernate provides an innovative new approach to handling data with "visibility" rules.
A <emphasis>NHibernate filter</emphasis> is a global, named, parameterized filter that may be
enabled or disabled for a particular NHibernate session.
</para>
@@ -11,7 +11,7 @@
<title>NHibernate filters</title>
<para>
- NHibernate 1.2 adds the ability to pre-define filter criteria and attach those filters at both
+ NHibernate adds the ability to pre-define filter criteria and attach those filters at both
a class and a collection level. A filter criteria is the ability to define a restriction clause
very similiar to the existing "where" attribute available on the class and various collection
elements. Except these filter conditions can be parameterized. The application can then make
Modified: trunk/nhibernate/doc/reference/modules/nhibernate_mapping_attributes.xml
===================================================================
--- trunk/nhibernate/doc/reference/modules/nhibernate_mapping_attributes.xml 2010-11-25 16:35:51 UTC (rev 5270)
+++ trunk/nhibernate/doc/reference/modules/nhibernate_mapping_attributes.xml 2010-11-25 16:45:58 UTC (rev 5271)
@@ -52,7 +52,7 @@
<section id="mapping-attributes-new">
<title>What's new?</title>
<formalpara>
- <title>NHibernate 1.2.0</title>
+ <title>NHibernate</title>
<para>introduces many new features, improvements and changes:</para>
</formalpara>
<orderedlist>
Modified: trunk/nhibernate/doc/reference/modules/performance.xml
===================================================================
--- trunk/nhibernate/doc/reference/modules/performance.xml 2010-11-25 16:35:51 UTC (rev 5270)
+++ trunk/nhibernate/doc/reference/modules/performance.xml 2010-11-25 16:45:58 UTC (rev 5271)
@@ -12,7 +12,7 @@
</para>
<para>
- NHibernate 1.2 defines the following fetching strategies:
+ NHibernate defines the following fetching strategies:
</para>
<itemizedlist>
@@ -128,7 +128,7 @@
<title>Working with lazy associations</title>
<para>
- By default, NHibernate 1.2 uses lazy select fetching for collections and lazy proxy
+ By default, NHibernate uses lazy select fetching for collections and lazy proxy
fetching for single-valued associations. These defaults make sense for almost
all associations in almost all applications.
</para>
@@ -181,7 +181,7 @@
<para>
On the other hand, we often want to choose join fetching (which is non-lazy by
nature) instead of select fetching in a particular transaction. We'll now see
- how to customize the fetching strategy. In NHibernate 1.2, the mechanisms for
+ how to customize the fetching strategy. In NHibernate, the mechanisms for
choosing a fetch strategy are identical for single-valued associations and
collections.
</para>
@@ -280,7 +280,7 @@
</para>
<para>
- By default, NHibernate 1.2 generates proxies (at startup) for all persistent classes
+ By default, NHibernate generates proxies (at startup) for all persistent classes
and uses them to enable lazy fetching of <literal>many-to-one</literal> and
<literal>one-to-one</literal> associations.
</para>
@@ -1160,7 +1160,7 @@
<title>Batch updates</title>
<para>
- NHibernate 1.2 supports batching SQL update commands (<literal>INSERT</literal>,
+ NHibernate supports batching SQL update commands (<literal>INSERT</literal>,
<literal>UPDATE</literal>, <literal>DELETE</literal>) with the following limitations:
</para>
Modified: trunk/nhibernate/doc/reference/modules/query_sql.xml
===================================================================
--- trunk/nhibernate/doc/reference/modules/query_sql.xml 2010-11-25 16:35:51 UTC (rev 5270)
+++ trunk/nhibernate/doc/reference/modules/query_sql.xml 2010-11-25 16:45:58 UTC (rev 5271)
@@ -7,7 +7,7 @@
also provides a clean migration path from a direct SQL/ADO.NET based
application to NHibernate.</para>
- <para>NHibernate 1.2 allows you to specify handwritten SQL (including stored
+ <para>NHibernate allows you to specify handwritten SQL (including stored
procedures) for all create, update, delete, and load operations.</para>
<sect1 id="querysql-creating" revision="4">
@@ -505,7 +505,7 @@
<sect2 id="sp_query" revision="1">
<title>Using stored procedures for querying</title>
- <para>NHibernate 1.2 introduces support for queries via stored procedures
+ <para>NHibernate introduces support for queries via stored procedures
and functions. Most of the following documentation is equivalent for
both. The stored procedure/function must return a resultset to be able to work
with NHibernate. An example of such a stored function in MS SQL Server 2000 and
@@ -593,7 +593,7 @@
<sect1 id="querysql-cud">
<title>Custom SQL for create, update and delete</title>
- <para>NHibernate 1.2 can use custom SQL statements for create, update, and
+ <para>NHibernate can use custom SQL statements for create, update, and
delete operations. The class and collection persisters in NHibernate
already contain a set of configuration time generated strings (insertsql,
deletesql, updatesql etc.). The mapping tags
Modified: trunk/nhibernate/doc/reference/modules/transactions.xml
===================================================================
--- trunk/nhibernate/doc/reference/modules/transactions.xml 2010-11-25 16:35:51 UTC (rev 5270)
+++ trunk/nhibernate/doc/reference/modules/transactions.xml 2010-11-25 16:45:58 UTC (rev 5271)
@@ -516,7 +516,7 @@
The legacy (1.0.x) behavior of NHibernate in regards to ADO.NET connection management
was that a <literal>ISession</literal> would obtain a connection when it was first
needed and then hold unto that connection until the session was closed.
- NHibernate 1.2 introduced the notion of connection release modes to tell a session
+ NHibernate introduced the notion of connection release modes to tell a session
how to handle its ADO.NET connections. Note that the following discussion is pertinent
only to connections provided through a configured <literal>IConnectionProvider</literal>;
user-supplied connections are outside the breadth of this discussion. The different
@@ -569,7 +569,7 @@
</itemizedlist>
<para>
- As of NHibernate 1.2.0, if your application manages transactions through .NET APIs such as <literal>
+ As of NHibernate, if your application manages transactions through .NET APIs such as <literal>
System.Transactions</literal> library, <literal>ConnectionReleaseMode.AfterTransaction</literal> may cause
NHibernate to open and close several connections during one transaction, leading to unnecessary overhead and
transaction promotion from local to distributed. Specifying <literal>ConnectionReleaseMode.OnClose</literal>
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
