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

[nhibernate-issues] [NHJIRA] Commented: (NH-2099) Linq Expressions and case sensitivity

[Mattias Ö. (J. <nh...@gm...>]

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

Mattias Öhrn commented on NH-2099:
----------------------------------

I actually have a scenario where this would be useful even if you have full control of the DB structure. In MySQL (and maybe other DB brands) the collation of a column is used for all comparisons, including unique constraint checking. So if a unique constraint must be case sensitive a case sensitive collation must be used even if you know that you want to run case insensitive queries towards this column.

> Linq Expressions and case sensitivity
> -------------------------------------
>
>                 Key: NH-2099
>                 URL: http://216.121.112.228/browse/NH-2099
>             Project:  NHibernate
>          Issue Type: New Feature
>          Components: Linq Provider
>    Affects Versions: 3.0.0.Alpha1
>            Reporter: Jose F. Romaniello
>            Priority: Minor
>
> The following query:
> persons.Where(p => p.Nombre.StartsWith("a"))
> in objects is case-sensitive. And I would like in nhibernate be case sensitive too.
> otherwise:
> persons.Where(p => p.Nombre.StartsWith("a", StringComparison.OrdinalIgnoreCase))
> In sql server it is possible to change the "coalesce" in the where statement. I don't know for other providers.
> The same for others string operators.

-- 
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-2761) SchemaUpdate Generates Additional Relations Mandatory on Both Endpoints

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

SchemaUpdate Generates Additional Relations Mandatory on Both Endpoints
-----------------------------------------------------------------------

                 Key: NH-2761
                 URL: http://216.121.112.228/browse/NH-2761
             Project:  NHibernate
          Issue Type: Bug
          Components: Tests
    Affects Versions: 3.2.0Beta1
            Reporter: Ricardo Peres
         Attachments: bd.png, NHTest.zip

SchemaUpdate generates invalid schema. Additional relations, mandatory on both sides, are added to the following mapping (also attached), please see the attached picture:

<hibernate-mapping default-lazy="false" namespace="NHTest" assembly="NHTest" xmlns="urn:nhibernate-mapping-2.2">
	<class name="A" lazy="false" table="`A`">
		<id name="Id" access="property" column="`A_ID`">
			<generator class="hilo" />
		</id>
		<property name="AProperty" column="`A_PROPERTY`" length="50"/>
		<many-to-one name="B" class="B" column="`B_ID`" not-null="false" />
		<many-to-one name="C" class="C" column="`C_ID`" not-null="false" />
	</class>
</hibernate-mapping>

<hibernate-mapping default-lazy="false" namespace="NHTest" assembly="NHTest" xmlns="urn:nhibernate-mapping-2.2">
	<class name="B" lazy="false" table="`B`">
		<id name="Id" access="property" column="`B_ID`">
			<generator class="hilo" />
		</id>
		<property name="BProperty" column="`B_PROPERTY`" length="50"/>
		<set name="As" inverse="true">
			<key column="`B_ID`"/>
			<one-to-many class="A"/>
		</set>
		<many-to-one name="C" class="C" column="`C_ID`" not-null="false" fetch="select"/>
	</class>
</hibernate-mapping>

<hibernate-mapping default-lazy="false" namespace="NHTest" assembly="NHTest" xmlns="urn:nhibernate-mapping-2.2">
	<class name="C" lazy="false" table="`C`">
		<id name="Id" access="property" column="`C_ID`">
			<generator class="hilo" />
		</id>
		<property name="CProperty" column="`C_PROPERTY`" length="50"/>
		<set name="As" inverse="true">
			<key column="`A_ID`"/>
			<one-to-many class="A"/>
		</set>
		<set name="Bs" inverse="true">
			<key column="`B_ID`"/>
			<one-to-many class="B"/>
		</set>
	</class>
</hibernate-mapping>

A test case is included which only generates the schema.

-- 
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] Assigned: (NH-2435) No order by clause generated with self referencing orderby clause.

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

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

Patrick Earl reassigned NH-2435:
--------------------------------

    Assignee: Patrick Earl

> No order by clause generated with self referencing orderby clause.
> ------------------------------------------------------------------
>
>                 Key: NH-2435
>                 URL: http://216.121.112.228/browse/NH-2435
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Linq Provider
>    Affects Versions: 3.0.0.CR1
>            Reporter: Patrick Earl
>            Assignee: Patrick Earl
>            Priority: Minor
>


-- 
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-2427) Support querying HasValue on Nullable types

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

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

Patrick Earl resolved NH-2427.
------------------------------

       Resolution: Fixed
    Fix Version/s: 3.2.0Beta2

This was fixed in ReLinq 1.13.92.  We're now at 1.13.100.

> Support querying HasValue on Nullable types
> -------------------------------------------
>
>                 Key: NH-2427
>                 URL: http://216.121.112.228/browse/NH-2427
>             Project:  NHibernate
>          Issue Type: Improvement
>          Components: Linq Provider
>    Affects Versions: 3.0.0.CR1
>            Reporter: Patrick Earl
>             Fix For: 3.2.0Beta2
>
>


-- 
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-2760) Unable to order by sub-collection's count

[Kelly S. (JIRA) <nh...@gm...>]

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

Kelly Stuard commented on NH-2760:
----------------------------------

Unit tests and exception attached. Please let me know if I can provide any additional information.

> Unable to order by sub-collection's count
> -----------------------------------------
>
>                 Key: NH-2760
>                 URL: http://216.121.112.228/browse/NH-2760
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Linq Provider
>    Affects Versions: 3.2.0Beta1
>            Reporter: Kelly Stuard
>            Priority: Major
>         Attachments: NH2760-Exception.txt, NH2760.zip
>
>
> (Attaching unit tests and exception shortly.)
> // Many-to-many association between User and UserGroup.
> var query =
> 	from ug in session.Query<UserGroup>()
> 	orderby ug.Users.Count()
> 	select ug;
> query.ToList();
> // 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] Updated: (NH-2760) Unable to order by sub-collection's count

[Kelly S. (JIRA) <nh...@gm...>]

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

Kelly Stuard updated NH-2760:
-----------------------------

    Attachment: NH2760.zip
                NH2760-Exception.txt

> Unable to order by sub-collection's count
> -----------------------------------------
>
>                 Key: NH-2760
>                 URL: http://216.121.112.228/browse/NH-2760
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Linq Provider
>    Affects Versions: 3.2.0Beta1
>            Reporter: Kelly Stuard
>            Priority: Major
>         Attachments: NH2760-Exception.txt, NH2760.zip
>
>
> (Attaching unit tests and exception shortly.)
> // Many-to-many association between User and UserGroup.
> var query =
> 	from ug in session.Query<UserGroup>()
> 	orderby ug.Users.Count()
> 	select ug;
> query.ToList();
> // 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-2760) Unable to order by sub-collection's count

[Kelly S. (JIRA) <nh...@gm...>]

Unable to order by sub-collection's count
-----------------------------------------

                 Key: NH-2760
                 URL: http://216.121.112.228/browse/NH-2760
             Project:  NHibernate
          Issue Type: Bug
          Components: Linq Provider
    Affects Versions: 3.2.0Beta1
            Reporter: Kelly Stuard
            Priority: Major


(Attaching unit tests and exception shortly.)

// Many-to-many association between User and UserGroup.
var query =
	from ug in session.Query<UserGroup>()
	orderby ug.Users.Count()
	select ug;

query.ToList();
// 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] Resolved: (NH-2318) Template functions fail with certain combinations of arguments.

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

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

Patrick Earl resolved NH-2318.
------------------------------

       Resolution: Fixed
    Fix Version/s: 3.2.0Beta2

> Template functions fail with certain combinations of arguments.
> ---------------------------------------------------------------
>
>                 Key: NH-2318
>                 URL: http://216.121.112.228/browse/NH-2318
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 3.0.0.Alpha2
>            Reporter: Patrick Earl
>            Assignee: Patrick Earl
>             Fix For: 3.2.0Beta2
>
>         Attachments: HqlParameterReordering.patch, ISqlFunctionParameterReordering.patch, SqlFunctionProjectionFix.patch, TrimFunctionsTest.patch, TrimFunctionsTest2.patch
>
>
> Some template functions such as TRIM() fail since they use repeated arguments in the template.  Additionally, the LEADING and TRAILING trim emulation functions have their ltrim and rtrim reversed.  Included is a unit test that demonstrates that failure.

-- 
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-2759) Any() in where clause along with property access confuses parser.

[Kelly S. (JIRA) <nh...@gm...>]

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

Kelly Stuard updated NH-2759:
-----------------------------

    Attachment: NH2759.zip

2 unit tests: 1 passing, 1 failing

Notice how adding the property in the where clause confuses the parser in the any portion.

> Any() in where clause along with property access confuses parser.
> -----------------------------------------------------------------
>
>                 Key: NH-2759
>                 URL: http://216.121.112.228/browse/NH-2759
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Linq Provider
>    Affects Versions: 3.2.0Beta1
>            Reporter: Kelly Stuard
>         Attachments: NH2759-Exception.txt, NH2759.zip
>
>
> (I have a passing and a failing test case and the exception lined up to attach, shortly.)
> The following code throws an exception; the parser thinks the property in the any clause should be an asset, not a library permission. However, if I remove the property access in the where clause, the parser figures out everything, fine.
> var recentlyViewed =
> 	from voa in session.Query<ViewsOnAsset>()
> 	select voa.Asset;
> var query =
> 	from asset in recentlyViewed
> 	let library = asset.Library
> 	where library.LibraryType == 1 && library.LibraryPermissions.Any(p =>
> 		p.CanViewAssets)
> 	select asset;

-- 
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-2759) Any() in where clause along with property access confuses parser.

[Kelly S. (JIRA) <nh...@gm...>]

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

Kelly Stuard updated NH-2759:
-----------------------------

    Attachment: NH2759-Exception.txt

This is the exception thrown on the failing unit test.

> Any() in where clause along with property access confuses parser.
> -----------------------------------------------------------------
>
>                 Key: NH-2759
>                 URL: http://216.121.112.228/browse/NH-2759
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Linq Provider
>    Affects Versions: 3.2.0Beta1
>            Reporter: Kelly Stuard
>         Attachments: NH2759-Exception.txt
>
>
> (I have a passing and a failing test case and the exception lined up to attach, shortly.)
> The following code throws an exception; the parser thinks the property in the any clause should be an asset, not a library permission. However, if I remove the property access in the where clause, the parser figures out everything, fine.
> var recentlyViewed =
> 	from voa in session.Query<ViewsOnAsset>()
> 	select voa.Asset;
> var query =
> 	from asset in recentlyViewed
> 	let library = asset.Library
> 	where library.LibraryType == 1 && library.LibraryPermissions.Any(p =>
> 		p.CanViewAssets)
> 	select asset;

-- 
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-2759) Any() in where clause along with property access confuses parser.

[Kelly S. (JIRA) <nh...@gm...>]

Any() in where clause along with property access confuses parser.
-----------------------------------------------------------------

                 Key: NH-2759
                 URL: http://216.121.112.228/browse/NH-2759
             Project:  NHibernate
          Issue Type: Bug
          Components: Linq Provider
    Affects Versions: 3.2.0Beta1
            Reporter: Kelly Stuard


(I have a passing and a failing test case and the exception lined up to attach, shortly.)

The following code throws an exception; the parser thinks the property in the any clause should be an asset, not a library permission. However, if I remove the property access in the where clause, the parser figures out everything, fine.

var recentlyViewed =
	from voa in session.Query<ViewsOnAsset>()
	select voa.Asset;

var query =
	from asset in recentlyViewed
	let library = asset.Library
	where library.LibraryType == 1 && library.LibraryPermissions.Any(p =>
		p.CanViewAssets)
	select asset;


-- 
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] Closed: (NH-2758) windows presentation foundation

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

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

Fabio Maulo closed NH-2758.
---------------------------

    Resolution: Not an Issue

Type universe cannot resolve assembly: NHibernate, Version=3.2.0.2001, Culture=neutral, PublicKeyToken=aa95f207798dfdb4.

> windows presentation foundation
> -------------------------------
>
>                 Key: NH-2758
>                 URL: http://216.121.112.228/browse/NH-2758
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 3.2.0Beta1
>            Reporter: Palle Hansen
>            Priority: Major
>         Attachments: UnresolvedAssemblyException.txt
>
>
> Working with WPF, the wpf designer in vs 2010 crashes again again.....
> Se attach exception error...
> If it is a vs 2010 problem, I apologize  ...
> best regards 
>   palle hansen

-- 
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-2758) windows presentation foundation

[Steve B. (JIRA) <nh...@gm...>]

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

Steve Bohlen commented on NH-2758:
----------------------------------

Since the WPF designer obviously works for most people under VS2010, you'd need to attach to this issue (at a minimum) some sample sln containing a WPF project that references NH and demonstrates the issue on your system.  There is simply insufficient information otherwise for anyone to attempt to repro this issue with any hope of helping to resolve it (if in fact its NH-related at all).

> windows presentation foundation
> -------------------------------
>
>                 Key: NH-2758
>                 URL: http://216.121.112.228/browse/NH-2758
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 3.2.0Beta1
>            Reporter: Palle Hansen
>            Priority: Major
>         Attachments: UnresolvedAssemblyException.txt
>
>
> Working with WPF, the wpf designer in vs 2010 crashes again again.....
> Se attach exception error...
> If it is a vs 2010 problem, I apologize  ...
> best regards 
>   palle hansen

-- 
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-2758) windows presentation foundation

[Palle H. (JIRA) <nh...@gm...>]

windows presentation foundation
-------------------------------

                 Key: NH-2758
                 URL: http://216.121.112.228/browse/NH-2758
             Project:  NHibernate
          Issue Type: Bug
          Components: Core
    Affects Versions: 3.2.0Beta1
            Reporter: Palle Hansen
            Priority: Major
         Attachments: UnresolvedAssemblyException.txt

Working with WPF, the wpf designer in vs 2010 crashes again again.....

Se attach exception error...

If it is a vs 2010 problem, I apologize  ...

best regards 
  palle hansen

-- 
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-2683) Add common dialect functions as extension methods for QueryOver

[Richard B. (JIRA) <nh...@gm...>]

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

Richard Brown resolved NH-2683.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 3.2.0Beta2

> Add common dialect functions as extension methods for QueryOver
> ---------------------------------------------------------------
>
>                 Key: NH-2683
>                 URL: http://216.121.112.228/browse/NH-2683
>             Project:  NHibernate
>          Issue Type: Improvement
>          Components: QueryOver
>    Affects Versions: 3.2.0Alpha2
>            Reporter: Richard Brown
>            Assignee: Richard Brown
>            Priority: Minor
>             Fix For: 3.2.0Beta2
>
>         Attachments: ProjectionsExtensions.zip, QueryOverSqlFuncsExts.zip
>
>
> Some of the common functions (that are registered in most, if not all Dialects) can be used in ICriteria using SQL-projections.
> Extensions methods can be added for these to allow queries along the lines of:
> s.QueryOver<Person>()
>     .Where(p => p.BirthDate.Year() == 1970)
>     .List()
> ... which can be translated to:
>     .Where(Restrictions.Eq(Projections.SqlFunction("year", NHibernateUtil.DateTime, Projections.Property<Person>(p => p.BirthDate)), 1970))
> ... and in turn to:
>     datepart(year, this_.BirthDate) = @p0;

-- 
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-2662) Casting a joined alias in QueryOver loses alias context and looks for property on QueryOver root

[Richard B. (JIRA) <nh...@gm...>]

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

Richard Brown resolved NH-2662.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 3.2.0Beta2

Fixed.  Thanks for the test case.

> Casting a joined alias in QueryOver loses alias context and looks for property on QueryOver root
> ------------------------------------------------------------------------------------------------
>
>                 Key: NH-2662
>                 URL: http://216.121.112.228/browse/NH-2662
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: QueryOver
>    Affects Versions: 3.2.0Alpha2
>            Reporter: Graeme Foster
>            Assignee: Richard Brown
>            Priority: Major
>             Fix For: 3.2.0Beta2
>
>         Attachments: NH2662.zip
>
>
> If you QueryOver an entity, alias-join to a property on that entity which has an inheritance tree, and then attempt to project a property on a specific subclass of the entity, the property path loses the context of the alias and attempts to find it on the queryover root.
> Pseudo code:
> QueryOver<Customer>()
> .JoinAlias(c => c.Order, () => orderAlias)
> .SelectList(list => list.Select( () => ((SpecialOrder)orderAlias).SpecialReason);
> blows up.
> The equivalent in linq-nhibernate works OK which is why I think this is a bug.
> Query<Customer>().Select( c => new { SpecialReason = ((SpecialOrder)c.Order).SpecialReason } );
> Will attach issue zip in same format as NH Trunk issues.
> Graeme

-- 
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-2712) Linq query doesn't support enums in VB.NET

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

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

Patrick Earl resolved NH-2712.
------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 3.1.0)
                   3.2.0Beta2

The bug reported here is for the Linq provider and has already been fixed.  If there is another bug for QueryOver, please create another issue and provide a failing test case.

> Linq query doesn't support enums in VB.NET
> ------------------------------------------
>
>                 Key: NH-2712
>                 URL: http://216.121.112.228/browse/NH-2712
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Linq Provider
>    Affects Versions: 3.0.0.Beta2
>            Reporter: Matthew Beer
>            Assignee: Patrick Earl
>            Priority: Minor
>             Fix For: 3.2.0Beta2
>
>
> Comparing enums in a Linq query with VB.NET throws a NotSupportedException:
> Return (From invoice In session.Query(Of Invoice)()
>         Where invoice.Payment.ElectronicInvoiceStatus = ElectronicInvoiceStatus.Unpaid
>         Select invoice).Any()
> Message: ConvertChecked([-1].Payment.ElectronicInvoiceStatus)
> Stack Trace:
>    at NHibernate.Linq.Visitors.HqlGeneratorExpressionTreeVisitor.VisitUnaryExpression(UnaryExpression expression)
>    at NHibernate.Linq.Visitors.HqlGeneratorExpressionTreeVisitor.VisitExpression(Expression expression)
>    at NHibernate.Linq.Visitors.HqlGeneratorExpressionTreeVisitor.VisitBinaryExpression(BinaryExpression expression)
>    at NHibernate.Linq.Visitors.HqlGeneratorExpressionTreeVisitor.VisitExpression(Expression expression)
>    at NHibernate.Linq.Visitors.HqlGeneratorExpressionTreeVisitor.Visit(Expression expression, VisitorParameters parameters)
>    at NHibernate.Linq.Visitors.QueryModelVisitor.VisitWhereClause(WhereClause whereClause, QueryModel queryModel, Int32 index)
>    at Remotion.Data.Linq.Clauses.WhereClause.Accept(IQueryModelVisitor visitor, QueryModel queryModel, Int32 index)
>    at Remotion.Data.Linq.QueryModelVisitorBase.VisitBodyClauses(ObservableCollection`1 bodyClauses, QueryModel queryModel)
>    at Remotion.Data.Linq.QueryModelVisitorBase.VisitQueryModel(QueryModel queryModel)
>    at NHibernate.Linq.Visitors.QueryModelVisitor.Visit()
>    at NHibernate.Linq.Visitors.QueryModelVisitor.GenerateHqlQuery(QueryModel queryModel, VisitorParameters parameters, Boolean root)
>    at NHibernate.Linq.NhLinqExpression.Translate(ISessionFactoryImplementor sessionFactory)
>    at NHibernate.Hql.Ast.ANTLR.ASTQueryTranslatorFactory.CreateQueryTranslators(String queryIdentifier, IQueryExpression queryExpression, String collectionRole, Boolean shallow, IDictionary`2 filters, ISessionFactoryImplementor factory)
>    at NHibernate.Engine.Query.HQLExpressionQueryPlan.CreateTranslators(String expressionStr, IQueryExpression queryExpression, String collectionRole, Boolean shallow, IDictionary`2 enabledFilters, ISessionFactoryImplementor factory)
>    at NHibernate.Engine.Query.HQLExpressionQueryPlan..ctor(String expressionStr, IQueryExpression queryExpression, String collectionRole, Boolean shallow, IDictionary`2 enabledFilters, ISessionFactoryImplementor factory)
>    at NHibernate.Engine.Query.HQLExpressionQueryPlan..ctor(String expressionStr, IQueryExpression queryExpression, Boolean shallow, IDictionary`2 enabledFilters, ISessionFactoryImplementor factory)
>    at NHibernate.Engine.Query.QueryPlanCache.GetHQLQueryPlan(IQueryExpression queryExpression, Boolean shallow, IDictionary`2 enabledFilters)
>    at NHibernate.Impl.AbstractSessionImpl.GetHQLQueryPlan(IQueryExpression queryExpression, Boolean shallow)
>    at NHibernate.Impl.AbstractSessionImpl.CreateQuery(IQueryExpression queryExpression)
>    at NHibernate.Linq.NhQueryProvider.PrepareQuery(Expression expression, IQuery& query, NhLinqExpression& nhQuery)
>    at NHibernate.Linq.NhQueryProvider.Execute(Expression expression)
>    at NHibernate.Linq.NhQueryProvider.Execute[TResult](Expression expression)
>    at System.Linq.Queryable.Any[TSource](IQueryable`1 source)

-- 
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-2712) Linq query doesn't support enums in VB.NET

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

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

Patrick Earl updated NH-2712:
-----------------------------

    Summary: Linq query doesn't support enums in VB.NET  (was: queryover doesn't support enums in VB.NET)

> Linq query doesn't support enums in VB.NET
> ------------------------------------------
>
>                 Key: NH-2712
>                 URL: http://216.121.112.228/browse/NH-2712
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Linq Provider
>    Affects Versions: 3.0.0.Beta2
>            Reporter: Matthew Beer
>            Assignee: Patrick Earl
>            Priority: Minor
>             Fix For: 3.1.0
>
>
> Comparing enums in a Linq query with VB.NET throws a NotSupportedException:
> Return (From invoice In session.Query(Of Invoice)()
>         Where invoice.Payment.ElectronicInvoiceStatus = ElectronicInvoiceStatus.Unpaid
>         Select invoice).Any()
> Message: ConvertChecked([-1].Payment.ElectronicInvoiceStatus)
> Stack Trace:
>    at NHibernate.Linq.Visitors.HqlGeneratorExpressionTreeVisitor.VisitUnaryExpression(UnaryExpression expression)
>    at NHibernate.Linq.Visitors.HqlGeneratorExpressionTreeVisitor.VisitExpression(Expression expression)
>    at NHibernate.Linq.Visitors.HqlGeneratorExpressionTreeVisitor.VisitBinaryExpression(BinaryExpression expression)
>    at NHibernate.Linq.Visitors.HqlGeneratorExpressionTreeVisitor.VisitExpression(Expression expression)
>    at NHibernate.Linq.Visitors.HqlGeneratorExpressionTreeVisitor.Visit(Expression expression, VisitorParameters parameters)
>    at NHibernate.Linq.Visitors.QueryModelVisitor.VisitWhereClause(WhereClause whereClause, QueryModel queryModel, Int32 index)
>    at Remotion.Data.Linq.Clauses.WhereClause.Accept(IQueryModelVisitor visitor, QueryModel queryModel, Int32 index)
>    at Remotion.Data.Linq.QueryModelVisitorBase.VisitBodyClauses(ObservableCollection`1 bodyClauses, QueryModel queryModel)
>    at Remotion.Data.Linq.QueryModelVisitorBase.VisitQueryModel(QueryModel queryModel)
>    at NHibernate.Linq.Visitors.QueryModelVisitor.Visit()
>    at NHibernate.Linq.Visitors.QueryModelVisitor.GenerateHqlQuery(QueryModel queryModel, VisitorParameters parameters, Boolean root)
>    at NHibernate.Linq.NhLinqExpression.Translate(ISessionFactoryImplementor sessionFactory)
>    at NHibernate.Hql.Ast.ANTLR.ASTQueryTranslatorFactory.CreateQueryTranslators(String queryIdentifier, IQueryExpression queryExpression, String collectionRole, Boolean shallow, IDictionary`2 filters, ISessionFactoryImplementor factory)
>    at NHibernate.Engine.Query.HQLExpressionQueryPlan.CreateTranslators(String expressionStr, IQueryExpression queryExpression, String collectionRole, Boolean shallow, IDictionary`2 enabledFilters, ISessionFactoryImplementor factory)
>    at NHibernate.Engine.Query.HQLExpressionQueryPlan..ctor(String expressionStr, IQueryExpression queryExpression, String collectionRole, Boolean shallow, IDictionary`2 enabledFilters, ISessionFactoryImplementor factory)
>    at NHibernate.Engine.Query.HQLExpressionQueryPlan..ctor(String expressionStr, IQueryExpression queryExpression, Boolean shallow, IDictionary`2 enabledFilters, ISessionFactoryImplementor factory)
>    at NHibernate.Engine.Query.QueryPlanCache.GetHQLQueryPlan(IQueryExpression queryExpression, Boolean shallow, IDictionary`2 enabledFilters)
>    at NHibernate.Impl.AbstractSessionImpl.GetHQLQueryPlan(IQueryExpression queryExpression, Boolean shallow)
>    at NHibernate.Impl.AbstractSessionImpl.CreateQuery(IQueryExpression queryExpression)
>    at NHibernate.Linq.NhQueryProvider.PrepareQuery(Expression expression, IQuery& query, NhLinqExpression& nhQuery)
>    at NHibernate.Linq.NhQueryProvider.Execute(Expression expression)
>    at NHibernate.Linq.NhQueryProvider.Execute[TResult](Expression expression)
>    at System.Linq.Queryable.Any[TSource](IQueryable`1 source)

-- 
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] Closed: (NH-2757) could not find LinqToHqlGeneratorsRegistry()

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

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

Fabio Maulo closed NH-2757.
---------------------------

    Resolution: Not an Issue

I'm not sure that this is the place to make questions.
just for this time: NHibernate.Cfg.ConfigurationExtensions

> could not find LinqToHqlGeneratorsRegistry()
> --------------------------------------------
>
>                 Key: NH-2757
>                 URL: http://216.121.112.228/browse/NH-2757
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Linq Provider
>    Affects Versions: 3.1.0
>            Reporter: alireza sabouri
>            Priority: Major
>
> In previous versions for registering custom HQLGenerators we could use of LinqToHqlGeneratorsRegistry()
> but in current version (3.1.0) i couldn't find any suitable method.
> i'm not sure if the method of registering has been changed or it totally removed

-- 
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-2757) could not find LinqToHqlGeneratorsRegistry()

[alireza s. (JIRA) <nh...@gm...>]

could not find LinqToHqlGeneratorsRegistry()
--------------------------------------------

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


In previous versions for registering custom HQLGenerators we could use of LinqToHqlGeneratorsRegistry()
but in current version (3.1.0) i couldn't find any suitable method.

i'm not sure if the method of registering has been changed or it totally removed


-- 
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-2756) Unable to map a set of composite-elements with a formula property

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

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

cremor updated NH-2756:
-----------------------

    Attachment: NH2756 Test.zip

> Unable to map a set of composite-elements with a formula property
> -----------------------------------------------------------------
>
>                 Key: NH-2756
>                 URL: http://216.121.112.228/browse/NH-2756
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 3.2.0Beta1
>            Reporter: cremor
>            Priority: Minor
>         Attachments: NH2756 Test.zip
>
>
> The attached test shows that a mapping containing a <set> of composite-elements with a formula <property> doesn't work (InvalidCastException in NHibernate.Mapping.Set.CreatePrimaryKey()).
> Using a <bag> 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-2756) Unable to map a set of composite-elements with a formula property

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

Unable to map a set of composite-elements with a formula property
-----------------------------------------------------------------

                 Key: NH-2756
                 URL: http://216.121.112.228/browse/NH-2756
             Project:  NHibernate
          Issue Type: Bug
          Components: Core
    Affects Versions: 3.2.0Beta1
            Reporter: cremor
            Priority: Minor


The attached test shows that a mapping containing a <set> of composite-elements with a formula <property> doesn't work (InvalidCastException in NHibernate.Mapping.Set.CreatePrimaryKey()).

Using a <bag> 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-2755) LockMode hash differs in x86 and 64bit OS

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

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

Fabio Maulo commented on NH-2755:
---------------------------------

Well... that is not the only one place where NH store the hash code at ctor.

> LockMode hash differs in x86 and 64bit OS
> -----------------------------------------
>
>                 Key: NH-2755
>                 URL: http://216.121.112.228/browse/NH-2755
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 3.2.0Beta2
>            Reporter: Anton
>            Priority: Major
>
> When using LockMode over remoting between PCs with x86 and 64bit operating systems there is different result in GetHashCode.
> It leads to error "LockMode Upgrade not supported by NHibernate.Persister.Entity.SingleTableEntityPersister " when I pass LockMode.Upgrade from x86 to 64bit to do
> session.Lock(this, lockMode)
> It is caused by generating and storing hash code upon creating instance of LockMode.
> LockMode constructor uses a XOR (^) operand to generate and store hash code, and it has different behavior depends on OS type (x84, 64bit)

-- 
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-2755) LockMode hash differs in x86 and 64bit OS

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

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

Anton commented on NH-2755:
---------------------------

Yes, LockMode just passes from client to server PC, client is x86, server is 64bit.
When using client 64bit and server 64bit - everything ok.

Stored hashcode in instance of LockMode differs at 86/64

> LockMode hash differs in x86 and 64bit OS
> -----------------------------------------
>
>                 Key: NH-2755
>                 URL: http://216.121.112.228/browse/NH-2755
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 3.2.0Beta2
>            Reporter: Anton
>            Priority: Major
>
> When using LockMode over remoting between PCs with x86 and 64bit operating systems there is different result in GetHashCode.
> It leads to error "LockMode Upgrade not supported by NHibernate.Persister.Entity.SingleTableEntityPersister " when I pass LockMode.Upgrade from x86 to 64bit to do
> session.Lock(this, lockMode)
> It is caused by generating and storing hash code upon creating instance of LockMode.
> LockMode constructor uses a XOR (^) operand to generate and store hash code, and it has different behavior depends on OS type (x84, 64bit)

-- 
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-2755) LockMode hash differs in x86 and 64bit OS

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

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

Fabio Maulo commented on NH-2755:
---------------------------------

What you are doing is pass the NH's LockMode serializaed instance between 2 different machines, right ?

> LockMode hash differs in x86 and 64bit OS
> -----------------------------------------
>
>                 Key: NH-2755
>                 URL: http://216.121.112.228/browse/NH-2755
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 3.2.0Beta2
>            Reporter: Anton
>            Priority: Major
>
> When using LockMode over remoting between PCs with x86 and 64bit operating systems there is different result in GetHashCode.
> It leads to error "LockMode Upgrade not supported by NHibernate.Persister.Entity.SingleTableEntityPersister " when I pass LockMode.Upgrade from x86 to 64bit to do
> session.Lock(this, lockMode)
> It is caused by generating and storing hash code upon creating instance of LockMode.
> LockMode constructor uses a XOR (^) operand to generate and store hash code, and it has different behavior depends on OS type (x84, 64bit)

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