From: <fab...@us...> - 2009-05-15 22:59:19
|
Revision: 4323 http://nhibernate.svn.sourceforge.net/nhibernate/?rev=4323&view=rev Author: fabiomaulo Date: 2009-05-15 22:59:12 +0000 (Fri, 15 May 2009) Log Message: ----------- Fix NH-1780 and related Modified Paths: -------------- trunk/nhibernate/doc/reference/modules/component_mapping.xml trunk/nhibernate/doc/reference/modules/example_parentchild.xml Modified: trunk/nhibernate/doc/reference/modules/component_mapping.xml =================================================================== --- trunk/nhibernate/doc/reference/modules/component_mapping.xml 2009-05-15 22:37:17 UTC (rev 4322) +++ trunk/nhibernate/doc/reference/modules/component_mapping.xml 2009-05-15 22:59:12 UTC (rev 4323) @@ -270,14 +270,14 @@ </para> <para> - You may instead implement <literal>IInterceptor.IsUnsaved()</literal> if + You may instead implement <literal>IInterceptor.IsTransient()</literal> if you wish to use <literal>SaveOrUpdate()</literal> or cascading save / update. As an alternative, you may also set the <literal>unsaved-value</literal> attribute on a <literal><version></literal> (or <literal><timestamp></literal>) element to specify a value that indicates a new transient instance. In this case, the version of the entity is used instead of the (assigned) identifier and you don't have - to implement <literal>IInterceptor.IsUnsaved()</literal> yourself. + to implement <literal>IInterceptor.IsTransient()</literal> yourself. </para> <para> Modified: trunk/nhibernate/doc/reference/modules/example_parentchild.xml =================================================================== --- trunk/nhibernate/doc/reference/modules/example_parentchild.xml 2009-05-15 22:37:17 UTC (rev 4322) +++ trunk/nhibernate/doc/reference/modules/example_parentchild.xml 2009-05-15 22:59:12 UTC (rev 4323) @@ -310,7 +310,7 @@ <para> There is one further possibility. There is a new <literal>IInterceptor</literal> method named - <literal>IsUnsaved()</literal> which lets the application implement its own strategy for distinguishing + <literal>IsTransient()</literal> which lets the application implement its own strategy for distinguishing newly instantiated objects. For example, you could define a base class for your persistent classes. </para> @@ -338,11 +338,12 @@ <para> (The <literal>saved</literal> property is non-persistent.) - Now implement <literal>IsUnsaved()</literal>, along with <literal>OnLoad()</literal> + Now implement <literal>IsTransient()</literal>, along with <literal>OnLoad()</literal> and <literal>OnSave()</literal> as follows. </para> - <programlisting><![CDATA[public object IsUnsaved(object entity) + <programlisting> + <![CDATA[public object IsTransient(object entity) { if (entity is Persistent) { This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
From: <fab...@us...> - 2009-10-16 19:06:06
|
Revision: 4765 http://nhibernate.svn.sourceforge.net/nhibernate/?rev=4765&view=rev Author: fabiomaulo Date: 2009-10-16 19:05:59 +0000 (Fri, 16 Oct 2009) Log Message: ----------- Merge r4764 (fix NH-1943 references) Modified Paths: -------------- trunk/nhibernate/doc/reference/modules/configuration.xml trunk/nhibernate/doc/reference/modules/quickstart.xml Modified: trunk/nhibernate/doc/reference/modules/configuration.xml =================================================================== --- trunk/nhibernate/doc/reference/modules/configuration.xml 2009-10-16 19:04:31 UTC (rev 4764) +++ trunk/nhibernate/doc/reference/modules/configuration.xml 2009-10-16 19:05:59 UTC (rev 4765) @@ -458,12 +458,10 @@ <entry> Specifies the bytecode provider to use to optimize the use of reflection in NHibernate. Use <literal>null</literal> to disable the optimization completely, <literal>lcg</literal> - to use lightweight code generation (supported on .NET 2.0 only), and <literal> - codedom</literal> to use CodeDOM-based code generation (supported on .NET 1.1, has problems - with generic types on .NET 2.0). + to use lightweight code generation. <para> <emphasis role="strong">eg.</emphasis> - <literal>null</literal> | <literal>lcg</literal> | <literal>codedom</literal> + <literal>null</literal> | <literal>lcg</literal> </para> </entry> </row> Modified: trunk/nhibernate/doc/reference/modules/quickstart.xml =================================================================== --- trunk/nhibernate/doc/reference/modules/quickstart.xml 2009-10-16 19:04:31 UTC (rev 4764) +++ trunk/nhibernate/doc/reference/modules/quickstart.xml 2009-10-16 19:05:59 UTC (rev 4765) @@ -5,7 +5,7 @@ <title>Getting started with NHibernate</title> <para> - This tutorial explains a setup of NHibernate 1.0.2 within a Microsoft + This tutorial explains a setup of NHibernate 2.1.0 within a Microsoft environment. The tools used in this tutorial are: </para> @@ -15,13 +15,13 @@ ASP.NET. </listitem> <listitem> - Microsoft SQL Server 2000 - the database server. This tutorial uses - the desktop edition (MSDE), a free download from Microsoft. Support + Microsoft SQL Server 2005 - the database server. This tutorial uses + the desktop edition (SQL-EXPRESS), a free download from Microsoft. Support for other databases is only a matter of changing the NHibernate SQL dialect and driver configuration. </listitem> <listitem> - Microsoft Visual Studio .NET 2003 - the development environment. + Microsoft Visual Studio .NET (at leats 2005) - the development environment. </listitem> </orderedlist> @@ -40,7 +40,8 @@ configuration elements according to the listing below: </para> - <programlisting><![CDATA[<?xml version="1.0" encoding="utf-8" ?> + <programlisting> + <![CDATA[<?xml version="1.0" encoding="utf-8" ?> <configuration> <!-- Add this element --> <configSections> @@ -53,10 +54,11 @@ <!-- Add this element --> <hibernate-configuration xmlns="urn:nhibernate-configuration-2.2"> <session-factory> - <property name="dialect">NHibernate.Dialect.MsSql2000Dialect</property> + <property name="dialect">NHibernate.Dialect.MsSql2005Dialect</property> <property name="connection.provider">NHibernate.Connection.DriverConnectionProvider</property> - <property name="connection.connection_string">Server=(local);initial catalog=quickstart;Integrated Security=SSPI</property> - + <property name="connection.connection_string">Server=localhost\SQLEXPRESS;initial catalog=quickstart;Integrated Security=True</property> + <property name="proxyfactory.factory_class">NHibernate.ByteCode.LinFu.ProxyFactoryFactory, NHibernate.ByteCode.LinFu</property> + <mapping assembly="QuickStart" /> </session-factory> </hibernate-configuration> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |
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. |