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

[nhibernate-issues] [JIRA] Commented: (NH-860) Performant count of HQL query

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

     [ http://jira.nhibernate.org/browse/NH-860?page=comments#action_14781 ]
     
Luis Ferreira commented on NH-860:
----------------------------------

What you're saying is doing something like

            Dim q2 As IQuery = Session.CreateQuery("select count(*) from (" & q1.QueryString & ")")

But how can I pass the parameter list?

            q2.SetParameterList(????? how can I set them ?????)

As far as I can tell I have access to q1's named parameter NAMES, not the values.

> Performant count of HQL query
> -----------------------------
>
>          Key: NH-860
>          URL: http://jira.nhibernate.org/browse/NH-860
>      Project: NHibernate
>         Type: Improvement
>   Components: Core
>     Versions: 1.2.0.Beta3
>     Reporter: Luis Ferreira

>
> We are implementing pagination in our Web Project and we'd like to have a way of calculating the count(*) for each of the HQL queries we have already implemented *without writing specific queries for that* AND *without returning the results as a list* and then getting its count property.
> A member of the team has attempted, with some success, to use NHibernate to
> generate the SQL for our HQL queries and then wrapping it with a select
> count(*) from (<generated SQL>). But to do that we have had to use
> Reflection to access protected methods, and filling query parameters for
> parametrized queries is still a problem. To really tackle the issue it would
> be necessary to have some changes in NHibernate, namely public exposure in
> IQuery of methods in AbstractQueryImpl / QueryImpl regarding access to named
> parameters names and values.
> Of course a really great solution would be for NHibernate to provide that
> count(*) funcionality (in a way similar to what has been done with
> projections for ICriteria? haven't used that much, we've got really hairy
> queries to write). It seems to be an issue for a lot of people. For
> databases that support subquerying it wouldn't be too difficult to
> implement I guess, but maybe the team doesn't want to impose that kind of
> restrictions.

-- 
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-860) Performant count of HQL query

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

     [ http://jira.nhibernate.org/browse/NH-860?page=comments#action_14780 ]
     
Ayende Rahien commented on NH-860:
----------------------------------

Any particular reason you can just do:

select count(*) from (HQL Query) ??

> Performant count of HQL query
> -----------------------------
>
>          Key: NH-860
>          URL: http://jira.nhibernate.org/browse/NH-860
>      Project: NHibernate
>         Type: Improvement
>   Components: Core
>     Versions: 1.2.0.Beta3
>     Reporter: Luis Ferreira

>
> We are implementing pagination in our Web Project and we'd like to have a way of calculating the count(*) for each of the HQL queries we have already implemented *without writing specific queries for that* AND *without returning the results as a list* and then getting its count property.
> A member of the team has attempted, with some success, to use NHibernate to
> generate the SQL for our HQL queries and then wrapping it with a select
> count(*) from (<generated SQL>). But to do that we have had to use
> Reflection to access protected methods, and filling query parameters for
> parametrized queries is still a problem. To really tackle the issue it would
> be necessary to have some changes in NHibernate, namely public exposure in
> IQuery of methods in AbstractQueryImpl / QueryImpl regarding access to named
> parameters names and values.
> Of course a really great solution would be for NHibernate to provide that
> count(*) funcionality (in a way similar to what has been done with
> projections for ICriteria? haven't used that much, we've got really hairy
> queries to write). It seems to be an issue for a lot of people. For
> databases that support subquerying it wouldn't be too difficult to
> implement I guess, but maybe the team doesn't want to impose that kind of
> restrictions.

-- 
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-860) Performant count of HQL query

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

Performant count of HQL query
-----------------------------

         Key: NH-860
         URL: http://jira.nhibernate.org/browse/NH-860
     Project: NHibernate
        Type: Improvement
  Components: Core  
    Versions: 1.2.0.Beta3    
    Reporter: Luis Ferreira


We are implementing pagination in our Web Project and we'd like to have a way of calculating the count(*) for each of the HQL queries we have already implemented *without writing specific queries for that* AND *without returning the results as a list* and then getting its count property.

A member of the team has attempted, with some success, to use NHibernate to
generate the SQL for our HQL queries and then wrapping it with a select
count(*) from (<generated SQL>). But to do that we have had to use
Reflection to access protected methods, and filling query parameters for
parametrized queries is still a problem. To really tackle the issue it would
be necessary to have some changes in NHibernate, namely public exposure in
IQuery of methods in AbstractQueryImpl / QueryImpl regarding access to named
parameters names and values.

Of course a really great solution would be for NHibernate to provide that
count(*) funcionality (in a way similar to what has been done with
projections for ICriteria? haven't used that much, we've got really hairy
queries to write). It seems to be an issue for a lot of people. For
databases that support subquerying it wouldn't be too difficult to
implement I guess, but maybe the team doesn't want to impose that kind of
restrictions.


-- 
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-633) Add support for generic collections to hbm2net

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

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

Harun Vos updated NH-633:
-------------------------

    Attachment: Generic-and-VirtualProperties.zip

I needed this feature, so I've written a patch.
I'm new to NHibernate and C#, this is pretty messy and I don't think it's ready for the mainline, but I thought I'd better post it before it becomes obsolete ;)

It was originally made against 1.2beta2, but has also been tested against 1.2beta3.

It can handle collections of mapped entities, and of values (<element> tag).
Currently, it supports IList<type> and ISet<type>, but it won't handle IDictionary<key,type> - it will ignore requests to make a generic map.
I'm not sure about bag & idbag - YMMV.
I don't know how it interacts with sorted collections.
I have included some fairly skeletal unit tests.

This patch also adds virtual property support for proxyable classes - this is another matter entirely, not part of the generics support.

To use it, add a generic="true" attribute to your collection tag.

Good luck :)


> Add support for generic collections to hbm2net
> ----------------------------------------------
>
>          Key: NH-633
>          URL: http://jira.nhibernate.org/browse/NH-633
>      Project: NHibernate
>         Type: Improvement
>   Components: Toolset
>     Versions: 1.2.0.Alpha1
>     Reporter: Sergey Koshcheyev
>     Priority: Trivial
>      Fix For: LATER
>  Attachments: Generic-and-VirtualProperties.zip
>
> Postponed.

-- 
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-716) Dirty Checking exception (many-to-one, select-before-update)

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

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

A workaround would be for you to recompile NHibernate with the fix until I fix it officially in 1.0.4.

> Dirty Checking exception (many-to-one, select-before-update)
> ------------------------------------------------------------
>
>          Key: NH-716
>          URL: http://jira.nhibernate.org/browse/NH-716
>      Project: NHibernate
>         Type: Bug
>   Components: Core
>     Versions: 1.2.0.Alpha1
>     Reporter: Sasha Borodin
>      Fix For: 1.0.4, 1.2.0.Beta2

>
> This problem can be reproduced by flushing a session with an entity which contains a "many-to-one" property, but only when the "select-before-update" option is turned on for that class (and performed).
> The problem occurs during the "dirty checking", in the EntityType.GetIdentifier. This is because that method is called on a variable which is already a String identifier itself, in ManyToOneType.IsModified. And i believe that THIS is because the "old" and "current" parameters passed to this class by TypeFactory.FindModified are reversed ("x" and "y"), so that EntityType.GetIdentifier is attempting to resolve the id on the wrong variable.
> Full stack trace of any exception that occurs:
> NHibernate.MappingException was unhandled by user code
> Message="Unknown entity class: System.String"
> Source="NHibernate"
> StackTrace:
> at NHibernate.Impl.SessionFactoryImpl.GetEntityPersister(Type theClass) in c:\net\nhibernate\nhibernate\src\NHibernate\Impl\SessionFactoryImpl.cs:line 563
> at NHibernate.Impl.SessionImpl.GetClassPersister(Type theClass) in c:\net\nhibernate\nhibernate\src\NHibernate\Impl\SessionImpl.cs:line 3489
> at NHibernate.Impl.SessionImpl.GetEntityPersister(Object obj) in c:\net\nhibernate\nhibernate\src\NHibernate\Impl\SessionImpl.cs:line 3497
> at NHibernate.Impl.SessionImpl.GetEntityIdentifierIfNotUnsaved(Object obj) in c:\net\nhibernate\nhibernate\src\NHibernate\Impl\SessionImpl.cs:line 3613
> at NHibernate.Type.EntityType.GetIdentifier(Object value, ISessionImplementor session) in c:\net\nhibernate\nhibernate\src\NHibernate\Type\EntityType.cs:line 60
> at NHibernate.Type.ManyToOneType.IsModified(Object old, Object current, Boolean[] checkable, ISessionImplementor session) in c:\net\nhibernate\nhibernate\src\NHibernate\Type\ManyToOneType.cs:line 112
> at NHibernate.Type.TypeFactory.FindModified(StandardProperty[] properties, Object[] x, Object[] y, Boolean[][] includeColumns, Boolean anyUninitializedProperties, ISessionImplementor session) in c:\net\nhibernate\nhibernate\src\NHibernate\Type\TypeFactory.cs:line 988
> at NHibernate.Persister.Entity.AbstractEntityPersister.FindModified(Object[] old, Object[] current, Object obj, ISessionImplementor session) in c:\net\nhibernate\nhibernate\src\NHibernate\Persister\Entity\AbstractEntityPersister.cs:line 311
> at NHibernate.Impl.SessionImpl.FlushEntity(Object obj, EntityEntry entry) in c:\net\nhibernate\nhibernate\src\NHibernate\Impl\SessionImpl.cs:line 3263
> at NHibernate.Impl.SessionImpl.FlushEntities() in c:\net\nhibernate\nhibernate\src\NHibernate\Impl\SessionImpl.cs:line 3200
> at NHibernate.Impl.SessionImpl.FlushEverything() in c:\net\nhibernate\nhibernate\src\NHibernate\Impl\SessionImpl.cs:line 2953
> at NHibernate.Impl.SessionImpl.Flush() in c:\net\nhibernate\nhibernate\src\NHibernate\Impl\SessionImpl.cs:line 2929
> at NHibernate.Transaction.AdoTransaction.Commit() in c:\net\nhibernate\nhibernate\src\NHibernate\Transaction\AdoTransaction.cs:line 141
> at DFWHC.GroupOne.GoRes.business.DivisionFactory.UpdateDivision(Division division) in C:\Development\dfw_hospital\GroupOne\GoRes\library\business\DivisionFactory.cs:line 72
> at EditDivision.Update(Object src, EventArgs args) in c:\Development\dfw_hospital\GroupOne\GoRes\website\user\employee\admin\EditDivision.aspx.cs:line 135
> at System.Web.UI.WebControls.Button.OnClick(EventArgs e)
> at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)
> at System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument)
> at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
> at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
> at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
> I think that I was able to solve the issue by making a small change in TypeFactory.FindModified(), line 991. By reordering the parameters correctly in TypeFactory.FindModified (swapping "x" and "y" around), the framework now resolves the id of the correct (entity) variable. But I am not familiar with the process of creating a patch.
> Thank you for looking into this.

-- 
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-716) Dirty Checking exception (many-to-one, select-before-update)

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

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

Sergey Koshcheyev updated NH-716:
---------------------------------

    Fix Version: 1.0.4

> Dirty Checking exception (many-to-one, select-before-update)
> ------------------------------------------------------------
>
>          Key: NH-716
>          URL: http://jira.nhibernate.org/browse/NH-716
>      Project: NHibernate
>         Type: Bug
>   Components: Core
>     Versions: 1.2.0.Alpha1
>     Reporter: Sasha Borodin
>      Fix For: 1.0.4, 1.2.0.Beta2

>
> This problem can be reproduced by flushing a session with an entity which contains a "many-to-one" property, but only when the "select-before-update" option is turned on for that class (and performed).
> The problem occurs during the "dirty checking", in the EntityType.GetIdentifier. This is because that method is called on a variable which is already a String identifier itself, in ManyToOneType.IsModified. And i believe that THIS is because the "old" and "current" parameters passed to this class by TypeFactory.FindModified are reversed ("x" and "y"), so that EntityType.GetIdentifier is attempting to resolve the id on the wrong variable.
> Full stack trace of any exception that occurs:
> NHibernate.MappingException was unhandled by user code
> Message="Unknown entity class: System.String"
> Source="NHibernate"
> StackTrace:
> at NHibernate.Impl.SessionFactoryImpl.GetEntityPersister(Type theClass) in c:\net\nhibernate\nhibernate\src\NHibernate\Impl\SessionFactoryImpl.cs:line 563
> at NHibernate.Impl.SessionImpl.GetClassPersister(Type theClass) in c:\net\nhibernate\nhibernate\src\NHibernate\Impl\SessionImpl.cs:line 3489
> at NHibernate.Impl.SessionImpl.GetEntityPersister(Object obj) in c:\net\nhibernate\nhibernate\src\NHibernate\Impl\SessionImpl.cs:line 3497
> at NHibernate.Impl.SessionImpl.GetEntityIdentifierIfNotUnsaved(Object obj) in c:\net\nhibernate\nhibernate\src\NHibernate\Impl\SessionImpl.cs:line 3613
> at NHibernate.Type.EntityType.GetIdentifier(Object value, ISessionImplementor session) in c:\net\nhibernate\nhibernate\src\NHibernate\Type\EntityType.cs:line 60
> at NHibernate.Type.ManyToOneType.IsModified(Object old, Object current, Boolean[] checkable, ISessionImplementor session) in c:\net\nhibernate\nhibernate\src\NHibernate\Type\ManyToOneType.cs:line 112
> at NHibernate.Type.TypeFactory.FindModified(StandardProperty[] properties, Object[] x, Object[] y, Boolean[][] includeColumns, Boolean anyUninitializedProperties, ISessionImplementor session) in c:\net\nhibernate\nhibernate\src\NHibernate\Type\TypeFactory.cs:line 988
> at NHibernate.Persister.Entity.AbstractEntityPersister.FindModified(Object[] old, Object[] current, Object obj, ISessionImplementor session) in c:\net\nhibernate\nhibernate\src\NHibernate\Persister\Entity\AbstractEntityPersister.cs:line 311
> at NHibernate.Impl.SessionImpl.FlushEntity(Object obj, EntityEntry entry) in c:\net\nhibernate\nhibernate\src\NHibernate\Impl\SessionImpl.cs:line 3263
> at NHibernate.Impl.SessionImpl.FlushEntities() in c:\net\nhibernate\nhibernate\src\NHibernate\Impl\SessionImpl.cs:line 3200
> at NHibernate.Impl.SessionImpl.FlushEverything() in c:\net\nhibernate\nhibernate\src\NHibernate\Impl\SessionImpl.cs:line 2953
> at NHibernate.Impl.SessionImpl.Flush() in c:\net\nhibernate\nhibernate\src\NHibernate\Impl\SessionImpl.cs:line 2929
> at NHibernate.Transaction.AdoTransaction.Commit() in c:\net\nhibernate\nhibernate\src\NHibernate\Transaction\AdoTransaction.cs:line 141
> at DFWHC.GroupOne.GoRes.business.DivisionFactory.UpdateDivision(Division division) in C:\Development\dfw_hospital\GroupOne\GoRes\library\business\DivisionFactory.cs:line 72
> at EditDivision.Update(Object src, EventArgs args) in c:\Development\dfw_hospital\GroupOne\GoRes\website\user\employee\admin\EditDivision.aspx.cs:line 135
> at System.Web.UI.WebControls.Button.OnClick(EventArgs e)
> at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)
> at System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument)
> at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
> at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
> at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
> I think that I was able to solve the issue by making a small change in TypeFactory.FindModified(), line 991. By reordering the parameters correctly in TypeFactory.FindModified (swapping "x" and "y" around), the framework now resolves the id of the correct (entity) variable. But I am not familiar with the process of creating a patch.
> Thank you for looking into this.

-- 
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] Reopened: (NH-716) Dirty Checking exception (many-to-one, select-before-update)

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

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


Reopening to fix in 1.0.4

> Dirty Checking exception (many-to-one, select-before-update)
> ------------------------------------------------------------
>
>          Key: NH-716
>          URL: http://jira.nhibernate.org/browse/NH-716
>      Project: NHibernate
>         Type: Bug
>   Components: Core
>     Versions: 1.2.0.Alpha1
>     Reporter: Sasha Borodin
>      Fix For: 1.0.4, 1.2.0.Beta2

>
> This problem can be reproduced by flushing a session with an entity which contains a "many-to-one" property, but only when the "select-before-update" option is turned on for that class (and performed).
> The problem occurs during the "dirty checking", in the EntityType.GetIdentifier. This is because that method is called on a variable which is already a String identifier itself, in ManyToOneType.IsModified. And i believe that THIS is because the "old" and "current" parameters passed to this class by TypeFactory.FindModified are reversed ("x" and "y"), so that EntityType.GetIdentifier is attempting to resolve the id on the wrong variable.
> Full stack trace of any exception that occurs:
> NHibernate.MappingException was unhandled by user code
> Message="Unknown entity class: System.String"
> Source="NHibernate"
> StackTrace:
> at NHibernate.Impl.SessionFactoryImpl.GetEntityPersister(Type theClass) in c:\net\nhibernate\nhibernate\src\NHibernate\Impl\SessionFactoryImpl.cs:line 563
> at NHibernate.Impl.SessionImpl.GetClassPersister(Type theClass) in c:\net\nhibernate\nhibernate\src\NHibernate\Impl\SessionImpl.cs:line 3489
> at NHibernate.Impl.SessionImpl.GetEntityPersister(Object obj) in c:\net\nhibernate\nhibernate\src\NHibernate\Impl\SessionImpl.cs:line 3497
> at NHibernate.Impl.SessionImpl.GetEntityIdentifierIfNotUnsaved(Object obj) in c:\net\nhibernate\nhibernate\src\NHibernate\Impl\SessionImpl.cs:line 3613
> at NHibernate.Type.EntityType.GetIdentifier(Object value, ISessionImplementor session) in c:\net\nhibernate\nhibernate\src\NHibernate\Type\EntityType.cs:line 60
> at NHibernate.Type.ManyToOneType.IsModified(Object old, Object current, Boolean[] checkable, ISessionImplementor session) in c:\net\nhibernate\nhibernate\src\NHibernate\Type\ManyToOneType.cs:line 112
> at NHibernate.Type.TypeFactory.FindModified(StandardProperty[] properties, Object[] x, Object[] y, Boolean[][] includeColumns, Boolean anyUninitializedProperties, ISessionImplementor session) in c:\net\nhibernate\nhibernate\src\NHibernate\Type\TypeFactory.cs:line 988
> at NHibernate.Persister.Entity.AbstractEntityPersister.FindModified(Object[] old, Object[] current, Object obj, ISessionImplementor session) in c:\net\nhibernate\nhibernate\src\NHibernate\Persister\Entity\AbstractEntityPersister.cs:line 311
> at NHibernate.Impl.SessionImpl.FlushEntity(Object obj, EntityEntry entry) in c:\net\nhibernate\nhibernate\src\NHibernate\Impl\SessionImpl.cs:line 3263
> at NHibernate.Impl.SessionImpl.FlushEntities() in c:\net\nhibernate\nhibernate\src\NHibernate\Impl\SessionImpl.cs:line 3200
> at NHibernate.Impl.SessionImpl.FlushEverything() in c:\net\nhibernate\nhibernate\src\NHibernate\Impl\SessionImpl.cs:line 2953
> at NHibernate.Impl.SessionImpl.Flush() in c:\net\nhibernate\nhibernate\src\NHibernate\Impl\SessionImpl.cs:line 2929
> at NHibernate.Transaction.AdoTransaction.Commit() in c:\net\nhibernate\nhibernate\src\NHibernate\Transaction\AdoTransaction.cs:line 141
> at DFWHC.GroupOne.GoRes.business.DivisionFactory.UpdateDivision(Division division) in C:\Development\dfw_hospital\GroupOne\GoRes\library\business\DivisionFactory.cs:line 72
> at EditDivision.Update(Object src, EventArgs args) in c:\Development\dfw_hospital\GroupOne\GoRes\website\user\employee\admin\EditDivision.aspx.cs:line 135
> at System.Web.UI.WebControls.Button.OnClick(EventArgs e)
> at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)
> at System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument)
> at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
> at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
> at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
> I think that I was able to solve the issue by making a small change in TypeFactory.FindModified(), line 991. By reordering the parameters correctly in TypeFactory.FindModified (swapping "x" and "y" around), the framework now resolves the id of the correct (entity) variable. But I am not familiar with the process of creating a patch.
> Thank you for looking into this.

-- 
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-716) Dirty Checking exception (many-to-one, select-before-update)

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

     [ http://jira.nhibernate.org/browse/NH-716?page=comments#action_14761 ]
     
Eric Katz commented on NH-716:
------------------------------

Is there a workaround for this issue in Version 1.0.3?  I believe I am encountering this issue because I have a table I'm joining to which has a primary key of a string from a joined-class entity.  

Any help would be greatly appreciated.

> Dirty Checking exception (many-to-one, select-before-update)
> ------------------------------------------------------------
>
>          Key: NH-716
>          URL: http://jira.nhibernate.org/browse/NH-716
>      Project: NHibernate
>         Type: Bug
>   Components: Core
>     Versions: 1.2.0.Alpha1
>     Reporter: Sasha Borodin
>      Fix For: 1.2.0.Beta2

>
> This problem can be reproduced by flushing a session with an entity which contains a "many-to-one" property, but only when the "select-before-update" option is turned on for that class (and performed).
> The problem occurs during the "dirty checking", in the EntityType.GetIdentifier. This is because that method is called on a variable which is already a String identifier itself, in ManyToOneType.IsModified. And i believe that THIS is because the "old" and "current" parameters passed to this class by TypeFactory.FindModified are reversed ("x" and "y"), so that EntityType.GetIdentifier is attempting to resolve the id on the wrong variable.
> Full stack trace of any exception that occurs:
> NHibernate.MappingException was unhandled by user code
> Message="Unknown entity class: System.String"
> Source="NHibernate"
> StackTrace:
> at NHibernate.Impl.SessionFactoryImpl.GetEntityPersister(Type theClass) in c:\net\nhibernate\nhibernate\src\NHibernate\Impl\SessionFactoryImpl.cs:line 563
> at NHibernate.Impl.SessionImpl.GetClassPersister(Type theClass) in c:\net\nhibernate\nhibernate\src\NHibernate\Impl\SessionImpl.cs:line 3489
> at NHibernate.Impl.SessionImpl.GetEntityPersister(Object obj) in c:\net\nhibernate\nhibernate\src\NHibernate\Impl\SessionImpl.cs:line 3497
> at NHibernate.Impl.SessionImpl.GetEntityIdentifierIfNotUnsaved(Object obj) in c:\net\nhibernate\nhibernate\src\NHibernate\Impl\SessionImpl.cs:line 3613
> at NHibernate.Type.EntityType.GetIdentifier(Object value, ISessionImplementor session) in c:\net\nhibernate\nhibernate\src\NHibernate\Type\EntityType.cs:line 60
> at NHibernate.Type.ManyToOneType.IsModified(Object old, Object current, Boolean[] checkable, ISessionImplementor session) in c:\net\nhibernate\nhibernate\src\NHibernate\Type\ManyToOneType.cs:line 112
> at NHibernate.Type.TypeFactory.FindModified(StandardProperty[] properties, Object[] x, Object[] y, Boolean[][] includeColumns, Boolean anyUninitializedProperties, ISessionImplementor session) in c:\net\nhibernate\nhibernate\src\NHibernate\Type\TypeFactory.cs:line 988
> at NHibernate.Persister.Entity.AbstractEntityPersister.FindModified(Object[] old, Object[] current, Object obj, ISessionImplementor session) in c:\net\nhibernate\nhibernate\src\NHibernate\Persister\Entity\AbstractEntityPersister.cs:line 311
> at NHibernate.Impl.SessionImpl.FlushEntity(Object obj, EntityEntry entry) in c:\net\nhibernate\nhibernate\src\NHibernate\Impl\SessionImpl.cs:line 3263
> at NHibernate.Impl.SessionImpl.FlushEntities() in c:\net\nhibernate\nhibernate\src\NHibernate\Impl\SessionImpl.cs:line 3200
> at NHibernate.Impl.SessionImpl.FlushEverything() in c:\net\nhibernate\nhibernate\src\NHibernate\Impl\SessionImpl.cs:line 2953
> at NHibernate.Impl.SessionImpl.Flush() in c:\net\nhibernate\nhibernate\src\NHibernate\Impl\SessionImpl.cs:line 2929
> at NHibernate.Transaction.AdoTransaction.Commit() in c:\net\nhibernate\nhibernate\src\NHibernate\Transaction\AdoTransaction.cs:line 141
> at DFWHC.GroupOne.GoRes.business.DivisionFactory.UpdateDivision(Division division) in C:\Development\dfw_hospital\GroupOne\GoRes\library\business\DivisionFactory.cs:line 72
> at EditDivision.Update(Object src, EventArgs args) in c:\Development\dfw_hospital\GroupOne\GoRes\website\user\employee\admin\EditDivision.aspx.cs:line 135
> at System.Web.UI.WebControls.Button.OnClick(EventArgs e)
> at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument)
> at System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument)
> at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
> at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
> at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
> I think that I was able to solve the issue by making a small change in TypeFactory.FindModified(), line 991. By reordering the parameters correctly in TypeFactory.FindModified (swapping "x" and "y" around), the framework now resolves the id of the correct (entity) variable. But I am not familiar with the process of creating a patch.
> Thank you for looking into this.

-- 
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-859) Improve SubselectFetch performance

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

Improve SubselectFetch performance
----------------------------------

         Key: NH-859
         URL: http://jira.nhibernate.org/browse/NH-859
     Project: NHibernate
        Type: Improvement
  Components: Core  
    Versions: 1.2.0.Beta3    
    Reporter: Sergey Koshcheyev
    Priority: Trivial
     Fix For: LATER


http://forum.hibernate.org/viewtopic.php?p=2336860#2336860

SubselectFetch constructor takes a relatively long time to execute.

-- 
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-858) Filter .xml not parsed

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

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

    Resolution: Duplicate

Apparently a duplicate of NH-845

> Filter .xml not parsed
> ----------------------
>
>          Key: NH-858
>          URL: http://jira.nhibernate.org/browse/NH-858
>      Project: NHibernate
>         Type: Improvement
>   Components: Core
>     Versions: 1.2.0.Beta2
>     Reporter: Luis Ferreira
>     Priority: Trivial

>
> My experience is that when using several .xml files for mappings, and embedding them in the Assembly, Filters will only be parsed if they are parsed in some an .xml file containing a class mapping. A filter declaration on a file of its own will not be parsed.
> Since filters may be used across several mappings, it would be great to be able to put them in their own file(s).

-- 
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-858) Filter .xml not parsed

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

Filter .xml not parsed
----------------------

         Key: NH-858
         URL: http://jira.nhibernate.org/browse/NH-858
     Project: NHibernate
        Type: Improvement
  Components: Core  
    Versions: 1.2.0.Beta2    
    Reporter: Luis Ferreira
    Priority: Trivial


My experience is that when using several .xml files for mappings, and embedding them in the Assembly, Filters will only be parsed if they are parsed in some an .xml file containing a class mapping. A filter declaration on a file of its own will not be parsed.

Since filters may be used across several mappings, it would be great to be able to put them in their own file(s).

-- 
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-857) Filter parameter is mandatory and should be optional

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

Filter parameter is mandatory and should be optional
----------------------------------------------------

         Key: NH-857
         URL: http://jira.nhibernate.org/browse/NH-857
     Project: NHibernate
        Type: Bug
  Components: Core  
    Versions: 1.2.0.Beta2    
    Reporter: Luis Ferreira
    Priority: Minor


When a filter is declared with no parameters, an exception is raised.
For instance, we'd like to have a filter such as:

<filter-def name="Autorizacoes" condition="Classe = 1">

So, results are accepted if a column has as value a specified constant (rather than something variable). The resulting exception is:

A first chance exception of type 'NHibernate.MappingException' occurred in BancoDePortugal.SI.REI.Negocio.DLL

Additional information: Denominacao.hbm.xml(39,5): XML validation error: The element 'filter-def' in namespace 'urn:nhibernate-mapping-2.2' has incomplete content. List of possible elements expected: 'urn:nhibernate-mapping-2.2:filter-param'.

Of course a possible workaround is using a parameter instead of the constant, and pass the constant every time... but it is odd.


-- 
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-856) NHibernate.Mapping.Attributes - Allow mapping attributes on interfaces

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

     [ http://jira.nhibernate.org/browse/NH-856?page=3Dall ]
    =20
Pierre Henri Kuat=C3=A9 closed NH-856:
---------------------------------

    Resolution: Fixed

> NHibernate.Mapping.Attributes - Allow mapping attributes on interfaces
> ----------------------------------------------------------------------
>
>          Key: NH-856
>          URL: http://jira.nhibernate.org/browse/NH-856
>      Project: NHibernate
>         Type: Improvement
>   Components: Contrib
>     Versions: 1.2.0.Beta2
>     Reporter: Pierre Henri Kuat=C3=A9
>     Assignee: Pierre Henri Kuat=C3=A9
>     Priority: Trivial
>      Fix For: 1.2.0.Beta3

>
> This feature was requested by a user on the forum.

--=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] Created: (NH-856) NHibernate.Mapping.Attributes - Allow mapping attributes on interfaces

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

NHibernate.Mapping.Attributes - Allow mapping attributes on interfaces
----------------------------------------------------------------------

         Key: NH-856
         URL: http://jira.nhibernate.org/browse/NH-856
     Project: NHibernate
        Type: Improvement
  Components: Contrib =20
    Versions: 1.2.0.Beta2   =20
    Reporter: Pierre Henri Kuat=C3=A9
 Assigned to: Pierre Henri Kuat=C3=A9=20
    Priority: Trivial
     Fix For: 1.2.0.Beta3


This feature was requested by a user on the forum.

--=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-648) NHibernate.Mapping.Attributes - Allow [(Jcs)Cache], [Discriminator] and [Key] at class-level

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

     [ http://jira.nhibernate.org/browse/NH-648?page=3Dall ]
    =20
Pierre Henri Kuat=C3=A9 closed NH-648:
---------------------------------

    Resolution: Fixed

Done for [(Jcs)Cache], [Discriminator] and [Key].

> NHibernate.Mapping.Attributes - Allow [(Jcs)Cache], [Discriminator] and [=
Key] at class-level
> -------------------------------------------------------------------------=
-------------------
>
>          Key: NH-648
>          URL: http://jira.nhibernate.org/browse/NH-648
>      Project: NHibernate
>         Type: Improvement
>   Components: Contrib
>     Versions: 1.2.0.Alpha1
>     Reporter: Christoph Wienands
>     Assignee: Pierre Henri Kuat=C3=A9
>     Priority: Trivial
>      Fix For: 1.2.0.Beta3

>
> Hello KPixel,
> I have another improvement request for you. I defined a base class Domain=
Object, which already defines an ID (note that PascalCaseMUnderScore is a c=
ustom FieldAccessor so I can use strong typing instead of strings):
> =09public class DomainObjectInt : DomainObject<int>
> =09{
> =09=09[Id(0, Name =3D "ID", Column =3D "ID", TypeType =3D typeof(Int32), =
UnsavedValue =3D "0",
> =09=09=09AccessType =3D typeof(PascalCaseMUnderScore))]
> =09=09[Generator(1, Class =3D "identity")]
> =09=09public override int ID
> =09=09{
> =09=09=09get { return base.ID; }
> =09=09}
> =09}
> Now when I want to define inheritance hierarchies I run into trouble:
> =09[Class(0, NameType =3D typeof(Operation), Table =3D "[Operation]", Laz=
y =3D false)]
> =09[Discriminator(1, Column =3D "Discriminator")]
> =09public abstract class Operation : DomainObjectInt, IOperation
> =09{
> =09}
> I'd like to place the discriminator right at the top with the class defin=
ition. However, it's only valid on property, indexer or field. The workarou=
nd is to place it e.g. on top of the first member variable but that's misle=
ading when someone looks at the code.
> Is there a reason why I couldn't place that attribute on top of the class=
?
> Thanks, Christoph

--=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] Updated: (NH-648) NHibernate.Mapping.Attributes - Allow [(Jcs)Cache], [Discriminator] and [Key] at class-level

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

     [ http://jira.nhibernate.org/browse/NH-648?page=3Dall ]

Pierre Henri Kuat=C3=A9 updated NH-648:
----------------------------------

    Description:=20
Hello KPixel,

I have another improvement request for you. I defined a base class DomainOb=
ject, which already defines an ID (note that PascalCaseMUnderScore is a cus=
tom FieldAccessor so I can use strong typing instead of strings):

=09public class DomainObjectInt : DomainObject<int>
=09{
=09=09[Id(0, Name =3D "ID", Column =3D "ID", TypeType =3D typeof(Int32), Un=
savedValue =3D "0",
=09=09=09AccessType =3D typeof(PascalCaseMUnderScore))]
=09=09[Generator(1, Class =3D "identity")]
=09=09public override int ID
=09=09{
=09=09=09get { return base.ID; }
=09=09}
=09}

Now when I want to define inheritance hierarchies I run into trouble:

=09[Class(0, NameType =3D typeof(Operation), Table =3D "[Operation]", Lazy =
=3D false)]
=09[Discriminator(1, Column =3D "Discriminator")]
=09public abstract class Operation : DomainObjectInt, IOperation
=09{
=09}

I'd like to place the discriminator right at the top with the class definit=
ion. However, it's only valid on property, indexer or field. The workaround=
 is to place it e.g. on top of the first member variable but that's mislead=
ing when someone looks at the code.

Is there a reason why I couldn't place that attribute on top of the class?

Thanks, Christoph

  was:
Hello Kpix,

I have another improvement request for you. I defined a base class DomainOb=
ject, which already defines an ID (note that PascalCaseMUnderScore is a cus=
tom FieldAccessor so I can use strong typing instead of strings):

=09public class DomainObjectInt : DomainObject<int>
=09{
=09=09[Id(0, Name =3D "ID", Column =3D "ID", TypeType =3D typeof(Int32), Un=
savedValue =3D "0",
=09=09=09AccessType =3D typeof(PascalCaseMUnderScore))]
=09=09[Generator(1, Class =3D "identity")]
=09=09public override int ID
=09=09{
=09=09=09get { return base.ID; }
=09=09}
=09}

Now when I want to define inheritance hierarchies I run into trouble:

=09[Class(0, NameType =3D typeof(Operation), Table =3D "[Operation]", Lazy =
=3D false)]
=09[Discriminator(1, Column =3D "Discriminator")]
=09public abstract class Operation : DomainObjectInt, IOperation
=09{
=09}

I'd like to place the discriminator right at the top with the class definit=
ion. However, it's only valid on property, indexer or field. The workaround=
 is to place it e.g. on top of the first member variable but that's mislead=
ing when someone looks at the code.

Is there a reason why I couldn't place that attribute on top of the class?

Thanks, Christoph

        Summary: NHibernate.Mapping.Attributes - Allow [(Jcs)Cache], [Discr=
iminator] and [Key] at class-level  (was: Discriminator attribute allowed f=
or class (not only property, field or indexer))

> NHibernate.Mapping.Attributes - Allow [(Jcs)Cache], [Discriminator] and [=
Key] at class-level
> -------------------------------------------------------------------------=
-------------------
>
>          Key: NH-648
>          URL: http://jira.nhibernate.org/browse/NH-648
>      Project: NHibernate
>         Type: Improvement
>   Components: Contrib
>     Versions: 1.2.0.Alpha1
>     Reporter: Christoph Wienands
>     Assignee: Pierre Henri Kuat=C3=A9
>     Priority: Trivial
>      Fix For: 1.2.0.Beta3

>
> Hello KPixel,
> I have another improvement request for you. I defined a base class Domain=
Object, which already defines an ID (note that PascalCaseMUnderScore is a c=
ustom FieldAccessor so I can use strong typing instead of strings):
> =09public class DomainObjectInt : DomainObject<int>
> =09{
> =09=09[Id(0, Name =3D "ID", Column =3D "ID", TypeType =3D typeof(Int32), =
UnsavedValue =3D "0",
> =09=09=09AccessType =3D typeof(PascalCaseMUnderScore))]
> =09=09[Generator(1, Class =3D "identity")]
> =09=09public override int ID
> =09=09{
> =09=09=09get { return base.ID; }
> =09=09}
> =09}
> Now when I want to define inheritance hierarchies I run into trouble:
> =09[Class(0, NameType =3D typeof(Operation), Table =3D "[Operation]", Laz=
y =3D false)]
> =09[Discriminator(1, Column =3D "Discriminator")]
> =09public abstract class Operation : DomainObjectInt, IOperation
> =09{
> =09}
> I'd like to place the discriminator right at the top with the class defin=
ition. However, it's only valid on property, indexer or field. The workarou=
nd is to place it e.g. on top of the first member variable but that's misle=
ading when someone looks at the code.
> Is there a reason why I couldn't place that attribute on top of the class=
?
> Thanks, Christoph

--=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] Updated: (NH-855) Port lazy="extra" from Hibernate 3

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

     [ http://jira.nhibernate.org/browse/NH-855?page=3Dall ]

Sergey Koshcheyev updated NH-855:
---------------------------------

    Fix Version: LATER
       Priority: Major  (was: Minor)
        Summary: Port lazy=3D"extra" from Hibernate 3  (was: Lazy collectio=
n retrieval should use proxies)
           type: New Feature  (was: Improvement)

> Port lazy=3D"extra" from Hibernate 3
> ----------------------------------
>
>          Key: NH-855
>          URL: http://jira.nhibernate.org/browse/NH-855
>      Project: NHibernate
>         Type: New Feature
>   Components: Core
>     Versions: 1.2.0.Beta2
>     Reporter: Andr=C3=A9s G. Aragoneses
>      Fix For: LATER
>  Attachments: NHibBugAboutDataRetrieval.zip
>
> When retrieving a lazy collection I've noted that there is much informati=
on retrieved from the DB that may not be needed. For example, if we only ne=
ed the Count property of the collection, NHibernate retrieves full objects =
instead of just proxies (object with only the ID property filled).
> I am attaching a testcase.
> Note the folling C# lines in the testcase:
> IList aParameters =3D oSession.CreateCriteria(typeof(Parameter)).List();
> if (aParameters.Count =3D=3D 0)
> {
>     return;
> }
> Parameter oParameter =3D aParameters[0] as Parameter;
> //the Group is a proxy object, so this instruction does not retrieve anyt=
hing from DB
> int iIdGroup =3D oParameter.Group.Id;
> //this instruction unproxies the object because it is filled with its pro=
perties
> string sName =3D oParameter.Group.Name;
> //why don't we retrieve here only proxies? because we only need to know h=
ow many rows, their ID's
> int iCount =3D oParameter.Group.Terminals.Count;
> //if in the last instruction NHibernate would have retrieved proxies inst=
ead of full objects
> //this instruction would generate a new query
> string sName2 =3D oParameter.Group.Terminals[0].Name;
> I know that maybe this is a too specific feature and perhaps, to be imple=
mented, it should be done so by adding a new configuration parameter, for e=
xample: RetrievalMode.Minimal.
> What do you think?
> P.S.: You may add the NHib libs to the Lib subdir of the ZIP file attache=
d, before building it.

--=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] Created: (NH-855) Lazy collection retrieval should use proxies

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

Lazy collection retrieval should use proxies
--------------------------------------------

         Key: NH-855
         URL: http://jira.nhibernate.org/browse/NH-855
     Project: NHibernate
        Type: Improvement
  Components: Core =20
    Versions: 1.2.0.Beta2   =20
    Reporter: Andr=C3=A9s G. Aragoneses
    Priority: Minor
 Attachments: NHibBugAboutDataRetrieval.zip

When retrieving a lazy collection I've noted that there is much information=
 retrieved from the DB that may not be needed. For example, if we only need=
 the Count property of the collection, NHibernate retrieves full objects in=
stead of just proxies (object with only the ID property filled).

I am attaching a testcase.

Note the folling C# lines in the testcase:

IList aParameters =3D oSession.CreateCriteria(typeof(Parameter)).List();

if (aParameters.Count =3D=3D 0)
{
    return;
}
Parameter oParameter =3D aParameters[0] as Parameter;

//the Group is a proxy object, so this instruction does not retrieve anythi=
ng from DB
int iIdGroup =3D oParameter.Group.Id;

//this instruction unproxies the object because it is filled with its prope=
rties
string sName =3D oParameter.Group.Name;

//why don't we retrieve here only proxies? because we only need to know how=
 many rows, their ID's
int iCount =3D oParameter.Group.Terminals.Count;

//if in the last instruction NHibernate would have retrieved proxies instea=
d of full objects
//this instruction would generate a new query
string sName2 =3D oParameter.Group.Terminals[0].Name;

I know that maybe this is a too specific feature and perhaps, to be impleme=
nted, it should be done so by adding a new configuration parameter, for exa=
mple: RetrievalMode.Minimal.

What do you think?

P.S.: You may add the NHib libs to the Lib subdir of the ZIP file attached,=
 before building it.

--=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] Commented: (NH-853) Inconsistent need of the Flush method invokation

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

     [ http://jira.nhibernate.org/browse/NH-853?page=3Dcomments#action_1475=
8 ]
    =20
Andr=C3=A9s G. Aragoneses commented on NH-853:
-----------------------------------------

Thanks for the comments.

BTW, regarding the Ayende's one: "In the future, NHibernate is going to mov=
e to a mode where it will only do Identity Inserts when in a transaction", =
why don't we close then this issue in that future? I think this behaviour m=
ay be confusing for newcomers so, at least, we could reference them to this=
 "UNRESOLVED" feature.

> Inconsistent need of the Flush method invokation
> ------------------------------------------------
>
>          Key: NH-853
>          URL: http://jira.nhibernate.org/browse/NH-853
>      Project: NHibernate
>         Type: Bug
>   Components: Core
>     Versions: 1.2.0.Beta2
>     Reporter: Andr=C3=A9s G. Aragoneses
>     Priority: Trivial
>  Attachments: NHibBugAboutFlush.zip
>
> I have managed to create a simple NHibernate testcase which creates some =
objects and all the operations are done successfully without the FLUSH meth=
od invokation *except* the many-to-many relation creations.
> I am attaching the testcase as a VS2005 solution. Note the following line=
 in Program.cs:
>             //if this line is commented, the table TERMINALS_TERMINALGROU=
PS is not persisted! but the rest yes
>             oSession.Flush();
> P.S.: Be sure to add the NHibernate DLL's to the 'Lib' directory (and to =
the bin/Debug ones) when uncompressing.
> P.S.2: Don't pay attention to the name of the solution. It's for another =
bug I am going to open.

--=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] Updated: (NH-692) Problem when display a Collection in a Combobox (C#)

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

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

Sergey Koshcheyev updated NH-692:
---------------------------------

    Comment: was deleted

> Problem when display a Collection in a Combobox (C#)
> ----------------------------------------------------
>
>          Key: NH-692
>          URL: http://jira.nhibernate.org/browse/NH-692
>      Project: NHibernate
>         Type: Bug
>   Components: Core
>     Versions: 1.2.0.Beta1, 1.2.0.Alpha1
>     Reporter: Franz Meier
>  Attachments: bugreport.zip
>
> The Problem occurs when I retrieve data from a table and put the List as the Datasource of a combobox
> eg:
> coDomain.DataSource = session.CreateQuery("from TDomain").List();
> //then i set display member:
> coDomain.DisplayMember = "DomainName";
> After that only the first value is displayed correctly in the combobox,
> all other values are display as the Class Name (it seems that the TOString() Function is called). see atteched bug.jpg
> The Interesting thing is, this problems existist since 1.2.0Alpha1 and also on the current cvs snapshot.
> the old 1.0.2 is working perfectly.
> The Domain Class has an included bag, if i remove the bag the whole thing is also working.
> Strange!
> It think this is an proxy issue!

-- 
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-239) Issue with PersistentEnumType.ReturnedClass

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

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

Sergey Koshcheyev updated NH-239:
---------------------------------

    Comment: was deleted

> Issue with PersistentEnumType.ReturnedClass
> -------------------------------------------
>
>          Key: NH-239
>          URL: http://jira.nhibernate.org/browse/NH-239
>      Project: NHibernate
>         Type: Bug
>   Components: Core
>     Reporter: Jenser Almeida
>     Assignee: Mike Doerfler
>      Fix For: beta-0.8.4
>  Attachments: EnumTest.zip
>
> A query like "select new Result(t.str1, t.enumType) from Test t" will not work because a issue with the System.Type of enum's. 
> Test case e relevant mapping's will be atached.
> PS If there is anything not clear please tell me. I am not a good english writer

-- 
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-468) Publisher policy to redirect 1.0 -> 1.0.1

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

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

Sergey Koshcheyev updated NH-468:
---------------------------------

    Comment: was deleted

> Publisher policy to redirect 1.0 -> 1.0.1
> -----------------------------------------
>
>          Key: NH-468
>          URL: http://jira.nhibernate.org/browse/NH-468
>      Project: NHibernate
>         Type: Task
>   Components: Toolset
>     Versions: 1.0, 1.0.1
>     Reporter: Sergey Koshcheyev
>     Priority: Minor
>  Attachments: nhibernate-1.0.1-policy.zip
>
> Need to create a publisher policy assembly signed with our snk redirecting NH 1.0.0.0 to 1.0.1.0 (also including all the NHC assemblies). It can be installed to the GAC together with NH 1.0.1 to allow applications compiled against 1.0 to run with 1.0.1.
> The assembly should also be generated automatically as part of the build process (i.e. redirecting 1.0.* to 1.0.current).

-- 
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-854) Can't use order-by with set

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

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

    Resolution: Not an Issue

Please go to the forum (http://forum.hibernate.org). JIRA is not the place to post your problems and demand that somebody helps you "urgently".

> Can't use order-by with set
> ---------------------------
>
>          Key: NH-854
>          URL: http://jira.nhibernate.org/browse/NH-854
>      Project: NHibernate
>         Type: Bug
>     Reporter: Kaivalya Vishnu
>     Priority: Blocker

>
> I am usinh nHibernate 2.0. My code does not work if I use "order-by" attribute in .hbm.xml file with a "set"
> Following is my .hbm.xml file 
> <class name="Contract" table="tblContracts" mutable="true">
> 		<id name="ID" column="ID" type="Int32">
> 			<generator class="native" />
> 		</id>
> 		<property name="Name"			column="Name"					type="String" />
>     <set 
>       name="allDeals" 
>       table="tblDeals" 
>       inverse="true" 
>       cascade="all-delete-orphan"
>       access="field"
>       lazy="true"	
>       order-by="ClientName asc">
>       <key column="FK_ContractID" />
>       <one-to-many class="Deal" not-found="ignore" />
>     </set>
>   </class>
> the following is my entity class definition in .NET
>     public class Contract
>     {
>         private int id_number;
>         private string name;
>         
>         //private ISet<Deal>allDeals = new HashedSet<Deal>(); //Use without order-by
>         //private ListSet allDeals = new ListSet(); //Use without order-by
>         private IDictionary allDeals; //Use without order-by
>         public virtual int ID
>         {
>             get { return id_number; }
>             set { id_number = value; }
>         }
>         public virtual string Name
>         {
>             get { return name; }
>             set { name = value; }
>         }
>         /// <summary>
>         /// Do not use. Instead use:
>         /// deal.Liabilities.AllLiabilities 
>         /// </summary>
>         /* internal virtual ISet<Deal> AllDeals
>         {
>             get { return allDeals; }
>             set { allDeals = value; }
>         }*/
>         internal virtual IDictionary AllDeals
>         {
>             get { return allDeals; }
>             set { allDeals = value; }
>         }
>         public Contract()
>         {
>             id_number = 0;
>             name = "Unknown";
>         }
>         public override string ToString()
>         {
>             return id_number.ToString() + "," + name;
>         }
>     }
> It always throws an exception saying that can not map the entity class. Please help urgently.

-- 
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-854) Can't use order-by with set

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

Can't use order-by with set
---------------------------

         Key: NH-854
         URL: http://jira.nhibernate.org/browse/NH-854
     Project: NHibernate
        Type: Bug
    Reporter: Kaivalya Vishnu
    Priority: Blocker


I am usinh nHibernate 2.0. My code does not work if I use "order-by" attribute in .hbm.xml file with a "set"

Following is my .hbm.xml file 

<class name="Contract" table="tblContracts" mutable="true">
		<id name="ID" column="ID" type="Int32">
			<generator class="native" />
		</id>
		<property name="Name"			column="Name"					type="String" />
    <set 
      name="allDeals" 
      table="tblDeals" 
      inverse="true" 
      cascade="all-delete-orphan"
      access="field"
      lazy="true"	
      order-by="ClientName asc">

      <key column="FK_ContractID" />
      <one-to-many class="Deal" not-found="ignore" />
    </set>
  </class>


the following is my entity class definition in .NET

    public class Contract
    {
        private int id_number;
        private string name;
        
        //private ISet<Deal>allDeals = new HashedSet<Deal>(); //Use without order-by
        //private ListSet allDeals = new ListSet(); //Use without order-by
        private IDictionary allDeals; //Use without order-by

        public virtual int ID
        {
            get { return id_number; }
            set { id_number = value; }
        }

        public virtual string Name
        {
            get { return name; }
            set { name = value; }
        }

        /// <summary>
        /// Do not use. Instead use:
        /// deal.Liabilities.AllLiabilities 
        /// </summary>
        /* internal virtual ISet<Deal> AllDeals
        {
            get { return allDeals; }
            set { allDeals = value; }
        }*/

        internal virtual IDictionary AllDeals
        {
            get { return allDeals; }
            set { allDeals = value; }
        }

        public Contract()
        {
            id_number = 0;
            name = "Unknown";
        }

        public override string ToString()
        {
            return id_number.ToString() + "," + name;
        }
    }

It always throws an exception saying that can not map the entity class. Please help urgently.

-- 
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-851) More descriptive error message for 'Cannot find constructor' on projections

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

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

    Resolution: Fixed

> More descriptive error message for 'Cannot find constructor' on projections
> ---------------------------------------------------------------------------
>
>          Key: NH-851
>          URL: http://jira.nhibernate.org/browse/NH-851
>      Project: NHibernate
>         Type: Improvement
>   Components: Core
>     Versions: 1.2.0.Beta2
>     Reporter: Ken Egozi
>     Priority: Trivial
>      Fix For: 1.2.0.Beta3
>  Attachments: DisplayParametersOnConstructorNotFound.patch
>
> Using .NET 2.0, over SQL Server 2005
> one of the latests changes (I guess) was that "select new Projection(... sum(s.Data)) ... " would assume "long" for the sum element, rather than int.
> So if the projection has "int" in the constructor an exception will occur. 
> However, current users gets a non informative error message.
> attached here a patch that would add the expected types for the contructor's parameters, so it would be easier to fix.
> I was not able to build the solution due to some local problems with nant, so it should be tested.

-- 
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