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

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

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

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

Sergey Koshcheyev reassigned NH-515:
------------------------------------

    Assign To: 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

[nhibernate-issues] [JIRA] Closed: (NH-614) Optimize generic IQuery.List implementation

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

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

    Resolution: Fixed

> Optimize generic IQuery.List implementation
> -------------------------------------------
>
>          Key: NH-614
>          URL: http://jira.nhibernate.org/browse/NH-614
>      Project: NHibernate
>         Type: Improvement
>   Components: Core
>     Versions: 1.2.0.Alpha1
>     Reporter: Sergey Koshcheyev
>     Priority: Trivial
>      Fix For: 1.2.0.Beta2

>
> The current implementation of IQuery.List or ISession.List run the non-generic version and copy the results into a new generic collection. This should be optimized so that the results are placed into the generic collection from the beginning.

-- 
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-775) IQuery.SetResultTransformer() doesn't work

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

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

    Resolution: Fixed

> IQuery.SetResultTransformer() doesn't work
> ------------------------------------------
>
>          Key: NH-775
>          URL: http://jira.nhibernate.org/browse/NH-775
>      Project: NHibernate
>         Type: Bug
>   Components: Core
>     Versions: 1.2.0.Beta1
>     Reporter: Dario Cecere
>     Priority: Minor
>      Fix For: 1.2.0.Beta2

>
> (already posted on forum and approved as bug by Sergey)
> NHibernate does not call the IResultTransformer Interface Object within a situation like this:
> IQuery q = oz.CreateQuery("select users.Username, roles from Domain.EUser as users inner join users.Roles as roles where users.Username = 'admin'"); 
> q = q.SetResultTransformer(o); 
> IEnumerable l = q.Enumerable(); 
> The same with List(), and i figure also with generic-methods
> Hope i can help more

-- 
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] Deleted: (NH-785) Test

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

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


> Test
> ----
>
>          Key: NH-785
>          URL: http://jira.nhibernate.org/browse/NH-785
>      Project: NHibernate
>         Type: Task
>     Reporter: Sergey Koshcheyev
>     Priority: Trivial

>


-- 
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-785) Test

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

Test
----

         Key: NH-785
         URL: http://jira.nhibernate.org/browse/NH-785
     Project: NHibernate
        Type: Task
    Reporter: Sergey Koshcheyev
    Priority: Trivial




-- 
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-631) Describe contents of the bin directory of the distribution

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

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

    Fix Version:     (was: 1.2.0.Beta2)
     Resolution: Not an Issue

Closing, doesn't seem to be as important as I thought.

> Describe contents of the bin directory of the distribution
> ----------------------------------------------------------
>
>          Key: NH-631
>          URL: http://jira.nhibernate.org/browse/NH-631
>      Project: NHibernate
>         Type: Task
>   Components: Documentation
>     Versions: 1.2.0.Alpha1
>     Reporter: Sergey Koshcheyev
>     Priority: Trivial

>
> People get confused and don't know which .dll to reference for what. Need to create some kind of description.

-- 
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-615) Change XML schema names to -2.2

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

     [ http://jira.nhibernate.org/browse/NH-615?page=all ]
     
Christian Bauer resolved NH-615:
--------------------------------

    Resolution: Fixed

OK, there really is no perfect solution. Use a).

> Change XML schema names to -2.2
> -------------------------------
>
>          Key: NH-615
>          URL: http://jira.nhibernate.org/browse/NH-615
>      Project: NHibernate
>         Type: Improvement
>   Components: Core
>     Versions: 1.2.0.Alpha1
>     Reporter: Sergey Koshcheyev
>     Assignee: Sergey Koshcheyev
>     Priority: Trivial
>      Fix For: 1.2.0.Beta2

>
> The XML schema name of nhibernate-mapping-2.0 should probably be changed to nhibernate-mapping-2.2 to reflect changes made since 1.0.2.

-- 
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-615) Change XML schema names to -2.2

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

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

Option a) was what I did.

The schema was only added to, nothing was removed. But of course a file using 1.2-specific features won't validate against the 1.0.2 schema since it doesn't permit any attributes or elements it doesn't know about.

> Change XML schema names to -2.2
> -------------------------------
>
>          Key: NH-615
>          URL: http://jira.nhibernate.org/browse/NH-615
>      Project: NHibernate
>         Type: Improvement
>   Components: Core
>     Versions: 1.2.0.Alpha1
>     Reporter: Sergey Koshcheyev
>     Assignee: Sergey Koshcheyev
>     Priority: Trivial
>      Fix For: 1.2.0.Beta2

>
> The XML schema name of nhibernate-mapping-2.0 should probably be changed to nhibernate-mapping-2.2 to reflect changes made since 1.0.2.

-- 
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-615) Change XML schema names to -2.2

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

     [ http://jira.nhibernate.org/browse/NH-615?page=comments#action_14256 ]
     
Christian Bauer commented on NH-615:
------------------------------------

One other thing: We only incremented the Hibernate DTD version when we made breaking changes. Are you sure that the NH 1.2 schema isn't backwards compatible with NH 1.0? If you just add new stuff to it, which is ignored by NH 1.0, then you can keep the major and minor version.


> Change XML schema names to -2.2
> -------------------------------
>
>          Key: NH-615
>          URL: http://jira.nhibernate.org/browse/NH-615
>      Project: NHibernate
>         Type: Improvement
>   Components: Core
>     Versions: 1.2.0.Alpha1
>     Reporter: Sergey Koshcheyev
>     Assignee: Sergey Koshcheyev
>     Priority: Trivial
>      Fix For: 1.2.0.Beta2

>
> The XML schema name of nhibernate-mapping-2.0 should probably be changed to nhibernate-mapping-2.2 to reflect changes made since 1.0.2.

-- 
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-615) Change XML schema names to -2.2

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

     [ http://jira.nhibernate.org/browse/NH-615?page=comments#action_14255 ]
     
Christian Bauer commented on NH-615:
------------------------------------

The choices are: 

a) increment version numbers: NH 1.2/DTD 2.2, NH 2.0/DTD 3.0
b) align NHibernate version numbers: NH 1.2/DTD 1.2, NH 2.0/DTD 3.0
c) align all version numbers: NH 1.2/DTD 1.2, NH 3.0/DTD 3.0



> Change XML schema names to -2.2
> -------------------------------
>
>          Key: NH-615
>          URL: http://jira.nhibernate.org/browse/NH-615
>      Project: NHibernate
>         Type: Improvement
>   Components: Core
>     Versions: 1.2.0.Alpha1
>     Reporter: Sergey Koshcheyev
>     Assignee: Sergey Koshcheyev
>     Priority: Trivial
>      Fix For: 1.2.0.Beta2

>
> The XML schema name of nhibernate-mapping-2.0 should probably be changed to nhibernate-mapping-2.2 to reflect changes made since 1.0.2.

-- 
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-615) Change XML schema names to -2.2

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

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

The problem is that 1.2 is less than 2.0 which is counter-intuitive, and using 3.0/3.2 would imply that all Hibernate 3.0/3.2 features are available in the mapping while it's not the case, so the number would be essentially random anyway.

I guess I'll go with 1.2 then.

> Change XML schema names to -2.2
> -------------------------------
>
>          Key: NH-615
>          URL: http://jira.nhibernate.org/browse/NH-615
>      Project: NHibernate
>         Type: Improvement
>   Components: Core
>     Versions: 1.2.0.Alpha1
>     Reporter: Sergey Koshcheyev
>     Assignee: Sergey Koshcheyev
>     Priority: Trivial
>      Fix For: 1.2.0.Beta2

>
> The XML schema name of nhibernate-mapping-2.0 should probably be changed to nhibernate-mapping-2.2 to reflect changes made since 1.0.2.

-- 
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-615) Change XML schema names to -2.2

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

     [ http://jira.nhibernate.org/browse/NH-615?page=all ]
     
Christian Bauer reopened NH-615:
--------------------------------

     Assign To: Sergey Koshcheyev

This is not a good choice. Either use 1.2 to match the NHibernate version or 3.0/3.2 to match the Hibernate version. Some random number is no good. Users have to migrate and change it anyway. 

> Change XML schema names to -2.2
> -------------------------------
>
>          Key: NH-615
>          URL: http://jira.nhibernate.org/browse/NH-615
>      Project: NHibernate
>         Type: Improvement
>   Components: Core
>     Versions: 1.2.0.Alpha1
>     Reporter: Sergey Koshcheyev
>     Assignee: Sergey Koshcheyev
>     Priority: Trivial
>      Fix For: 1.2.0.Beta2

>
> The XML schema name of nhibernate-mapping-2.0 should probably be changed to nhibernate-mapping-2.2 to reflect changes made since 1.0.2.

-- 
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-615) Change XML schema names to -2.2

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

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

    Resolution: Fixed

> Change XML schema names to -2.2
> -------------------------------
>
>          Key: NH-615
>          URL: http://jira.nhibernate.org/browse/NH-615
>      Project: NHibernate
>         Type: Improvement
>   Components: Core
>     Versions: 1.2.0.Alpha1
>     Reporter: Sergey Koshcheyev
>     Priority: Trivial
>      Fix For: 1.2.0.Beta2

>
> The XML schema name of nhibernate-mapping-2.0 should probably be changed to nhibernate-mapping-2.2 to reflect changes made since 1.0.2.

-- 
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-779) abstract class not recognized using multiple mapping files

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

     [ http://jira.nhibernate.org/browse/NH-779?page=comments#action_14252 ]
     
Hace commented on NH-779:
-------------------------

One extra note: When an abstract class and (one or more) joined-subclasses are not in one mapping file, but joined-subclasses are in separate mappingfiles AND THE MAPPINGFILE WITH THE JOINEDSUBCLASS IS IN A DIFFERENT ASSEMBLY, the connection between the abstract class and the joined subclasses is lost. 

When trying to read the concreteclassB from NHibernate in code, an error of 'cannot instantiate abstract class' occurs. While when reading ConcreteClassA as an abstractclass, it works perfectly.

So it seems 'adding' concreteclassB as an extension for abstractclass in a separate mapping file which is in another assembly seems to be the problem.

Hope this helps,

> abstract class not recognized using multiple mapping files
> ----------------------------------------------------------
>
>          Key: NH-779
>          URL: http://jira.nhibernate.org/browse/NH-779
>      Project: NHibernate
>         Type: Bug
>     Versions: 1.0.2
>     Reporter: Hace
>  Attachments: JoinedSubClass.zip
>
> When an abstract class and (one or more) joined-subclasses are not in one mapping file, but joined-subclasses are in separate mappingfiles, the connection between the abstract class and the joined subclasses is lost. An error of 'cannot instantiate abstract class' occurs.
> [ AbstractClass.hbm.xml ]
> <hibernate-mapping>
>   <class name="Namespace.Common.AbstractClass, Namespace.Common" table="GeneralItem">
>     <id name="GeneralItemId"  type="Int32" column="GeneralItemId" >
>       <generator class="identity"/>
>     </id>
>     <property name="GeneralText" column="GeneralText" />
>     
>     <joined-subclass name="Namespace.Common.A.ConcreteClassA, Namespace.Common.A" table="ItemsA" extends="Namespace.Common.AbstractClass, Namespace.Common">
>       <key column="GeneralItemId" />
>       ..concrete properties for A..
>     </joined-subclass>
>   
>   </class>
> </hibernate-mapping>
> [ ConcreteClassB.hbm.xml ]
> <hibernate-mapping>
>   <joined-subclass name="Namespace.Common.B.ConcreteClassB, Namespace.Common.B" table="ItemsB" extends="Namespace.Common.AbstractClass, Namespace.Common">
>       <key column="GeneralItemId" />
>       ..concrete properties for B..
>     </joined-subclass>
> </hibernate-mapping>
> Items for ConcreteClassB will not be loaded correctly, only because the joined-subclass is not in the SAME mappingfile as ConcreteClassA ?
> [ Code ]
> List<AbstractClass> itemList = new List<AbstractClass>();
>    ISession session = OurSession.CurrentSession;
>    ICriteria NHibernateCriteria = session.CreateCriteria(typeof(AbstractClass));
>    NHibernateCriteria.Add(Expression.In("GeneralItemId", generalItemIds.ToArray()));
>    try
>    {
>      IEnumerable<AbstractClass> enumerable = (AbstractClass[])ArrayList.Adapter(NHibernateCriteria.List()).ToArray(typeof(AbstractClass));
>      itemList = new List<AbstractClass>(enumerable);
>    }
>    catch(Exception exception)
>    {
>       ... log exception..
>    }
> ......
>   dostuff
>   foreach(ConcreteClassA in itemList)
>  .... 
> [ /code ]

-- 
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-615) Change XML schema names to -2.2

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

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

Sergey Koshcheyev updated NH-615:
---------------------------------

    Description: The XML schema name of nhibernate-mapping-2.0 should probably be changed to nhibernate-mapping-2.2 to reflect changes made since 1.0.2.  (was: The XML schema name of nhibernate-mapping-2.0 should probably be changed to nhibernate-mapping-3.0 to reflect changes made since 1.0.2.)
        Summary: Change XML schema names to -2.2  (was: Change XML schema names to -3.0)

I chose 2.2 because the original intent was to match Hibernate versions. Currently the schema is something in between 2.1 and 3.2.

> Change XML schema names to -2.2
> -------------------------------
>
>          Key: NH-615
>          URL: http://jira.nhibernate.org/browse/NH-615
>      Project: NHibernate
>         Type: Improvement
>   Components: Core
>     Versions: 1.2.0.Alpha1
>     Reporter: Sergey Koshcheyev
>     Priority: Trivial
>      Fix For: 1.2.0.Beta2

>
> The XML schema name of nhibernate-mapping-2.0 should probably be changed to nhibernate-mapping-2.2 to reflect changes made since 1.0.2.

-- 
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-663) Update readme.html

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

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

    Resolution: Fixed

> Update readme.html
> ------------------
>
>          Key: NH-663
>          URL: http://jira.nhibernate.org/browse/NH-663
>      Project: NHibernate
>         Type: Task
>   Components: Documentation
>     Versions: 1.2.0.Alpha1
>     Reporter: Pierre Henri Kuat=C3=A9
>      Fix For: 1.2.0.Beta2

>
> The section "Documentation" is (almost) completely obsolete.
> And it would be nice to add a little introduction... May be copy it from =
the documentation.

--=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-784) NHibernate should throw exception on failed driver load

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

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-412) Improve build files

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

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

    Resolution: Fixed

All done except the doc format splitting, but this isn't that important.

> Improve build files
> -------------------
>
>          Key: NH-412
>          URL: http://jira.nhibernate.org/browse/NH-412
>      Project: NHibernate
>         Type: Task
>   Components: Toolset
>     Versions: 1.0
>     Reporter: Sergey Koshcheyev
>     Assignee: Sergey Koshcheyev
>      Fix For: 1.2.0.Beta2

>
> 1. There is currently a lot of duplication in the build files which should be removed.
> 2. It should be possible to easily build releases (using one command).
> 3. It would be good to accept the database configuration for tests in the form of a .properties or .xml file.
> 4. ...

-- 
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-545) Distributed transactions support

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

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

Sergey Koshcheyev updated NH-545:
---------------------------------

    Fix Version:     (was: 1.2.0.Beta2)

Postponed.

> Distributed transactions support
> --------------------------------
>
>          Key: NH-545
>          URL: http://jira.nhibernate.org/browse/NH-545
>      Project: NHibernate
>         Type: Improvement
>   Components: Core
>     Versions: 1.0.2
>     Reporter: Sergey Koshcheyev
>     Priority: Critical

>
> Currently distributed transactions will not interact correctly with the second-level cache because NHibernate does not get notified when such transaction is completed and SessionImpl.AfterTransactionCompletion is not called then. Probably the only way to get this notification on .NET 1.1 is to implement a compensating resource manager (see namespace System.EnterpriseServices.CompensatingResourceManager). .NET 2.0 appears to have events on Transaction class that could serve this purpose.

-- 
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-783) Port Subquery support for the Criteria API

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

     [ http://jira.nhibernate.org/browse/NH-783?page=3Dcomments#action_1423=
2 ]
    =20
Ayende Rahien commented on NH-783:
----------------------------------

Finished the initial port.
Need to write more tests for it, to ensure that it is working properly and =
how it can be used.

> Port Subquery support for the Criteria API
> ------------------------------------------
>
>          Key: NH-783
>          URL: http://jira.nhibernate.org/browse/NH-783
>      Project: NHibernate
>         Type: New Feature
>   Components: Core
>     Versions: 1.2.0.Beta1
>     Reporter: Ayende Rahien
>     Assignee: Ayende Rahien
>      Fix For: 1.2.0.Beta2

>
> Doing queries on collections using the criteria API at the moment is very=
 hard.
> Looking at the Hibernate source, it looks like they solved the issue with=
 sub queries and detached criteria.
> We need to port the following:
> =E2=80=A2 Subqueries
> =E2=80=A2 Property
> =E2=80=A2 Subquery Expression
>   o PropertySubquery Expression
>   o ExistsSubquery Expression

--=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-783) Port Subquery support for the Criteria API

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

Port Subquery support for the Criteria API
------------------------------------------

         Key: NH-783
         URL: http://jira.nhibernate.org/browse/NH-783
     Project: NHibernate
        Type: New Feature
  Components: Core =20
    Versions: 1.2.0.Beta1   =20
    Reporter: Ayende Rahien
 Assigned to: Ayende Rahien=20
     Fix For: 1.2.0.Beta2


Doing queries on collections using the criteria API at the moment is very h=
ard.
Looking at the Hibernate source, it looks like they solved the issue with s=
ub queries and detached criteria.
We need to port the following:
=E2=80=A2 Subqueries
=E2=80=A2 Property
=E2=80=A2 Subquery Expression
  o PropertySubquery Expression
  o ExistsSubquery Expression


--=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] Resolved: (NH-697) System.MissingMethodException: Method not found: Int32 System.Runtime.CompilerServices.RuntimeHelpers.GetHashCode(System.Object).

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

     [ http://jira.nhibernate.org/browse/NH-697?page=all ]
     
Paul Hatcher resolved NH-697:
-----------------------------

    Resolution: Fixed
     Assign To: Paul Hatcher

I think this is fixed now, still some issues with Medium Trust, but that's a different problem.

> System.MissingMethodException: Method not found: Int32 System.Runtime.CompilerServices.RuntimeHelpers.GetHashCode(System.Object).
> ---------------------------------------------------------------------------------------------------------------------------------
>
>          Key: NH-697
>          URL: http://jira.nhibernate.org/browse/NH-697
>      Project: NHibernate
>         Type: Bug
>   Components: Core
>     Versions: 1.2.0.Alpha1
>     Reporter: David Scott
>     Assignee: Paul Hatcher
>      Fix For: 1.2.0.Beta2

>
> Scenario: I am running multiple web sites/web services under ASP.Net. Each of these use the same data access layer dlls. When accessing the first site everything is OK. Accessing any of the others causes the exception listed in the summary. Once this exception occurs, none of the sites work. Once I run IISReset, I can access one of the sites again.
> The environment is windows XP SP2 running IIS 5, NET 1.1, MS SQL Server 2000.
> I saw on the SourceForge forums that this was a problem about 2 years ago and that a fix was made but nothing after that. http://sourceforge.net/forum/message.php?msg_id=2645644
> I rolled back my nHibernate dlls to version 1.0.2 and they seem to be working fine.
> Stack Trace:
> [MissingMethodException: Method not found: Int32 System.Runtime.CompilerServices.RuntimeHelpers.GetHashCode(System.Object).]
>    NHibernate.IdentityHashCodeProvider.GetHashCode(Object obj) +0
>    System.Collections.Hashtable.GetHash(Object key) +23
>    System.Collections.Hashtable.get_Item(Object key) +62
>    NHibernate.Util.SequencedHashMap.set_Item(Object o, Object value) in c:\net\nhibernate\nhibernate\src\NHibernate\Util\SequencedHashMap.cs:285
>    NHibernate.Util.IdentityMap.set_Item(Object key, Object value) in c:\net\nhibernate\nhibernate\src\NHibernate\Util\IdentityMap.cs:198
>    NHibernate.Impl.SessionImpl.AddEntry(Object obj, Status status, Object[] loadedState, Object id, Object version, LockMode lockMode, Boolean existsInDatabase, IEntityPersister persister, Boolean disableVersionIncrement) in c:\net\nhibernate\nhibernate\src\NHibernate\Impl\SessionImpl.cs:656
>    NHibernate.Impl.SessionImpl.AddUninitializedEntity(EntityKey key, Object obj, LockMode lockMode) in c:\net\nhibernate\nhibernate\src\NHibernate\Impl\SessionImpl.cs:2293
>    NHibernate.Loader.Loader.LoadFromResultSet(IDataReader rs, Int32 i, Object obj, Type instanceClass, EntityKey key, LockMode lockMode, ILoadable rootPersister, ISessionImplementor session) in c:\net\nhibernate\nhibernate\src\NHibernate\Loader\Loader.cs:920
>    NHibernate.Loader.Loader.InstanceNotYetLoaded(IDataReader dr, Int32 i, ILoadable persister, EntityKey key, LockMode lockMode, EntityKey optionalObjectKey, Object optionalObject, IList hydratedObjects, ISessionImplementor session) in c:\net\nhibernate\nhibernate\src\NHibernate\Loader\Loader.cs:884
>    NHibernate.Loader.Loader.GetRow(IDataReader rs, ILoadable[] persisters, EntityKey[] keys, Object optionalObject, EntityKey optionalObjectKey, LockMode[] lockModes, IList hydratedObjects, ISessionImplementor session) in c:\net\nhibernate\nhibernate\src\NHibernate\Loader\Loader.cs:818
>    NHibernate.Loader.Loader.GetRowFromResultSet(IDataReader resultSet, ISessionImplementor session, QueryParameters queryParameters, LockMode[] lockModeArray, EntityKey optionalObjectKey, IList hydratedObjects, EntityKey[] keys, Boolean returnProxies) in c:\net\nhibernate\nhibernate\src\NHibernate\Loader\Loader.cs:294
>    NHibernate.Loader.Loader.DoQuery(ISessionImplementor session, QueryParameters queryParameters, Boolean returnProxies) in c:\net\nhibernate\nhibernate\src\NHibernate\Loader\Loader.cs:425
>    NHibernate.Loader.Loader.DoQueryAndInitializeNonLazyCollections(ISessionImplementor session, QueryParameters queryParameters, Boolean returnProxies) in c:\net\nhibernate\nhibernate\src\NHibernate\Loader\Loader.cs:182
>    NHibernate.Loader.Loader.DoList(ISessionImplementor session, QueryParameters queryParameters) in c:\net\nhibernate\nhibernate\src\NHibernate\Loader\Loader.cs:1636
> [ADOException: could not execute query]
>    DRRSN.ResourceStatus.Domain.Repositories.RespOrgRepository.LoadAll() in c:\inetpub\wwwroot\drrsn.resourcestatus.repository\repositories\resporgrepository.cs:27
>    DRRS.ResourceStatus.BusinessServices.OrdnanceMapperProvider.GetRespOrgs() in C:\Inetpub\wwwroot\DRRS.ResourceStatus.BusinessServices\OrdnanceMapperProvider.cs:233
>    DRRS.ResourceMapper.MapOrdnance.LoadAssignOrdnanceThresholds() in c:\inetpub\wwwroot\resourcemapper\mapordnance.aspx.cs:160
>    DRRS.ResourceMapper.MapOrdnance.Page_Load(Object sender, EventArgs e) in c:\inetpub\wwwroot\resourcemapper\mapordnance.aspx.cs:360
>    System.Web.UI.Control.OnLoad(EventArgs e)
>    System.Web.UI.Control.LoadRecursive()
>    System.Web.UI.Page.ProcessRequestMain()

-- 
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-545) Distributed transactions support

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

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

Sergey Koshcheyev updated NH-545:
---------------------------------

    Summary: Distributed transactions support  (was: Add a CompensatingResourceManager to support distributed transactions)

> Distributed transactions support
> --------------------------------
>
>          Key: NH-545
>          URL: http://jira.nhibernate.org/browse/NH-545
>      Project: NHibernate
>         Type: Improvement
>   Components: Core
>     Versions: 1.0.2
>     Reporter: Sergey Koshcheyev
>     Priority: Critical
>      Fix For: 1.2.0.Beta2

>
> Currently distributed transactions will not interact correctly with the second-level cache because NHibernate does not get notified when such transaction is completed and SessionImpl.AfterTransactionCompletion is not called then. Probably the only way to get this notification on .NET 1.1 is to implement a compensating resource manager (see namespace System.EnterpriseServices.CompensatingResourceManager). .NET 2.0 appears to have events on Transaction class that could serve this purpose.

-- 
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) Creating a proxy instance failed

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

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

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

    Priority: Major  (was: Blocker)

Waiting for a new release of DynamicProxy to fix this.

> Creating a proxy instance failed 
> ---------------------------------
>
>          Key: NH-782
>          URL: http://jira.nhibernate.org/browse/NH-782
>      Project: NHibernate
>         Type: Bug
>   Components: Core
>     Versions: 1.2.0.Beta1
>     Reporter: Pawel Pabich

>
> .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] Created: (NH-782) Creating a proxy instance failed

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

Creating a proxy instance failed 
---------------------------------

         Key: NH-782
         URL: http://jira.nhibernate.org/browse/NH-782
     Project: NHibernate
        Type: Bug
  Components: Core  
    Versions: 1.2.0.Beta1    
    Reporter: Pawel Pabich
    Priority: Blocker


.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