nhibernate-issues — Updates to JIRA issues are sent to this list

[nhibernate-issues] [JIRA] Closed: (NH-782) Update to latest DynamicProxy to fix race condition

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-782?page=all ]
     
Sergey Koshcheyev closed NH-782:
--------------------------------

    Resolution: Fixed

> Update to latest DynamicProxy to fix race condition
> ---------------------------------------------------
>
>          Key: NH-782
>          URL: http://jira.nhibernate.org/browse/NH-782
>      Project: NHibernate
>         Type: Bug
>   Components: Core
>     Versions: 1.0.2, 1.2.0.Beta1
>     Reporter: Pawel Pabich
>      Fix For: 1.2.0.Beta2, 1.0.3

>
> .NET farmework 2.0
> MS Sql Server 2005
> This issues is described on the forum:
> http://forum.hibernate.org/viewtopic.php?t=952999&postdays=0&postorder=asc&start=15
> That's how I create my session factory:
> static DataStore()
> {
> sessionFactory = new Configuration().Configure().BuildSessionFactory();
> }
> That's how I create and use my session object
> public void UpdateX(X newX,)
> {
> using (ISession session = sessionFactory.OpenSession())
> {
> using (ITransaction transaction = session.BeginTransaction(IsolationLevel.RepeatableRead))
> {
> // some statements
> transaction.Commit();
> }
> }
> }
> Now when I call UpdateX using two concurrent threads(they use the same session factory but different sessions) I'm getting this error:
> NHibernate.HibernateException: Creating a proxy instance failed ---> System.ArgumentException: Duplicate type name within an assembly.
> at System.Reflection.Emit.AssemblyBuilderData.CheckTypeNameConflict(String strTypeName, TypeBuilder enclosingType)
> at System.Reflection.Emit.TypeBuilder.Init(String fullname, TypeAttributes attr, Type parent, Type[] interfaces, Module module, PackingSize iPackingSize, Int32 iTypeSize, TypeBuilder enclosingType)
> at System.Reflection.Emit.ModuleBuilder.DefineTypeNoLock(String name, TypeAttributes attr, Type parent, Type[] interfaces)
> at System.Reflection.Emit.ModuleBuilder.DefineType(String name, TypeAttributes attr, Type parent, Type[] interfaces)
> at Castle.DynamicProxy.Builder.CodeBuilder.EasyType..ctor(ModuleScope modulescope, String name, Type baseType, Type[] interfaces, Boolean serializable)
> at Castle.DynamicProxy.Builder.CodeGenerators.BaseCodeGenerator.CreateTypeBuilder(String typeName, Type baseType, Type[] interfaces)
> at Castle.DynamicProxy.Builder.CodeGenerators.ClassProxyGenerator.GenerateCode(Type baseClass, Type[] interfaces)
> at Castle.DynamicProxy.Builder.DefaultProxyBuilder.CreateClassProxy(Type theClass, Type[] interfaces)
> at Castle.DynamicProxy.ProxyGenerator.CreateClassProxy(Type baseClass, Type[] interfaces, IInterceptor interceptor, Boolean checkAbstract, Object[] argumentsForConstructor)
> at NHibernate.Proxy.CastleProxyFactory.GetProxy(Object id, ISessionImplementor session)
> --- End of inner exception stack trace ---
> at NHibernate.Proxy.CastleProxyFactory.GetProxy(Object id, ISessionImplementor session)
> at NHibernate.Persister.Entity.AbstractEntityPersister.CreateProxy(Object id, ISessionImplementor session)
> at NHibernate.Impl.SessionImpl.DoLoadByClass(Type clazz, Object id, Boolean checkDeleted, Boolean allowProxyCreation)
> at NHibernate.Impl.SessionImpl.InternalLoad(Type clazz, Object id, Boolean isNullable)
> at NHibernate.Type.EntityType.ResolveIdentifier(Object id, ISessionImplementor session)
> at NHibernate.Type.EntityType.ResolveIdentifier(Object id, ISessionImplementor session, Object owner)
> at NHibernate.Impl.SessionImpl.InitializeEntity(Object obj)
> at NHibernate.Loader.Loader.InitializeEntitiesAndCollections(IList hydratedObjects, Object resultSetId, ISessionImplementor session)
> at NHibernate.Loader.Loader.DoQuery(ISessionImplementor session, QueryParameters queryParameters, Boolean returnProxies)
> at NHibernate.Loader.Loader.DoQueryAndInitializeNonLazyCollections(ISessionImplementor session, QueryParameters queryParameters, Boolean returnProxies)
> at NHibernate.Loader.Loader.DoList(ISessionImplementor session, QueryParameters queryParameters)
> at NHibernate.Loader.Loader.ListIgnoreQueryCache(ISessionImplementor session, QueryParameters queryParameters)
> at NHibernate.Loader.Loader.List(ISessionImplementor session, QueryParameters queryParameters, ISet querySpaces, IType[] resultTypes)
> at NHibernate.Loader.Criteria.CriteriaLoader.List(ISessionImplementor session)
> at NHibernate.Impl.SessionImpl.Find(CriteriaImpl criteria, IList results)
> at NHibernate.Impl.SessionImpl.Find(CriteriaImpl criteria)
> at NHibernate.Impl.CriteriaImpl.List()
> at NHibernate.Impl.CriteriaImpl.UniqueResult()
> at FullTilt.Tools.Services.ScheduledMessage.FTP.PersistentStorage.DataStore.GetScheduledMessageByMessageIndexInternal(Int64 messageIndex, Boolean fetchRelatedObjects, ISession session) in C:\Work\Code\FullTilt\Tools_TableSpam\Services\ScheduledMessage\ScheduledMessage.FTP\PersistentStorage\DataStore.cs:line 289
> at FullTilt.Tools.Services.ScheduledMessage.FTP.PersistentStorage.DataStore.DeleteScheduledMessageByMessageIndexInternal(Int64 messageIndex, ISession session) in C:\Work\Code\FullTilt\Tools_TableSpam\Services\ScheduledMessage\ScheduledMessage.FTP\PersistentStorage\DataStore.cs:line 259
> at FullTilt.Tools.Services.ScheduledMessage.FTP.PersistentStorage.DataStore.UpdateScheduledMessage(ScheduledMessageEntity newMessage, Int32 timeSpan) in C:\Work\Code\FullTilt\Tools_TableSpam\Services\ScheduledMessage\ScheduledMessage.FTP\PersistentStorage\DataStore.cs:line 219
> at TestConsoleApplication.Program.Update(Object obj) in C:\Work\Code\FullTilt\Tools_TableSpam\Services\ScheduledMessage\ScheduledMessage.FTP\TestConsoleApplication\Program.cs:line 219

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.nhibernate.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[nhibernate-issues] [JIRA] Commented: (NH-789) ORA-08177 not wrapped as StaleObjectException with Oracle.DataAcess

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-789?page=comments#action_14277 ]
     
Sergey Koshcheyev commented on NH-789:
--------------------------------------

Then just change from type="Timestamp" to type="DateTime" if you don't need the milliseconds. The exception has nothing to do with NHibernate, looks like Oracle does its own locking or something. NHibernate only throws StaleStateException if the count of rows affected by UPDATE/INSERT don't match what it expects, this functionality doesn't rely on Oracle errors, these are different things.

> ORA-08177 not wrapped as StaleObjectException with Oracle.DataAcess
> -------------------------------------------------------------------
>
>          Key: NH-789
>          URL: http://jira.nhibernate.org/browse/NH-789
>      Project: NHibernate
>         Type: Bug
>   Components: Core
>     Versions: 1.0.2
>     Reporter: Johannes Schmidt

>
> The OracleClientDriver does not support milliseconds for Timestamp mapping. So, I decided to used OracleDataClientDriver. I'm using OptimisticLock settings in the mapping file. If there is a concurrency problem, I except a StaleObjectException, but the ADOExceptionReporter throws an exceptions that contains only the text of the Oracle exception for ORA-08177.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.nhibernate.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[nhibernate-issues] [JIRA] Commented: (NH-789) ORA-08177 not wrapped as StaleObjectException with Oracle.DataAcess

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-789?page=comments#action_14276 ]
     
Johannes Schmidt commented on NH-789:
-------------------------------------

#1 http://ora-08177.ora-code.com/ : using oracle 9i with optimistic lock strategy
# 2 configuration
<nhibernate>
    <add key="hibernate.connection.provider" value="NHibernate.Connection.DriverConnectionProvider" />
    <add key="hibernate.dialect" value="NHibernate.Dialect.Oracle9Dialect" />
    <add key="hibernate.connection.driver_class" value="NHibernate.Driver.OracleClientDriver" />
    <add key="hibernate.connection.connection_string" value="Enlist=false;Data Source=pc;User Id=user;Password=secret;" />
    <add key="hibernate.connection.isolation" value="Serializable" />  </nhibernate>
# 3 mapping
<hibernate-mapping xmlns = "urn:nhibernate-mapping-2.0" 
                   namespace = "OraclePoc" 
                   assembly = "OraclePoc">

  <class name="OraclePoc.MyTest" 
         table="MyTest">

    <!-- technical header -->
    <id name="TechnicalId" column="TechnicalId" type="String">
      <generator class="uuid.hex"/>
    </id>
    
    <!-- properties -->
    <property name="TimeTest" type="Timestamp"/>
    <property name="Name" type="String" not-null="true"/>
  </class>
</hibernate-mapping>

When I'm using OracleClientDriver the TimeTest will not save milliseconds. If I'm using OracleDataClientdriver, the milliseconds will be saved correctly. But there is no StaleObjectException, just an exception from ADOExceptionReporter.

> ORA-08177 not wrapped as StaleObjectException with Oracle.DataAcess
> -------------------------------------------------------------------
>
>          Key: NH-789
>          URL: http://jira.nhibernate.org/browse/NH-789
>      Project: NHibernate
>         Type: Bug
>   Components: Core
>     Versions: 1.0.2
>     Reporter: Johannes Schmidt

>
> The OracleClientDriver does not support milliseconds for Timestamp mapping. So, I decided to used OracleDataClientDriver. I'm using OptimisticLock settings in the mapping file. If there is a concurrency problem, I except a StaleObjectException, but the ADOExceptionReporter throws an exceptions that contains only the text of the Oracle exception for ORA-08177.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.nhibernate.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[nhibernate-issues] [JIRA] Updated: (NH-782) Update to latest DynamicProxy to fix race condition

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-782?page=all ]

Sergey Koshcheyev updated NH-782:
---------------------------------

    Fix Version: 1.2.0.Beta2
                 1.0.3
        Version: 1.0.2
        Summary: Update to latest DynamicProxy to fix race condition  (was: Creating a proxy instance failed )

> Update to latest DynamicProxy to fix race condition
> ---------------------------------------------------
>
>          Key: NH-782
>          URL: http://jira.nhibernate.org/browse/NH-782
>      Project: NHibernate
>         Type: Bug
>   Components: Core
>     Versions: 1.0.2, 1.2.0.Beta1
>     Reporter: Pawel Pabich
>      Fix For: 1.2.0.Beta2, 1.0.3

>
> .NET farmework 2.0
> MS Sql Server 2005
> This issues is described on the forum:
> http://forum.hibernate.org/viewtopic.php?t=952999&postdays=0&postorder=asc&start=15
> That's how I create my session factory:
> static DataStore()
> {
> sessionFactory = new Configuration().Configure().BuildSessionFactory();
> }
> That's how I create and use my session object
> public void UpdateX(X newX,)
> {
> using (ISession session = sessionFactory.OpenSession())
> {
> using (ITransaction transaction = session.BeginTransaction(IsolationLevel.RepeatableRead))
> {
> // some statements
> transaction.Commit();
> }
> }
> }
> Now when I call UpdateX using two concurrent threads(they use the same session factory but different sessions) I'm getting this error:
> NHibernate.HibernateException: Creating a proxy instance failed ---> System.ArgumentException: Duplicate type name within an assembly.
> at System.Reflection.Emit.AssemblyBuilderData.CheckTypeNameConflict(String strTypeName, TypeBuilder enclosingType)
> at System.Reflection.Emit.TypeBuilder.Init(String fullname, TypeAttributes attr, Type parent, Type[] interfaces, Module module, PackingSize iPackingSize, Int32 iTypeSize, TypeBuilder enclosingType)
> at System.Reflection.Emit.ModuleBuilder.DefineTypeNoLock(String name, TypeAttributes attr, Type parent, Type[] interfaces)
> at System.Reflection.Emit.ModuleBuilder.DefineType(String name, TypeAttributes attr, Type parent, Type[] interfaces)
> at Castle.DynamicProxy.Builder.CodeBuilder.EasyType..ctor(ModuleScope modulescope, String name, Type baseType, Type[] interfaces, Boolean serializable)
> at Castle.DynamicProxy.Builder.CodeGenerators.BaseCodeGenerator.CreateTypeBuilder(String typeName, Type baseType, Type[] interfaces)
> at Castle.DynamicProxy.Builder.CodeGenerators.ClassProxyGenerator.GenerateCode(Type baseClass, Type[] interfaces)
> at Castle.DynamicProxy.Builder.DefaultProxyBuilder.CreateClassProxy(Type theClass, Type[] interfaces)
> at Castle.DynamicProxy.ProxyGenerator.CreateClassProxy(Type baseClass, Type[] interfaces, IInterceptor interceptor, Boolean checkAbstract, Object[] argumentsForConstructor)
> at NHibernate.Proxy.CastleProxyFactory.GetProxy(Object id, ISessionImplementor session)
> --- End of inner exception stack trace ---
> at NHibernate.Proxy.CastleProxyFactory.GetProxy(Object id, ISessionImplementor session)
> at NHibernate.Persister.Entity.AbstractEntityPersister.CreateProxy(Object id, ISessionImplementor session)
> at NHibernate.Impl.SessionImpl.DoLoadByClass(Type clazz, Object id, Boolean checkDeleted, Boolean allowProxyCreation)
> at NHibernate.Impl.SessionImpl.InternalLoad(Type clazz, Object id, Boolean isNullable)
> at NHibernate.Type.EntityType.ResolveIdentifier(Object id, ISessionImplementor session)
> at NHibernate.Type.EntityType.ResolveIdentifier(Object id, ISessionImplementor session, Object owner)
> at NHibernate.Impl.SessionImpl.InitializeEntity(Object obj)
> at NHibernate.Loader.Loader.InitializeEntitiesAndCollections(IList hydratedObjects, Object resultSetId, ISessionImplementor session)
> at NHibernate.Loader.Loader.DoQuery(ISessionImplementor session, QueryParameters queryParameters, Boolean returnProxies)
> at NHibernate.Loader.Loader.DoQueryAndInitializeNonLazyCollections(ISessionImplementor session, QueryParameters queryParameters, Boolean returnProxies)
> at NHibernate.Loader.Loader.DoList(ISessionImplementor session, QueryParameters queryParameters)
> at NHibernate.Loader.Loader.ListIgnoreQueryCache(ISessionImplementor session, QueryParameters queryParameters)
> at NHibernate.Loader.Loader.List(ISessionImplementor session, QueryParameters queryParameters, ISet querySpaces, IType[] resultTypes)
> at NHibernate.Loader.Criteria.CriteriaLoader.List(ISessionImplementor session)
> at NHibernate.Impl.SessionImpl.Find(CriteriaImpl criteria, IList results)
> at NHibernate.Impl.SessionImpl.Find(CriteriaImpl criteria)
> at NHibernate.Impl.CriteriaImpl.List()
> at NHibernate.Impl.CriteriaImpl.UniqueResult()
> at FullTilt.Tools.Services.ScheduledMessage.FTP.PersistentStorage.DataStore.GetScheduledMessageByMessageIndexInternal(Int64 messageIndex, Boolean fetchRelatedObjects, ISession session) in C:\Work\Code\FullTilt\Tools_TableSpam\Services\ScheduledMessage\ScheduledMessage.FTP\PersistentStorage\DataStore.cs:line 289
> at FullTilt.Tools.Services.ScheduledMessage.FTP.PersistentStorage.DataStore.DeleteScheduledMessageByMessageIndexInternal(Int64 messageIndex, ISession session) in C:\Work\Code\FullTilt\Tools_TableSpam\Services\ScheduledMessage\ScheduledMessage.FTP\PersistentStorage\DataStore.cs:line 259
> at FullTilt.Tools.Services.ScheduledMessage.FTP.PersistentStorage.DataStore.UpdateScheduledMessage(ScheduledMessageEntity newMessage, Int32 timeSpan) in C:\Work\Code\FullTilt\Tools_TableSpam\Services\ScheduledMessage\ScheduledMessage.FTP\PersistentStorage\DataStore.cs:line 219
> at TestConsoleApplication.Program.Update(Object obj) in C:\Work\Code\FullTilt\Tools_TableSpam\Services\ScheduledMessage\ScheduledMessage.FTP\TestConsoleApplication\Program.cs:line 219

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.nhibernate.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[nhibernate-issues] [JIRA] Commented: (NH-789) ORA-08177 not wrapped as StaleObjectException with Oracle.DataAcess

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-789?page=comments#action_14275 ]
     
Sergey Koshcheyev commented on NH-789:
--------------------------------------

I need to see more details, preferably a test case, and also what is the ORA-08177 exception?

> ORA-08177 not wrapped as StaleObjectException with Oracle.DataAcess
> -------------------------------------------------------------------
>
>          Key: NH-789
>          URL: http://jira.nhibernate.org/browse/NH-789
>      Project: NHibernate
>         Type: Bug
>   Components: Core
>     Versions: 1.0.2
>     Reporter: Johannes Schmidt

>
> The OracleClientDriver does not support milliseconds for Timestamp mapping. So, I decided to used OracleDataClientDriver. I'm using OptimisticLock settings in the mapping file. If there is a concurrency problem, I except a StaleObjectException, but the ADOExceptionReporter throws an exceptions that contains only the text of the Oracle exception for ORA-08177.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.nhibernate.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[nhibernate-issues] [JIRA] Created: (NH-789) ORA-08177 not wrapped as StaleObjectException with Oracle.DataAcess

[NHibernate J. <mik...@us...>]

ORA-08177 not wrapped as StaleObjectException with Oracle.DataAcess
-------------------------------------------------------------------

         Key: NH-789
         URL: http://jira.nhibernate.org/browse/NH-789
     Project: NHibernate
        Type: Bug
  Components: Core  
    Versions: 1.0.2    
    Reporter: Johannes Schmidt


The OracleClientDriver does not support milliseconds for Timestamp mapping. So, I decided to used OracleDataClientDriver. I'm using OptimisticLock settings in the mapping file. If there is a concurrency problem, I except a StaleObjectException, but the ADOExceptionReporter throws an exceptions that contains only the text of the Oracle exception for ORA-08177.



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.nhibernate.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[nhibernate-issues] [JIRA] Created: (NH-788) Incrementing a nullable <Version> field fails

[NHibernate J. <mik...@us...>]

Incrementing a nullable <Version> field fails
---------------------------------------------

         Key: NH-788
         URL: http://jira.nhibernate.org/browse/NH-788
     Project: NHibernate
        Type: Bug
  Components: Core  
    Versions: 1.2.0.Beta1    
    Reporter: Jens Dein
    Priority: Minor
 Attachments: Serialno.hbm.xml

I have defined my version tag like this : 

    <version
      name="Hbversion"                               
      column="HBVersion"                            
      type="System.Int32"                                  
      unsaved-value="null"    
    />

and in my class like this :

  private System.Int32? _hbversion;

and when trying to persist the code I get an error in the following code :

	public class Int32Type : ValueTypeType, IDiscriminatorType, IVersionType

		public virtual object Next( object current )
		{
			return ( ( int )current ) + 1;
		}

besause current is typecasted to int without checking for null. Code might be changed to the following :

	public virtual object Next( object current )
	{
            if (current == null)
                return Seed;
            else
                return ((int)current) + 1;
	}

I hope I havent misunderstood totally how to use these nullables, but I believe I found advise on the net stating that it should be possible to do it this way in the 1.2 version.

Using .NET 2.0 of course and SQL Server 2005.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.nhibernate.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[nhibernate-issues] [JIRA] Closed: (NH-571) class keyword in WHERE broken for table-per-subclass mappings

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-571?page=all ]
     
Sergey Koshcheyev closed NH-571:
--------------------------------

    Fix Version: 1.2.0.Beta1
     Resolution: Fixed

Fixed correctly this time.

> class keyword in WHERE broken for table-per-subclass mappings
> -------------------------------------------------------------
>
>          Key: NH-571
>          URL: http://jira.nhibernate.org/browse/NH-571
>      Project: NHibernate
>         Type: Bug
>   Components: Core
>     Versions: 1.0.2
>     Reporter: Symon
>      Fix For: 1.2.0.Beta1, 1.0.3, 1.2.0.Alpha1

>
> Classes mapped using table-per-subclass are not returned correctly when using the "class" keyword in an HQL statement.  The SQL statement generated contains a case statement in the WHERE clause with a discriminator allocated to each subclass, however the value allocated to the class name after the "class" keyword is not transformed into one of the subclasses - it appears to always return 0.
> See the forum thread http://forum.hibernate.org/viewtopic.php?t=957690&sid=ec894da91fc1bc0bbe0150a4e677f4f0 for further information.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.nhibernate.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[nhibernate-issues] [JIRA] Closed: (NH-719) Caching of "any" reference to lazy classes

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-719?page=all ]
     
Sergey Koshcheyev closed NH-719:
--------------------------------

    Resolution: Fixed

> Caching of "any" reference to lazy classes
> ------------------------------------------
>
>          Key: NH-719
>          URL: http://jira.nhibernate.org/browse/NH-719
>      Project: NHibernate
>         Type: Bug
>   Components: Core
>     Versions: 1.0.2, 1.2.0.Alpha1
>     Reporter: Cris Constantin
>      Fix For: 1.0.3, 1.2.0.Beta1
>  Attachments: NH719.patch, NH719.zip
>
> Consider these the mappings:
> <class name="C" lazy="false">
> 		<any name="Owner" id-type="Int32" meta-type="Char">
> 			<meta-value value="b" class="A"/>
> 			<meta-value value="a" class="B"/>
> 			<column name="OwnerType"/>
> 			<column name="OwnerID"/>
> 		</any>
> 		....
> </class>
> <class name="A" lazy="true"/>
> <class name="B" lazy="true"/>
> With all classes A, B, and C being cached.
> The stack trace while trying to load an object of class C from the cache
> ERROR NHibernate.Proxy.LazyInitializer [(null)] - Exception initializing proxy [C#1]
> NHibernate.MappingException: Unknown entity class: CProxyTypeA_INHibernateProxy1
>    at NHibernate.Impl.SessionFactoryImpl.GetPersister(Type theClass)
>    at NHibernate.Impl.SessionImpl.GetClassPersister(Type theClass)
>    at NHibernate.Impl.SessionImpl.DoLoadByClass(Type clazz, Object id, Boolean checkDeleted, Boolean allowProxyCreation)
>    at NHibernate.Impl.SessionImpl.Load(Type clazz, Object id)
>    at NHibernate.Type.ObjectType.Assemble(Object cached, ISessionImplementor session, Object owner)
>    at NHibernate.Impl.CacheEntry.Assemble(Object[] values, Object result, Object id, IClassPersister persister, IInterceptor interceptor, ISessionImplementor session)
>    at NHibernate.Impl.CacheEntry.Assemble(Object instance, Object id, IClassPersister persister, IInterceptor interceptor, ISessionImplementor session)
>    at NHibernate.Impl.SessionImpl.AssembleCacheEntry(CacheEntry entry, Object id, IClassPersister persister, Object optionalObject)
>    at NHibernate.Impl.SessionImpl.DoLoad(Type theClass, Object id, Object optionalObject, LockMode lockMode, Boolean checkDeleted)
>    at NHibernate.Impl.SessionImpl.ImmediateLoad(Type clazz, Object id)
>    at NHibernate.Proxy.LazyInitializer.Initialize()
>    at NHibernate.Proxy.LazyInitializer.InitializeWrapExceptions()

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.nhibernate.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[nhibernate-issues] [JIRA] Commented: (NH-719) Caching of "any" reference to lazy classes

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-719?page=comments#action_14273 ]
     
Sergey Koshcheyev commented on NH-719:
--------------------------------------

Actually, H3.2 changed the implementation recently to avoid initializing the proxy, so I'm going to follow them.

> Caching of "any" reference to lazy classes
> ------------------------------------------
>
>          Key: NH-719
>          URL: http://jira.nhibernate.org/browse/NH-719
>      Project: NHibernate
>         Type: Bug
>   Components: Core
>     Versions: 1.0.2, 1.2.0.Alpha1
>     Reporter: Cris Constantin
>      Fix For: 1.0.3, 1.2.0.Beta1
>  Attachments: NH719.patch, NH719.zip
>
> Consider these the mappings:
> <class name="C" lazy="false">
> 		<any name="Owner" id-type="Int32" meta-type="Char">
> 			<meta-value value="b" class="A"/>
> 			<meta-value value="a" class="B"/>
> 			<column name="OwnerType"/>
> 			<column name="OwnerID"/>
> 		</any>
> 		....
> </class>
> <class name="A" lazy="true"/>
> <class name="B" lazy="true"/>
> With all classes A, B, and C being cached.
> The stack trace while trying to load an object of class C from the cache
> ERROR NHibernate.Proxy.LazyInitializer [(null)] - Exception initializing proxy [C#1]
> NHibernate.MappingException: Unknown entity class: CProxyTypeA_INHibernateProxy1
>    at NHibernate.Impl.SessionFactoryImpl.GetPersister(Type theClass)
>    at NHibernate.Impl.SessionImpl.GetClassPersister(Type theClass)
>    at NHibernate.Impl.SessionImpl.DoLoadByClass(Type clazz, Object id, Boolean checkDeleted, Boolean allowProxyCreation)
>    at NHibernate.Impl.SessionImpl.Load(Type clazz, Object id)
>    at NHibernate.Type.ObjectType.Assemble(Object cached, ISessionImplementor session, Object owner)
>    at NHibernate.Impl.CacheEntry.Assemble(Object[] values, Object result, Object id, IClassPersister persister, IInterceptor interceptor, ISessionImplementor session)
>    at NHibernate.Impl.CacheEntry.Assemble(Object instance, Object id, IClassPersister persister, IInterceptor interceptor, ISessionImplementor session)
>    at NHibernate.Impl.SessionImpl.AssembleCacheEntry(CacheEntry entry, Object id, IClassPersister persister, Object optionalObject)
>    at NHibernate.Impl.SessionImpl.DoLoad(Type theClass, Object id, Object optionalObject, LockMode lockMode, Boolean checkDeleted)
>    at NHibernate.Impl.SessionImpl.ImmediateLoad(Type clazz, Object id)
>    at NHibernate.Proxy.LazyInitializer.Initialize()
>    at NHibernate.Proxy.LazyInitializer.InitializeWrapExceptions()

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.nhibernate.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[nhibernate-issues] [JIRA] Closed: (NH-540) Register of AnsiChar type

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-540?page=3Dall ]
    =20
Sergey Koshcheyev closed NH-540:
--------------------------------

    Resolution: Fixed

> Register of AnsiChar type
> -------------------------
>
>          Key: NH-540
>          URL: http://jira.nhibernate.org/browse/NH-540
>      Project: NHibernate
>         Type: Bug
>   Components: Core
>     Versions: 1.0.2
>     Reporter: Andr=C3=A9 Luiz
>     Priority: Minor
>      Fix For: 1.0.3, 1.2.0.Alpha1
>  Attachments: TestCase.zip
>
> I had solicited in NH-493 in the creation of an AnsiChar type that would =
permit work with character parameters in a Oracle Database behavior. This t=
ype was created in the 1.0.2 but it's register was not made by the TypeFact=
ory class of NHibernate. I would like to receive the solution to this issue=
 as fast as you can because my project it's stopped only waiting this solut=
ion to be deployed.

--=20
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.nhibernate.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[nhibernate-issues] [JIRA] Closed: (NH-574) sort="natural" doen't work when namespace and assemply were set

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-574?page=all ]
     
Sergey Koshcheyev closed NH-574:
--------------------------------

    Resolution: Fixed

> sort="natural" doen't work when namespace and assemply were set
> ---------------------------------------------------------------
>
>          Key: NH-574
>          URL: http://jira.nhibernate.org/browse/NH-574
>      Project: NHibernate
>         Type: Bug
>   Components: Core
>     Versions: 1.0.2
>     Reporter: Kailuo Wang
>     Priority: Minor
>      Fix For: 1.0.3, 1.2.0.Alpha1

>
> In the mapping file, I set the sort attribute of a set as "natural", I also set the namespace and assembly property of the class as "SampleNameSpace.Impl" and "SampleAssemly". 
> The NHibernate thrown an Exception saying that it cannot instantiate the IComparer SampleNameSpace.Impl.natural, SampleAssembly".
> I removed the namespace and assemply propertis from the class (manually add that namespace and assembly for every class attribute. It works. 
> I think Nhibernate should recognize the natural as the sort attribute no matter the namespace and assembly attributes of the class were set or not. 
> here is the sample with which I got the error. 
> <hibernate-mapping xmlns="urn:nhibernate-mapping-2.0" schema="dbo" >
>   <class name="Campaign" table="tbl_Campaign" namespace="MindHarbor.mmpulse.Domain.Impl" 
> asembly=" MindHarbor.mmpulse" >
>     <id name="Id" type="Int32" column="Id">
>       <generator class="identity" />
>     </id>
>     <set name="blasts" access="field"  inverse="true" sort="natural"  lazy="true">
>       <key column="Campaign_Id" />
>       <one-to-many class="Blast" />
>     </set>
>   </class>
> </hibernate-mapping>

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.nhibernate.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[nhibernate-issues] [JIRA] Closed: (NH-563) Exception in NDataReader.cs when loading BinaryBlob

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-563?page=all ]
     
Sergey Koshcheyev closed NH-563:
--------------------------------

    Resolution: Fixed

> Exception in NDataReader.cs when loading BinaryBlob
> ---------------------------------------------------
>
>          Key: NH-563
>          URL: http://jira.nhibernate.org/browse/NH-563
>      Project: NHibernate
>         Type: Bug
>   Components: Core
>     Versions: 1.0.2
>     Reporter: Marco Lucio
>     Priority: Minor
>      Fix For: 1.0.3, 1.2.0.Alpha1
>  Attachments: NDataReader.cs
>
> An ArgumentNullException is thrown when trying to inizialize a collection of persistent objects when collection objects contains a BinaryBlob property.
> The exception is generated in the file Driver\NDataReader.cs because GetBytes function doesn't handle buffer == null argument correctly.
> The attachment file contains my patched version of the file.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.nhibernate.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[nhibernate-issues] [JIRA] Closed: (NH-661) SysCache throws an NullReferenceException when clearing cache region

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-661?page=all ]
     
Sergey Koshcheyev closed NH-661:
--------------------------------

    Resolution: Fixed

Should be fixed since we moved away from using a map to using a root cache key which all others depend on.

> SysCache throws an NullReferenceException when clearing cache region
> --------------------------------------------------------------------
>
>          Key: NH-661
>          URL: http://jira.nhibernate.org/browse/NH-661
>      Project: NHibernate
>         Type: Bug
>   Components: Contrib
>     Versions: 1.0.2
>     Reporter: Martijn Boland
>     Priority: Minor
>      Fix For: 1.0.3

>
> Seen in a production environment: after a while SysCache starts to throw nullreference exceptions when clearing cache regions:
> 2006-06-20 11:03:51,390 [3768] ERROR Cuyahoga.Web.Admin.NodeEdit [(null)] <(null)> - Error saving Node
> System.NullReferenceException: Object reference not set to an instance of an object.
>    at NHibernate.Caches.SysCache.SysCache.Clear()
>    at NHibernate.Cache.StandardQueryCache.Clear()
>    at NHibernate.Impl.SessionFactoryImpl.EvictQueries(String cacheRegion)
>    at Cuyahoga.Core.Service.CoreRepository.ClearQueryCache(String cacheRegion)
>    at Cuyahoga.Web.Admin.NodeEdit.SaveNode()
>    at Cuyahoga.Web.Admin.NodeEdit.btnSave_Click(Object sender, EventArgs e)
> Restarting the ASP.NET process solves the issue. 
> I'm aware that this is not a very detailed issue description, but unfortunately, I haven't been able to reproduce this in a non-production environment.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.nhibernate.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[nhibernate-issues] [JIRA] Closed: (NH-582) All IType implementations should be serializable

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-582?page=all ]
     
Sergey Koshcheyev closed NH-582:
--------------------------------

    Resolution: Fixed

> All IType implementations should be serializable
> ------------------------------------------------
>
>          Key: NH-582
>          URL: http://jira.nhibernate.org/browse/NH-582
>      Project: NHibernate
>         Type: Bug
>   Components: Core
>     Versions: 1.0.2
>     Reporter: Sergey Koshcheyev
>     Priority: Trivial
>      Fix For: 1.0.3, 1.2.0.Alpha1

>
> Every class that implements IType directly or indirectly should be marked [Serializable]. Need to remember about this for future types and UserTypes distributed with NHibernate as well.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.nhibernate.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[nhibernate-issues] [JIRA] Closed: (NH-552) Collection of "nullifiables" not updated when object saved back

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-552?page=all ]
     
Sergey Koshcheyev closed NH-552:
--------------------------------

    Resolution: Fixed

> Collection of "nullifiables" not updated when object saved back
> ---------------------------------------------------------------
>
>          Key: NH-552
>          URL: http://jira.nhibernate.org/browse/NH-552
>      Project: NHibernate
>         Type: Bug
>   Components: Core
>     Versions: 1.0.2
>     Reporter: Alexis Seigneurin
>     Priority: Trivial
>      Fix For: 1.0.3, 1.2.0.Alpha1

>
> In the SessionImpl class, the collection named "nullifiables" keeps track of objects which have been deleted. If, for a reason or another, we decide to save such an object back in the database, this object is still considered "nullifiable". The impact is that any reference to that object will be set to "null".
> In the application we are developping, all the generators are of type "assigned". This is because the objects are loaded from a remote location which is responsible for the generation of the identifiers. Each object can be saved and deleted more than once by NHibernate. It is therefore important to remove an object from the "nullifiables" collection when it is saved back.
> Here are two mappings ("Question" and "Answer") :
>   <class name="Question" table="QUESTION">
>     <id name="Id" type="long">
>       <generator class="assigned"/>
>     </id>
>     <set name="Answers" inverse="true" lazy="true" access="NHibernate.Generics.GenericAccessor, NHibernate.Generics">
>       <key column="Question"/>
>       <one-to-many class="Answer"/>
>     </set>
>   </class>
>   <class name="Answer" table="ANSWER">
>     <id name="Id" type="long">
>       <generator class="assigned"/>
>     </id>
>     <many-to-one name="Question" not-null="true" access="NHibernate.Generics.GenericAccessor, NHibernate.Generics"/>
>   </class>
> Each Answer belongs to a single Question. Each Question contains one or more Answers.
> To reproduce the bug, you need to:
>     - save a Question (with ID=1) (let's say it has no linked Answers, at this point)
>     - delete the Question (ID=1)
>     - save the Question once again (ID=1)
>     - save an Answer linked to the Question => the linked property (Question in the Answer instance) is "nullified" and the not-null constraint gets violated.
> Here is a patch:
> $ diff -C 5 SessionImpl.orig.cs  SessionImpl.cs
> *** SessionImpl.orig.cs Mon Feb 27 18:29:02 2006
> --- SessionImpl.cs      Mon Feb 27 18:30:01 2006
> ***************
> *** 709,718 ****
> --- 709,722 ----
>                                 }
>                         }
>                         //id might be generated by SQL insert
>                         object id = SaveWithGeneratedIdentifier( theObj, Cascades.CascadingAction.ActionSaveUpdate, null );
> +
> +             IClassPersister persister = GetPersister(theObj);
> +             nullifiables.Remove(new Key(id, persister));
> +
>                         ReassociateProxy( obj, id );
>                         return id;
>                 }
>                 private void ForceFlush( EntityEntry e )

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.nhibernate.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[nhibernate-issues] [JIRA] Closed: (NH-544) Small Issue about Iesi.Collection.Set

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-544?page=all ]
     
Sergey Koshcheyev closed NH-544:
--------------------------------

    Fix Version:     (was: 1.0.3)
     Resolution: Fixed

Won't fix in 1.0.3 since it's not that important.

> Small Issue about Iesi.Collection.Set
> -------------------------------------
>
>          Key: NH-544
>          URL: http://jira.nhibernate.org/browse/NH-544
>      Project: NHibernate
>         Type: Bug
>   Components: Core
>     Versions: 1.0.2
>     Reporter: Kailuo Wang
>     Priority: Trivial
>      Fix For: 1.2.0.Alpha1
>  Attachments: Set.cs.rar
>
> In the set class, the method ExclusiveOr was writen as follow
> public static ISet ExclusiveOr(ISet a, ISet b)
> {
> if(a == null && b == null)
> return null;
> else if(a == null)
> return (Set)b.Clone();
> else if(b == null)
> return (Set)a.Clone();
> else
> return a.ExclusiveOr(b);
> }
> Note that the clones of a and b were uneccessarily down cast to Set, while in the Union method of this class, these two clones are down cast to ISet. Although this won't affect any current usage, but for people who wants to have their own implementations of ISet ( an example[^]), this could be a problem.
> I did try modify the code to
> return (ISet)b.Clone();
> ...
> return (ISet)a.Clone();
> And all the Unit Tests from Nhibernate were passed
> Attached is the modified Set.cs, these two lines are the only change from the original one

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.nhibernate.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[nhibernate-issues] [JIRA] Commented: (NH-784) NHibernate should throw exception on failed driver load

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-784?page=comments#action_14270 ]
     
Sergey Koshcheyev commented on NH-784:
--------------------------------------

Another one:
- Do not make any connection provider the default and complain if it was not set.

> NHibernate should throw exception on failed driver load
> -------------------------------------------------------
>
>          Key: NH-784
>          URL: http://jira.nhibernate.org/browse/NH-784
>      Project: NHibernate
>         Type: Improvement
>   Components: Data Providers
>     Reporter: Al Twohill
>     Priority: Trivial

>
> For full background on where this issue arises from, see http://forum.hibernate.org/viewtopic.php?t=966582&highlight=
> When Configuration.Configure() is called, if NHibernate is unable to load a database driver for whatever reason (missing dll, incorrect hibernate.cfg.xml, etc) it falls back to returning a UserSuppliedConnectionProvider without an ADO.Net connection attached to it. This causes any use of Session (eg accessing database) to throw an exception. This is extremely difficult to debug, as there is absolutely no indication as to why a UserSuppliedConnectionProvider is returned.
> I propose that instead of returning a UserSuppliedConnectionProvider, NHibernate should throw an exception along the lines of "Cannot Load Driver", and give a reason why.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.nhibernate.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[nhibernate-issues] [JIRA] Commented: (NH-784) NHibernate should throw exception on failed driver load

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-784?page=comments#action_14263 ]
     
Fabio Maulo commented on NH-784:
--------------------------------

One more option.

- Change the nhibernate-configuration.xsd

> NHibernate should throw exception on failed driver load
> -------------------------------------------------------
>
>          Key: NH-784
>          URL: http://jira.nhibernate.org/browse/NH-784
>      Project: NHibernate
>         Type: Improvement
>   Components: Data Providers
>     Reporter: Al Twohill
>     Priority: Trivial

>
> For full background on where this issue arises from, see http://forum.hibernate.org/viewtopic.php?t=966582&highlight=
> When Configuration.Configure() is called, if NHibernate is unable to load a database driver for whatever reason (missing dll, incorrect hibernate.cfg.xml, etc) it falls back to returning a UserSuppliedConnectionProvider without an ADO.Net connection attached to it. This causes any use of Session (eg accessing database) to throw an exception. This is extremely difficult to debug, as there is absolutely no indication as to why a UserSuppliedConnectionProvider is returned.
> I propose that instead of returning a UserSuppliedConnectionProvider, NHibernate should throw an exception along the lines of "Cannot Load Driver", and give a reason why.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.nhibernate.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[nhibernate-issues] [JIRA] Commented: (NH-784) NHibernate should throw exception on failed driver load

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-784?page=comments#action_14262 ]
     
Fabio Maulo commented on NH-784:
--------------------------------

Until now NHb work like Hibernate using UserSuppliedConnectionProvider.
The possible solutions, i see, are:
- Make DriverConnectionProvider default if no connection.provider is specified in the mapping until DriverConnectionProvider is the unique provider of NHb.
- Change the exception of UserSuppliedConnectionProvider adding "Config connection.provider property was not specified".
- Exception if an unknown property was found in session-factory section.

I think the last option is the best to prevent typing error.


> NHibernate should throw exception on failed driver load
> -------------------------------------------------------
>
>          Key: NH-784
>          URL: http://jira.nhibernate.org/browse/NH-784
>      Project: NHibernate
>         Type: Improvement
>   Components: Data Providers
>     Reporter: Al Twohill
>     Priority: Trivial

>
> For full background on where this issue arises from, see http://forum.hibernate.org/viewtopic.php?t=966582&highlight=
> When Configuration.Configure() is called, if NHibernate is unable to load a database driver for whatever reason (missing dll, incorrect hibernate.cfg.xml, etc) it falls back to returning a UserSuppliedConnectionProvider without an ADO.Net connection attached to it. This causes any use of Session (eg accessing database) to throw an exception. This is extremely difficult to debug, as there is absolutely no indication as to why a UserSuppliedConnectionProvider is returned.
> I propose that instead of returning a UserSuppliedConnectionProvider, NHibernate should throw an exception along the lines of "Cannot Load Driver", and give a reason why.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.nhibernate.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[nhibernate-issues] [JIRA] Closed: (NH-787) IQuery.SetParameterList() - Malformed SQL

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-787?page=all ]
     
Sergey Koshcheyev closed NH-787:
--------------------------------

    Resolution: Not an Issue

Use "in (:parameter)".

> IQuery.SetParameterList() - Malformed SQL
> -----------------------------------------
>
>          Key: NH-787
>          URL: http://jira.nhibernate.org/browse/NH-787
>      Project: NHibernate
>         Type: Bug
>   Components: Core
>     Versions: 1.0.2
>     Reporter: Steve Guidi

>
> I have discovered the following issue using nHibernate 1.0.2 with SQL Server 2000.
> IList mappedObjectCollection = session.CreateCriteria(typeof(T)).List();
> session.CreateQuery("from T t where t in :objectsToLoad")
> .SetParameterList("objectsToLoad", mappedObjectCollection, NHibernateUtil.Entity(typeof(T)))
> .List();
> The mapping of the T class uses the GUID generator for its primary key, mapped to a property called "Key". When I execute the code with the SetParameterList directive, I notice that the generated SQL is incorrect (see below). I've replaced the selected columns of the T with '*' class for brevity.
> The generated SQL (show_sql=true):
> exec sp_executesql
> N'select * from T t0_ where (t0_.Key in @p0 , @p1 , @p2)',
> N'@p0 uniqueidentifier,@p1 uniqueidentifier,@p2 uniqueidentifier',
> @p0 = 'F44B4D98-311C-4800-B600-9C7499C7AF22',
> @p1 = '36FFAC14-61F7-4673-985C-7DF8BE21D9AC',
> @p2 = 'A7EBCDB0-36C2-48D3-B8DD-9CE56568BD56'
> Note the first parenthesis in the where clause -- it is in the wrong location. The parenthesis should be between the 'in' directive and the first parameter.
> I initially reported this issue via the nHibernate Community forum: http://forum.hibernate.org/viewtopic.php?t=966687.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.nhibernate.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[nhibernate-issues] [JIRA] Created: (NH-787) IQuery.SetParameterList() - Malformed SQL

[NHibernate J. <mik...@us...>]

IQuery.SetParameterList() - Malformed SQL
-----------------------------------------

         Key: NH-787
         URL: http://jira.nhibernate.org/browse/NH-787
     Project: NHibernate
        Type: Bug
  Components: Core  
    Versions: 1.0.2    
    Reporter: Steve Guidi


I have discovered the following issue using nHibernate 1.0.2 with SQL Server 2000.


IList mappedObjectCollection = session.CreateCriteria(typeof(T)).List();

session.CreateQuery("from T t where t in :objectsToLoad")
.SetParameterList("objectsToLoad", mappedObjectCollection, NHibernateUtil.Entity(typeof(T)))
.List();


The mapping of the T class uses the GUID generator for its primary key, mapped to a property called "Key". When I execute the code with the SetParameterList directive, I notice that the generated SQL is incorrect (see below). I've replaced the selected columns of the T with '*' class for brevity.

The generated SQL (show_sql=true):

exec sp_executesql
N'select * from T t0_ where (t0_.Key in @p0 , @p1 , @p2)',
N'@p0 uniqueidentifier,@p1 uniqueidentifier,@p2 uniqueidentifier',
@p0 = 'F44B4D98-311C-4800-B600-9C7499C7AF22',
@p1 = '36FFAC14-61F7-4673-985C-7DF8BE21D9AC',
@p2 = 'A7EBCDB0-36C2-48D3-B8DD-9CE56568BD56'


Note the first parenthesis in the where clause -- it is in the wrong location. The parenthesis should be between the 'in' directive and the first parameter.

I initially reported this issue via the nHibernate Community forum: http://forum.hibernate.org/viewtopic.php?t=966687.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.nhibernate.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[nhibernate-issues] [JIRA] Resolved: (NH-515) Port subselect fetching from Hibernate 3.1

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-515?page=all ]
     
Sergey Koshcheyev resolved NH-515:
----------------------------------

    Resolution: Fixed

> Port subselect fetching from Hibernate 3.1
> ------------------------------------------
>
>          Key: NH-515
>          URL: http://jira.nhibernate.org/browse/NH-515
>      Project: NHibernate
>         Type: New Feature
>   Components: Core
>     Reporter: Sergey Koshcheyev
>     Assignee: Sergey Koshcheyev
>      Fix For: 1.2.0.Beta2

>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.nhibernate.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[nhibernate-issues] [JIRA] Created: (NH-786) Port statistics from H3

[NHibernate J. <mik...@us...>]

Port statistics from H3
-----------------------

         Key: NH-786
         URL: http://jira.nhibernate.org/browse/NH-786
     Project: NHibernate
        Type: New Feature
  Components: Core  
    Reporter: Sergey Koshcheyev
    Priority: Trivial
     Fix For: 1.2.0.Beta2




-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.nhibernate.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[nhibernate-issues] [JIRA] Work started: (NH-515) Port subselect fetching from Hibernate 3.1

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-515?page=all ]
     
Work on NH-515 started by Sergey Koshcheyev

> Port subselect fetching from Hibernate 3.1
> ------------------------------------------
>
>          Key: NH-515
>          URL: http://jira.nhibernate.org/browse/NH-515
>      Project: NHibernate
>         Type: New Feature
>   Components: Core
>     Reporter: Sergey Koshcheyev
>     Assignee: Sergey Koshcheyev
>      Fix For: 1.2.0.Beta2

>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.nhibernate.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira