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

[nhibernate-issues] [NHJIRA] Commented: (NH-2784) NHibernate does extra select on each missing relations, even using an eager fetching.

[Peter K. (JIRA) <nh...@gm...>]

    [ http://216.121.112.228/browse/NH-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21350#action_21350 ] 

Peter Kiers commented on NH-2784:
---------------------------------

Yes, both statements are generated by that single Criteria query. And if I'd had more missing relations then I would get another select for each missing one. I will try ByCode mappings.

> NHibernate does extra select on each missing relations, even using an eager fetching.
> -------------------------------------------------------------------------------------
>
>                 Key: NH-2784
>                 URL: http://216.121.112.228/browse/NH-2784
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 3.1.0
>            Reporter: Peter Kiers
>
> When I do an eager join on a relation table, whenever the relation is missing it will generate an additional query for each missing relation.
> Table layout / data:
> TableName: Order
> +----+-----------+--------+
> | Id | OrderName | UserId |
> +----+-----------+--------+
> | 1  | OrderA    | 1      |
> | 2  | OrderB    | 2      |
> | 3  | OrderC    | 3      |  
> +-------------------------+  
> TableName: User
> +----+-----------+
> | Id | UserName  |
> +----+-----------+
> | 1  | User1     |
> | 2  | User2     |
> +----------------+
> var orders = session.CreateCriteria<Order>().SetFetchMode("User", 
> FetchMode.Eager).List<Order>(); 
> Console output:
> NHibernate: SELECT this_.Id as Id0_1_, this_.OrderName as OrderName0_1_, this_.User_id as User3_0_1_, user2_.Id as Id1_0_, user2_.UserName as UserName1_0_ FROM[Order] this_ left outer join [User] user2_ on this_.User_id=user2_.Id
> NHibernate: SELECT user0_.Id as Id1_0_, user0_.UserName as UserName1_0_ FROM [User] user0_ WHERE user0_.Id=@p0;@p0 = 3 [Type: Int32 (0)]
> As you can see it tries to get UserID 3 (which doesn't exists) but it should already know it isn't there as I did a eager fetchmode on that table.

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

        

[nhibernate-issues] [NHJIRA] Commented: (NH-2784) NHibernate does extra select on each missing relations, even using an eager fetching.

[Julian M. (JIRA) <nh...@gm...>]

    [ http://216.121.112.228/browse/NH-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21348#action_21348 ] 

Julian Maughan commented on NH-2784:
------------------------------------

I had a look at your FNH mappings. I don't really known FNH, but it looks correct. Having said that I was unable to reproduce the problem using a ByCode mapping:

mapper.Class<Order>(m =>
{
	m.Table("`Order`");
	m.Id(x => x.Id, map => map.Generator(Generators.Assigned));
	m.Property(model => model.Name);
	m.ManyToOne<User>(model => model.User, map => map.Column("TheUser"));
});

mapper.Class<User>(m =>
{
	m.Table("`User`");
	m.Id(x => x.Id, map => map.Generator(Generators.Assigned));
	m.Property(model => model.Name);
});

Are you saying that both SELECT statements are executed by the Criteria query, or is the second one only executed later on when you access the Order with ID = 3?

> NHibernate does extra select on each missing relations, even using an eager fetching.
> -------------------------------------------------------------------------------------
>
>                 Key: NH-2784
>                 URL: http://216.121.112.228/browse/NH-2784
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 3.1.0
>            Reporter: Peter Kiers
>
> When I do an eager join on a relation table, whenever the relation is missing it will generate an additional query for each missing relation.
> Table layout / data:
> TableName: Order
> +----+-----------+--------+
> | Id | OrderName | UserId |
> +----+-----------+--------+
> | 1  | OrderA    | 1      |
> | 2  | OrderB    | 2      |
> | 3  | OrderC    | 3      |  
> +-------------------------+  
> TableName: User
> +----+-----------+
> | Id | UserName  |
> +----+-----------+
> | 1  | User1     |
> | 2  | User2     |
> +----------------+
> var orders = session.CreateCriteria<Order>().SetFetchMode("User", 
> FetchMode.Eager).List<Order>(); 
> Console output:
> NHibernate: SELECT this_.Id as Id0_1_, this_.OrderName as OrderName0_1_, this_.User_id as User3_0_1_, user2_.Id as Id1_0_, user2_.UserName as UserName1_0_ FROM[Order] this_ left outer join [User] user2_ on this_.User_id=user2_.Id
> NHibernate: SELECT user0_.Id as Id1_0_, user0_.UserName as UserName1_0_ FROM [User] user0_ WHERE user0_.Id=@p0;@p0 = 3 [Type: Int32 (0)]
> As you can see it tries to get UserID 3 (which doesn't exists) but it should already know it isn't there as I did a eager fetchmode on that table.

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

        

[nhibernate-issues] [NHJIRA] Commented: (NH-2784) NHibernate does extra select on each missing relations, even using an eager fetching.

[Peter K. (JIRA) <nh...@gm...>]

    [ http://216.121.112.228/browse/NH-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21347#action_21347 ] 

Peter Kiers commented on NH-2784:
---------------------------------

I have a sample posted on StackOverflow: http://stackoverflow.com/questions/6518244/nhibernate-does-extra-select-on-missing-relations-even-using-eager-fetching
Would that be good enough?

> NHibernate does extra select on each missing relations, even using an eager fetching.
> -------------------------------------------------------------------------------------
>
>                 Key: NH-2784
>                 URL: http://216.121.112.228/browse/NH-2784
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 3.1.0
>            Reporter: Peter Kiers
>
> When I do an eager join on a relation table, whenever the relation is missing it will generate an additional query for each missing relation.
> Table layout / data:
> TableName: Order
> +----+-----------+--------+
> | Id | OrderName | UserId |
> +----+-----------+--------+
> | 1  | OrderA    | 1      |
> | 2  | OrderB    | 2      |
> | 3  | OrderC    | 3      |  
> +-------------------------+  
> TableName: User
> +----+-----------+
> | Id | UserName  |
> +----+-----------+
> | 1  | User1     |
> | 2  | User2     |
> +----------------+
> var orders = session.CreateCriteria<Order>().SetFetchMode("User", 
> FetchMode.Eager).List<Order>(); 
> Console output:
> NHibernate: SELECT this_.Id as Id0_1_, this_.OrderName as OrderName0_1_, this_.User_id as User3_0_1_, user2_.Id as Id1_0_, user2_.UserName as UserName1_0_ FROM[Order] this_ left outer join [User] user2_ on this_.User_id=user2_.Id
> NHibernate: SELECT user0_.Id as Id1_0_, user0_.UserName as UserName1_0_ FROM [User] user0_ WHERE user0_.Id=@p0;@p0 = 3 [Type: Int32 (0)]
> As you can see it tries to get UserID 3 (which doesn't exists) but it should already know it isn't there as I did a eager fetchmode on that table.

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

        

[nhibernate-issues] [NHJIRA] Commented: (NH-2184) Projections / Arithmetic Operators

[Mihai C. (JIRA) <nh...@gm...>]

    [ http://216.121.112.228/browse/NH-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21346#action_21346 ] 

Mihai Codrean commented on NH-2184:
-----------------------------------

Thanks Onur! However, I am not a committer, so we have to wait for one to do this.

http://en.wikipedia.org/wiki/Committer

> Projections / Arithmetic Operators
> ----------------------------------
>
>                 Key: NH-2184
>                 URL: http://216.121.112.228/browse/NH-2184
>             Project:  NHibernate
>          Issue Type: Patch
>          Components: Core
>    Affects Versions: 3.0.0.Alpha1
>            Reporter: Mihai Codrean
>            Priority: Minor
>         Attachments: ArithmeticOperatorProjection.patch
>
>
> Implemented the binary operator projections: addition, subtraction, multiplication and division.
> Basic test included.

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

        

[nhibernate-issues] [NHJIRA] Commented: (NH-2781) linq's OrderBy by a calculated column doesn't work

[Patrick E. (JIRA) <nh...@gm...>]

    [ http://216.121.112.228/browse/NH-2781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21345#action_21345 ] 

Patrick Earl commented on NH-2781:
----------------------------------

Hi dmitry.  It would be great if you could provide a full unit test.  http://blog.patearl.net/2010/12/nhibernate-30-linq.html

> linq's OrderBy by a calculated column doesn't work
> --------------------------------------------------
>
>                 Key: NH-2781
>                 URL: http://216.121.112.228/browse/NH-2781
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Linq Provider
>    Affects Versions: 3.1.0
>            Reporter: dmitry
>            Priority: Major
>
> var a = source.Select(s => new { s.Email, Revenue = s.CompletedOffers.Sum(c => (decimal?)c.Offer.Revenue) })
> .OrderBy(s => s.Revenue).ToList()
> throws QuerySyntaxException. Message: "Exception of type 'Antlr.Runtime.NoViableAltException' was thrown"

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

        

[nhibernate-issues] [NHJIRA] Commented: (NH-2401) Method for specifying IType of LINQ parameter

[Patrick E. (JIRA) <nh...@gm...>]

    [ http://216.121.112.228/browse/NH-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21344#action_21344 ] 

Patrick Earl commented on NH-2401:
----------------------------------

The unit test should at least demonstrate that a parameter that would normally be one type is converted to the new type that has been specified.  This is already handled for simple equality, so it will have to be a more interesting case.

> Method for specifying IType of LINQ parameter
> ---------------------------------------------
>
>                 Key: NH-2401
>                 URL: http://216.121.112.228/browse/NH-2401
>             Project:  NHibernate
>          Issue Type: Improvement
>          Components: Linq Provider
>    Affects Versions: 3.0.0.Beta1
>            Reporter: Patrick Earl
>         Attachments: nh2401MappedAs.patch, nh_2401.patch
>
>


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

        

[nhibernate-issues] [NHJIRA] Commented: (NH-2401) Method for specifying IType of LINQ parameter

[Patrick E. (JIRA) <nh...@gm...>]

    [ http://216.121.112.228/browse/NH-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21343#action_21343 ] 

Patrick Earl commented on NH-2401:
----------------------------------

There needs to be a unit test written.

> Method for specifying IType of LINQ parameter
> ---------------------------------------------
>
>                 Key: NH-2401
>                 URL: http://216.121.112.228/browse/NH-2401
>             Project:  NHibernate
>          Issue Type: Improvement
>          Components: Linq Provider
>    Affects Versions: 3.0.0.Beta1
>            Reporter: Patrick Earl
>         Attachments: nh2401MappedAs.patch, nh_2401.patch
>
>


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

        

[nhibernate-issues] [NHJIRA] Commented: (NH-2184) Projections / Arithmetic Operators

[Onur G. (JIRA) <nh...@gm...>]

    [ http://216.121.112.228/browse/NH-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21342#action_21342 ] 

Onur Gumus commented on NH-2184:
--------------------------------

This looks pretty cool. Would you please commit this ?

> Projections / Arithmetic Operators
> ----------------------------------
>
>                 Key: NH-2184
>                 URL: http://216.121.112.228/browse/NH-2184
>             Project:  NHibernate
>          Issue Type: Patch
>          Components: Core
>    Affects Versions: 3.0.0.Alpha1
>            Reporter: Mihai Codrean
>            Priority: Minor
>         Attachments: ArithmeticOperatorProjection.patch
>
>
> Implemented the binary operator projections: addition, subtraction, multiplication and division.
> Basic test included.

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

        

[nhibernate-issues] [NHJIRA] Commented: (NH-2401) Method for specifying IType of LINQ parameter

[Omri F. (JIRA) <nh...@gm...>]

    [ http://216.121.112.228/browse/NH-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21341#action_21341 ] 

Omri Fima commented on NH-2401:
-------------------------------

Is there anything else needed to be done, except for the patch, in order to close this issue??

> Method for specifying IType of LINQ parameter
> ---------------------------------------------
>
>                 Key: NH-2401
>                 URL: http://216.121.112.228/browse/NH-2401
>             Project:  NHibernate
>          Issue Type: Improvement
>          Components: Linq Provider
>    Affects Versions: 3.0.0.Beta1
>            Reporter: Patrick Earl
>         Attachments: nh2401MappedAs.patch, nh_2401.patch
>
>


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

        

[nhibernate-issues] [NHJIRA] Updated: (NH-2786) Using multiple QueryOver expressions on a polymorphic entity cause duplicate join aliases

[Andy (JIRA) <nh...@gm...>]

     [ http://216.121.112.228/browse/NH-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andy updated NH-2786:
---------------------

    Attachment: NHibernate.Test.zip

Sorry for the entity names!

> Using multiple QueryOver expressions on a polymorphic entity cause duplicate join aliases
> -----------------------------------------------------------------------------------------
>
>                 Key: NH-2786
>                 URL: http://216.121.112.228/browse/NH-2786
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: QueryOver
>    Affects Versions: 3.1.0
>            Reporter: Andy
>            Priority: Major
>         Attachments: NHibernate.Test.zip
>
>
> This may due to my misunderstanding of the way the QueryOver provider works but I am experiencing the following problem.
> I am using the Table-per-subclass strategy.
> I have an abstract entity which is subclassed by 2 other entities.  The abstract entity contains a nested property (PropA) which is referenced by both entities but within their own respective database table.  In an ideal world this property would be contained within the abstract entity table, however, this is a legacy database and I don't have that option!
> When I query from an entity onto the abstract entity and then query onto the PropA entity, I am getting a SQL error due to a duplicate join alias being generated for the table referenced by PropA.
> I have attached a unit test to show this behaviour.  Hopefully it is not something I am doing wrong!

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

        

[nhibernate-issues] [NHJIRA] Created: (NH-2786) Using multiple QueryOver expressions on a polymorphic entity cause duplicate join aliases

[Andy (JIRA) <nh...@gm...>]

Using multiple QueryOver expressions on a polymorphic entity cause duplicate join aliases
-----------------------------------------------------------------------------------------

                 Key: NH-2786
                 URL: http://216.121.112.228/browse/NH-2786
             Project:  NHibernate
          Issue Type: Bug
          Components: QueryOver
    Affects Versions: 3.1.0
            Reporter: Andy
            Priority: Major


This may due to my misunderstanding of the way the QueryOver provider works but I am experiencing the following problem.

I am using the Table-per-subclass strategy.

I have an abstract entity which is subclassed by 2 other entities.  The abstract entity contains a nested property (PropA) which is referenced by both entities but within their own respective database table.  In an ideal world this property would be contained within the abstract entity table, however, this is a legacy database and I don't have that option!

When I query from an entity onto the abstract entity and then query onto the PropA entity, I am getting a SQL error due to a duplicate join alias being generated for the table referenced by PropA.

I have attached a unit test to show this behaviour.  Hopefully it is not something I am doing wrong!

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

        

[nhibernate-issues] [NHJIRA] Created: (NH-2785) StaleStateExceptions discarded on optional <join> table

[Mike A. (JIRA) <nh...@gm...>]

StaleStateExceptions discarded on optional <join> table
-------------------------------------------------------

                 Key: NH-2785
                 URL: http://216.121.112.228/browse/NH-2785
             Project:  NHibernate
          Issue Type: Bug
          Components: Core
    Affects Versions: 3.1.0
            Reporter: Mike Abraham
            Priority: Major


When extending an existing table via an optional <join> (see abridged mapping below) and specifying optimistic locking via optimistic- 
lock="dirty" dynamic-update="true" (since <version> cannot be used in a <join>), updates to existing records in the join table that have been modified by another user, correctly throw a StaleStateException.  However, the exception is caught and discarded because IsNullableTable is true (because the <join> is optional) in the following code from AbstractEntityPersister. 

                protected bool Check(int rows, object id, int tableNumber, 
IExpectation expectation, IDbCommand statement) 
                { 
                        try 
                        { 
                                expectation.VerifyOutcomeNonBatched(rows, statement); 
                        } 
                        catch (StaleStateException) // THE StaleStateException IS THROWN
                        { 
                                if (!IsNullableTable(tableNumber)) // ... BUT IS DISCARDED HERE
                                { 
                                        if (Factory.Statistics.IsStatisticsEnabled) 
                                                Factory.StatisticsImplementor.OptimisticFailure(EntityName); 


                                        throw new StaleObjectStateException(EntityName, id); 
                                } 
                        } 
                        catch (TooManyRowsAffectedException ex) 
                        { 
                                throw new HibernateException("Duplicate identifier in table for: " 
+ MessageHelper.InfoString(this, id, Factory), ex); 
                        } 
                        catch (Exception) 
                        { 
                                return false; 
                        } 
                        return true; 
                } 


        <class name="Case" schema="Cases" table="`Case`" optimistic- 
lock="dirty" dynamic-update="true"> 


                <id name="CaseId" > 
                  <generator class="identity"/> 
                </id> 
                <property name="CaseCode"/> 
                <property name="MarketingCaseCode"/> 
                <property name="Name" column="CaseName"/> 
                <property name="Status" column="StatusId"/> 


                <join schema="CSA" table="CaseEx" optional="true"> 
                        <key column="CaseId"/> 


                        <property name="Details"/> 
                        <property name="Template"/> 
                </join> 
        </class> 




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

        

[nhibernate-issues] [NHJIRA] Commented: (NH-2784) NHibernate does extra select on each missing relations, even using an eager fetching.

[Julian M. (JIRA) <nh...@gm...>]

    [ http://216.121.112.228/browse/NH-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21339#action_21339 ] 

Julian Maughan commented on NH-2784:
------------------------------------

You need to provide more details before we can help. Your mappings would be a start. Also, what is generating the second SELECT statement? Even better is a test case that reproduces the issue: http://nhforge.org/blogs/nhibernate/archive/2008/10/04/the-best-way-to-solve-nhibernate-bugs-submit-good-unit-test.aspx

> NHibernate does extra select on each missing relations, even using an eager fetching.
> -------------------------------------------------------------------------------------
>
>                 Key: NH-2784
>                 URL: http://216.121.112.228/browse/NH-2784
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 3.1.0
>            Reporter: Peter Kiers
>
> When I do an eager join on a relation table, whenever the relation is missing it will generate an additional query for each missing relation.
> Table layout / data:
> TableName: Order
> +----+-----------+--------+
> | Id | OrderName | UserId |
> +----+-----------+--------+
> | 1  | OrderA    | 1      |
> | 2  | OrderB    | 2      |
> | 3  | OrderC    | 3      |  
> +-------------------------+  
> TableName: User
> +----+-----------+
> | Id | UserName  |
> +----+-----------+
> | 1  | User1     |
> | 2  | User2     |
> +----------------+
> var orders = session.CreateCriteria<Order>().SetFetchMode("User", 
> FetchMode.Eager).List<Order>(); 
> Console output:
> NHibernate: SELECT this_.Id as Id0_1_, this_.OrderName as OrderName0_1_, this_.User_id as User3_0_1_, user2_.Id as Id1_0_, user2_.UserName as UserName1_0_ FROM[Order] this_ left outer join [User] user2_ on this_.User_id=user2_.Id
> NHibernate: SELECT user0_.Id as Id1_0_, user0_.UserName as UserName1_0_ FROM [User] user0_ WHERE user0_.Id=@p0;@p0 = 3 [Type: Int32 (0)]
> As you can see it tries to get UserID 3 (which doesn't exists) but it should already know it isn't there as I did a eager fetchmode on that table.

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

        

[nhibernate-issues] [NHJIRA] Created: (NH-2784) NHibernate does extra select on each missing relations, even using an eager fetching.

[Peter K. (JIRA) <nh...@gm...>]

NHibernate does extra select on each missing relations, even using an eager fetching.
-------------------------------------------------------------------------------------

                 Key: NH-2784
                 URL: http://216.121.112.228/browse/NH-2784
             Project:  NHibernate
          Issue Type: Bug
          Components: Core
    Affects Versions: 3.1.0
            Reporter: Peter Kiers


When I do an eager join on a relation table, whenever the relation is missing it will generate an additional query for each missing relation.

Table layout / data:
TableName: Order
+----+-----------+--------+
| Id | OrderName | UserId |
+----+-----------+--------+
| 1  | OrderA    | 1      |
| 2  | OrderB    | 2      |
| 3  | OrderC    | 3      |  
+-------------------------+  

TableName: User
+----+-----------+
| Id | UserName  |
+----+-----------+
| 1  | User1     |
| 2  | User2     |
+----------------+

var orders = session.CreateCriteria<Order>().SetFetchMode("User", 
FetchMode.Eager).List<Order>(); 

Console output:
NHibernate: SELECT this_.Id as Id0_1_, this_.OrderName as OrderName0_1_, this_.User_id as User3_0_1_, user2_.Id as Id1_0_, user2_.UserName as UserName1_0_ FROM[Order] this_ left outer join [User] user2_ on this_.User_id=user2_.Id
NHibernate: SELECT user0_.Id as Id1_0_, user0_.UserName as UserName1_0_ FROM [User] user0_ WHERE user0_.Id=@p0;@p0 = 3 [Type: Int32 (0)]

As you can see it tries to get UserID 3 (which doesn't exists) but it should already know it isn't there as I did a eager fetchmode on that table.

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

        

[nhibernate-issues] [NHJIRA] Updated: (NH-2783) property-ref and dynamic-component

[Christophe (JIRA) <nh...@gm...>]

     [ http://216.121.112.228/browse/NH-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christophe updated NH-2783:
---------------------------

    Attachment: mapping.hbm.xml
                bar.cs
                foo.cs

> property-ref and dynamic-component
> ----------------------------------
>
>                 Key: NH-2783
>                 URL: http://216.121.112.228/browse/NH-2783
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 3.1.0
>            Reporter: Christophe
>            Priority: Major
>         Attachments: bar.cs, foo.cs, mapping.hbm.xml
>
>
> Many-to-one association that references a dynamic-component property throws an error "property-ref [DynValString2] not found on entity [NHibernateTest.bar]"
> Mapping used : 
>   <class name="foo">
>     <id type="int" name="Id">
>       <column name="Id"/>
>       <generator class="native"/>
>     </id>
>     <dynamic-component name="MyProps">
>       <many-to-one name="DynPointer" class="bar" property-ref="DynValString2"/>
>     </dynamic-component>
>   </class>
>   <class name="bar">
>     <id type="int" name="Id">
>       <column name="Id"/>
>       <generator class="native"/>
>     </id>
>     <dynamic-component name="MyProps">
>       <property name="DynValString2" type="string" unique="1"/>
>     </dynamic-component>
>   </class>
> If I move property DynValString2 out of the dynamic-component, it works.

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

        

[nhibernate-issues] [NHJIRA] Created: (NH-2783) property-ref and dynamic-component

[Christophe (JIRA) <nh...@gm...>]

property-ref and dynamic-component
----------------------------------

                 Key: NH-2783
                 URL: http://216.121.112.228/browse/NH-2783
             Project:  NHibernate
          Issue Type: Bug
          Components: Core
    Affects Versions: 3.1.0
            Reporter: Christophe
            Priority: Major


Many-to-one association that references a dynamic-component property throws an error "property-ref [DynValString2] not found on entity [NHibernateTest.bar]"

Mapping used : 

  <class name="foo">
    <id type="int" name="Id">
      <column name="Id"/>
      <generator class="native"/>
    </id>

    <dynamic-component name="MyProps">
      <many-to-one name="DynPointer" class="bar" property-ref="DynValString2"/>
    </dynamic-component>
  </class>

  <class name="bar">
    <id type="int" name="Id">
      <column name="Id"/>
      <generator class="native"/>
    </id>
    <dynamic-component name="MyProps">
      <property name="DynValString2" type="string" unique="1"/>
    </dynamic-component>
  </class>

If I move property DynValString2 out of the dynamic-component, it works.



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

        

[nhibernate-issues] [NHJIRA] Commented: (NH-2176) Consecutive TransactionScopes cannot be used in same NHibernate session

[Silviu P. (JIRA) <nh...@gm...>]

    [ http://216.121.112.228/browse/NH-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21338#action_21338 ] 

Silviu Paragina commented on NH-2176:
-------------------------------------

The issue seems to still happen in the 3.0 version from what I have seen.

The IEnlistmentNotiifcation is also called on a different thread.
The bug is also reproducible if you dispose the session right after the transaction.

As a configuration workaround you could add "<property name="connection.release_mode">on_close</property>" in the configuration, and make sure you always dispose the session after you finish a workload.

> Consecutive TransactionScopes cannot be used in same NHibernate session
> -----------------------------------------------------------------------
>
>                 Key: NH-2176
>                 URL: http://216.121.112.228/browse/NH-2176
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.1.2.GA
>            Reporter: Norman
>            Assignee: Julian Maughan
>            Priority: Major
>         Attachments: Fixture.cs, Mappings.hbm.xml, Model.cs
>
>
> "Connection is Closed" exception is thrown when a subsequent TransactionScope is used within the same the same session. This seems to be specific to Oracle (I've tested SQL Server and there was no issue).
> The problem seems to be caused because the Transaction.TransactionCompleted event is fired on a different thread when using TransactionScope. 
> When NHibernate handles this event it closes the database connection. However by this time another transaction and database call has already started on the main thread. NHibernate has opened the connection for the second call and expects it to remain open. 
> Detailed information is below. 
> Versions:
> .NET 3.5
> Oracle 10g
> Timeline: 
> MAIN THREAD: SessionFactory.OpenSession() // without passing a connection 
> MAIN THREAD: using (new TransactionScope()) 
> MAIN THREAD:    SomeDatabaseWork(); 
> MAIN THREAD:         // NHibernate opens connection 
> MAIN THREAD:         // NHibernate does database work 
> MAIN THREAD:         // NHibernate closes connection 
> MAIN THREAD:    // SomeDatabaseWork(); returns 
> MAIN THREAD:    TransactionScope.Complete(); 
> MAIN THREAD: TransactionScope.Dispose(); // from using 
> MAIN THREAD: using (new TransactionScope()) 
> MAIN THREAD:    MoreDatabaseWork(); 
> MAIN THREAD:         // NHibernate opens connection 
> ANOTHER THREAD: Transaction.TrasactionCompleted event fires 
> ANOTHER THREAD: Nhibernate event handler closes connection 
> MAIN THREAD:         // NHibernate does database work --> EXCEPTION HERE 
> Exception: 
> NHibernate.ADOException was unhandled by user code 
>   Message="could not execute query\r\n[ select * from blah]" 
>   Source="NHibernate" 
>   SqlString="select * from blah" 
>   StackTrace: 
>        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`1 querySpaces, IType[] 
> resultTypes) 
>        at 
> NHibernate.Loader.Criteria.CriteriaLoader.List(ISessionImplementor 
> session) 
>        at NHibernate.Impl.SessionImpl.List(CriteriaImpl criteria, 
> IList results) 
>        at NHibernate.Impl.CriteriaImpl.List(IList results) 
>        at NHibernate.Impl.CriteriaImpl.List[T]() 
>        at 
> NHibernate.Linq.Visitors.ImmediateResultsVisitor`1.GetElementList(MethodCal­lExpression 
> call, Int32 count) 
>        at 
> NHibernate.Linq.Visitors.ImmediateResultsVisitor`1.HandleFirstOrDefaultCall­(MethodCallExpression 
> call) 
>        at 
> NHibernate.Linq.Visitors.ImmediateResultsVisitor`1.VisitMethodCall(MethodCa­llExpression 
> call) 
>        at NHibernate.Linq.Visitors.ExpressionVisitor.Visit(Expression 
> exp) 
>        at 
> NHibernate.Linq.Visitors.NHibernateExpressionVisitor.Visit(Expression 
> exp) 
>        at 
> NHibernate.Linq.Visitors.ImmediateResultsVisitor`1.GetResults(MethodCallExp­ression 
> expr) 
>        at 
> NHibernate.Linq.Visitors.RootVisitor.HandleImmediateResultsCall(MethodCallE­xpression 
> call) 
>        at 
> NHibernate.Linq.Visitors.RootVisitor.VisitMethodCall(MethodCallExpression 
> expr) 
>        at NHibernate.Linq.Visitors.ExpressionVisitor.Visit(Expression 
> exp) 
>        at 
> NHibernate.Linq.Visitors.NHibernateExpressionVisitor.Visit(Expression 
> exp) 
>        at 
> NHibernate.Linq.Visitors.NHibernateQueryTranslator.TranslateInternal(Expres­sion 
> expression) 
>        at 
> NHibernate.Linq.Visitors.NHibernateQueryTranslator.Translate(Expression 
> expression, QueryOptions queryOptions) 
>        at 
> NHibernate.Linq.NHibernateQueryProvider.TranslateExpression(Expression 
> expression) 
>        at NHibernate.Linq.NHibernateQueryProvider.Execute(Expression 
> expression) 
>        at 
> NHibernate.Linq.QueryProvider.System.Linq.IQueryProvider.Execute[T] 
> (Expression expression) 
>        at System.Linq.Queryable.FirstOrDefault[TSource](IQueryable`1 
> source) 
>        at our code 
>        at SyncInvokeGetGroupWellStates(Object , Object[] , Object[] ) 
>        at 
> System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object 
> instance, Object[] inputs, Object[]& outputs) 
>        at 
> System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(Message­Rpc& 
> rpc) 
>   InnerException: System.InvalidOperationException 
>        Message="Invalid operation. The connection is closed." 
>        Source="System.Data.OracleClient" 
>        StackTrace: 
>             at 
> System.Data.OracleClient.OracleConnection.GetOpenInternalConnection() 
>             at 
> System.Data.OracleClient.OracleConnection.get_ErrorHandle() 
>             at 
> System.Data.OracleClient.OracleDataReader.FillColumnInfo() 
>             at 
> System.Data.OracleClient.OracleDataReader..ctor(OracleCommand command, 
> OciStatementHandle statementHandle, String statementText, 
> CommandBehavior commandBehavior) 
>             at 
> System.Data.OracleClient.OracleCommand.ExecuteReader(CommandBehavior 
> behavior) 
>             at 
> System.Data.OracleClient.OracleCommand.ExecuteDbDataReader(CommandBehavior 
> behavior) 
>             at 
> System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader() 
>             at 
> NHibernate.AdoNet.AbstractBatcher.ExecuteReader(IDbCommand cmd) 
>             at NHibernate.Loader.Loader.GetResultSet(IDbCommand st, 
> Boolean autoDiscoverTypes, Boolean callable, RowSelection selection, 
> ISessionImplementor session) 
>             at NHibernate.Loader.Loader.DoQuery(ISessionImplementor 
> session, QueryParameters queryParameters, Boolean returnProxies) 
>             at 
> NHibernate.Loader.Loader.DoQueryAndInitializeNonLazyCollections(ISessionImp­lementor 
> session, QueryParameters queryParameters, Boolean returnProxies) 
>             at NHibernate.Loader.Loader.DoList(ISessionImplementor 
> session, QueryParameters queryParameters) 
>        InnerException: 
> Possible Workarounds: 
> 1. Provide NHibernate with a connection when opening a session; or 
> 2. Create a TransactionScope for duration of session (not ideal)
> Forum Link:
> http://groups.google.com/group/nhusers/browse_thread/thread/160bad2228c15fc6?fwc=1

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

       

[nhibernate-issues] [NHJIRA] Updated: (NH-2571) Full PostgreSQL Support

[Patrick E. (JIRA) <nh...@gm...>]

     [ http://216.121.112.228/browse/NH-2571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Patrick Earl updated NH-2571:
-----------------------------

    Comment: was deleted

(was: Test comment.)

> Full PostgreSQL Support
> -----------------------
>
>                 Key: NH-2571
>                 URL: http://216.121.112.228/browse/NH-2571
>             Project:  NHibernate
>          Issue Type: Improvement
>          Components: DataProviders / Dialects, Tests
>    Affects Versions: 3.0.0.GA, 3.1.0
>            Reporter: Patrick Earl
>            Assignee: Patrick Earl
>
> The aim here is to have all unit tests passing. Whatever functionality should be implemented will be. After that, if the functionality is simply unsupportable, ignore the test.
> Limitations encountered along the way:
> * PostgreSQL does not support null characters in unicode strings.
> * Can't select for update across an outer join.  This means inherited entities can't be locked.

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

        

[nhibernate-issues] [NHJIRA] Created: (NH-2782) Linq: selecting into a new array doesn't work

[dmitry (JIRA) <nh...@gm...>]

Linq: selecting into a new array doesn't work
---------------------------------------------

                 Key: NH-2782
                 URL: http://216.121.112.228/browse/NH-2782
             Project:  NHibernate
          Issue Type: Bug
          Components: Linq Provider
    Affects Versions: 3.1.0
            Reporter: dmitry
            Priority: Major


from u in source
select new { Cells = new object[] { u.Id, u.Name } };

NotSupportedException is thrown. Message: NewArrayInitExpression

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

        

[nhibernate-issues] [NHJIRA] Commented: (NHE-13) Updated entity not being versioned DTC/AutoFlush

[Roger (JIRA) <nh...@gm...>]

    [ http://216.121.112.228/browse/NHE-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21337#action_21337 ] 

Roger commented on NHE-13:
--------------------------

Are you sure the problem is caused by DTC tran or do you have the same problem using plain NH transaction + Flushmode.auto?

If possible, please attach an isolated unit test for your problem.

Thanks.

> Updated entity not being versioned DTC/AutoFlush
> ------------------------------------------------
>
>                 Key: NHE-13
>                 URL: http://216.121.112.228/browse/NHE-13
>             Project: NHibernate.Envers
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0 CR 1
>            Reporter: Konstantin Polyzois
>            Priority: Minor
>
> There seems to be a problem with versioning when doing an update. I am using FlushMode.AUTO and System.Transactions.Transaction.Current (DTC transactions).
> The sequence is:
> 1 I commit my trans
> 2 DTC calls hibernate
> 3 Hibernate checks if there are any doBeforeTransactionCompletion
> 4 Autoflush is run which updates my Entity
> 5 NHibernate calls OnPostUpdate listeners
> 6 Envers registers for doBeforeTransactionCompletion
> If I add a flush before I commit everything works as expected Envers registers earlier and hence will be called at the right momment.

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

        

[nhibernate-issues] [NHJIRA] Created: (NHE-13) Updated entity not being versioned DTC/AutoFlush

[Konstantin P. (JIRA) <nh...@gm...>]

Updated entity not being versioned DTC/AutoFlush
------------------------------------------------

                 Key: NHE-13
                 URL: http://216.121.112.228/browse/NHE-13
             Project: NHibernate.Envers
          Issue Type: Bug
          Components: Core
    Affects Versions: 1.0 CR 1
            Reporter: Konstantin Polyzois
            Priority: Minor


There seems to be a problem with versioning when doing an update. I am using FlushMode.AUTO and System.Transactions.Transaction.Current (DTC transactions).
The sequence is:

1 I commit my trans
2 DTC calls hibernate
3 Hibernate checks if there are any doBeforeTransactionCompletion
4 Autoflush is run which updates my Entity
5 NHibernate calls OnPostUpdate listeners
6 Envers registers for doBeforeTransactionCompletion

If I add a flush before I commit everything works as expected Envers registers earlier and hence will be called at the right momment.





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

        

[nhibernate-issues] [NHJIRA] Commented: (NH-2571) Full PostgreSQL Support

[Patrick E. (JIRA) <nh...@gm...>]

    [ http://216.121.112.228/browse/NH-2571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21336#action_21336 ] 

Patrick Earl commented on NH-2571:
----------------------------------

Test comment.

> Full PostgreSQL Support
> -----------------------
>
>                 Key: NH-2571
>                 URL: http://216.121.112.228/browse/NH-2571
>             Project:  NHibernate
>          Issue Type: Improvement
>          Components: DataProviders / Dialects, Tests
>    Affects Versions: 3.0.0.GA, 3.1.0
>            Reporter: Patrick Earl
>            Assignee: Patrick Earl
>
> The aim here is to have all unit tests passing. Whatever functionality should be implemented will be. After that, if the functionality is simply unsupportable, ignore the test.
> Limitations encountered along the way:
> * PostgreSQL does not support null characters in unicode strings.
> * Can't select for update across an outer join.  This means inherited entities can't be locked.

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

        

[nhibernate-issues] [NHJIRA] Created: (NH-2781) linq's OrderBy by a calculated column doesn't work

[dmitry (JIRA) <nh...@gm...>]

linq's OrderBy by a calculated column doesn't work
--------------------------------------------------

                 Key: NH-2781
                 URL: http://216.121.112.228/browse/NH-2781
             Project:  NHibernate
          Issue Type: Bug
          Components: Linq Provider
    Affects Versions: 3.1.0
            Reporter: dmitry
            Priority: Major


var a = source.Select(s => new { s.Email, Revenue = s.CompletedOffers.Sum(c => (decimal?)c.Offer.Revenue) })
.OrderBy(s => s.Revenue).ToList()

throws QuerySyntaxException. Message: "Exception of type 'Antlr.Runtime.NoViableAltException' was thrown"

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

        

[nhibernate-issues] [NHJIRA] Created: (NH-2780) Linq nested sum doesn't work

[dmitry (JIRA) <nh...@gm...>]

Linq nested sum doesn't work
----------------------------

                 Key: NH-2780
                 URL: http://216.121.112.228/browse/NH-2780
             Project:  NHibernate
          Issue Type: Bug
          Components: Linq Provider
    Affects Versions: 3.1.0
            Reporter: dmitry
            Priority: Major


var a = source.Sum(s => s.User.CompletedOffers.Sum(c => (decimal?)c.Offer.Revenue));

this throws the RewriteEmptyStreamException exception. Message: rule x

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

        

[nhibernate-issues] [NHJIRA] Resolved: (NH-2118) GroupBy without Select doesnt work

[Patrick E. (JIRA) <nh...@gm...>]

     [ http://216.121.112.228/browse/NH-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Patrick Earl resolved NH-2118.
------------------------------

       Resolution: Fixed
    Fix Version/s: 3.2.0CR1
         Assignee: Patrick Earl

> GroupBy without Select doesnt work
> ----------------------------------
>
>                 Key: NH-2118
>                 URL: http://216.121.112.228/browse/NH-2118
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Linq Provider
>    Affects Versions: 3.0.0.Alpha1
>            Reporter: Jose F. Romaniello
>            Assignee: Patrick Earl
>             Fix For: 3.2.0CR1
>
>         Attachments: test-2118.patch
>
>
> A query like this doesn't work:
> session.Query<Person>().GroupBy(p => p.LastName).ToArray() //doesn't work
> however there is a temporary workaround:
> session.Query<Person>().GroupBy(p => p.LastName).Select(g => g).ToArray() // this work.

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