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

[nhibernate-issues] [NHJIRA] Created: (NH-2657) OrderBy After Cast Not Working

[Lee T. (JIRA) <nh...@gm...>]

OrderBy After Cast Not Working
------------------------------

                 Key: NH-2657
                 URL: http://216.121.112.228/browse/NH-2657
             Project:  NHibernate
          Issue Type: Bug
          Components: Linq Provider
    Affects Versions: 3.1.0
            Reporter: Lee Timmins
            Priority: Minor


The following test:

[TestMethod]
public void Cast_OrderBy() {
    var result = _session.Query<CommentUser>()
        .Cast<Comment>()
        .OrderBy(c => c.CommentID)
        .ToList();

    Assert.AreEqual(4, result.Count);
}

Fails in the latest Linq provider but worked fine in the old one.

-- 
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-2656) First/FirstOrDefault Doesn't Work

[Lee T. (JIRA) <nh...@gm...>]

First/FirstOrDefault Doesn't Work
---------------------------------

                 Key: NH-2656
                 URL: http://216.121.112.228/browse/NH-2656
             Project:  NHibernate
          Issue Type: Bug
          Components: Linq Provider
    Affects Versions: 3.1.0
            Reporter: Lee Timmins


I have the following tests:

[TestMethod]
public void First() {
    var result = _session.Query<Post>()
        .OrderBy(p => p.Date)
        .First(p => p.Comments.Count == 1);

    Assert.AreEqual(1, result.PostID);
}

[TestMethod]
public void FirstOrDefault() {
    var result = _session.Query<Post>()
        .OrderBy(p => p.Date)
        .FirstOrDefault(p => p.Comments.Count == 1);
    var result2 = _session.Query<Post>()
        .OrderBy(p => p.Date)
        .FirstOrDefault(p => p.Comments.Count == 10);

    Assert.AreEqual(1, result.PostID);
    Assert.IsNull(result2);
}

They both worked fine in the old Linq provider (changing Query to Linq) but in version 3.1 it throws the error:

Test method NHibernate3_1.UnitTest.First(OrDefault) threw exception: 
System.InvalidOperationException: Sequence contains no elements

-- 
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-2654) Any Doesn't Work

[Lee T. (JIRA) <nh...@gm...>]

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

Lee Timmins commented on NH-2654:
---------------------------------

Thanks for fixing this so quickly. I hope this fix also addresses the following aswell:

[TestMethod]
public void Where_Any() {
    var result = _session.Query<Post>()
        .Where(p => p.Comments.Any(c => c.IsSpam))
        .ToList();

    Assert.AreEqual(2, result.Count); // My test runner reports that there are actually 0 results but there should be 2
}

It is similar to the above except that Any is used within a Where clause.

> Any Doesn't Work
> ----------------
>
>                 Key: NH-2654
>                 URL: http://216.121.112.228/browse/NH-2654
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Linq Provider
>    Affects Versions: 3.1.0
>            Reporter: Lee Timmins
>            Priority: Major
>
> I have created my own basic blog application.  For testing i have pre-populated some data such that every post contains atleast one comment (one to many relationship from Post to Comment).  I have the following test:
> [TestMethod]
> public void Any() {
>     var result = _session.Query<Post>()
>         .Any(p => p.Comments.Count == 0);
>     Assert.IsFalse(result);
> }
> However this test fails where as in version 2 (changing Query to Linq) it worked fine.
> I'd appreciate if this could be solved quickly as this is stopping me from upgrading.  Thanks

-- 
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-2655) DbType.Double should be float(53) instead of DOUBLE PRECISION in the SQL-Severer2000 Dialect

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

DbType.Double should be float(53) instead of DOUBLE PRECISION in the SQL-Severer2000 Dialect
--------------------------------------------------------------------------------------------

                 Key: NH-2655
                 URL: http://216.121.112.228/browse/NH-2655
             Project:  NHibernate
          Issue Type: Bug
          Components: DataProviders / Dialects
    Affects Versions: 3.2.0Alpha2
            Reporter: Nils Andresen


I am using NH to map c#-double values into SQL Server as floats. Everything works perfectly fine, however recently I tried running the SchemaValidator.

SchemaValidator fails:

Found: float, Expected DOUBLE PRECISION

Creating the tables using DOUBLE PRECISION works, but SQL Server will report the columns as float

The code for src/NHibernate/Dialect/MsSql2000Dialect.cs states 
RegisterColumnType(DbType.Double, "DOUBLE PRECISION"); //synonym for FLOAT(53)

IMO it would be better here to use the "real" type (float) istead of it's synonym.

-- 
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-2647) Forward mapping and db types

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

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

David Popiashvili commented on NH-2647:
---------------------------------------

o god, I'm sorry, I didn't pay attention to that. Sorry again :(

> Forward mapping and db types
> ----------------------------
>
>                 Key: NH-2647
>                 URL: http://216.121.112.228/browse/NH-2647
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 3.0.0.GA
>            Reporter: David Popiashvili
>            Priority: Minor
>         Attachments: NHibernateTest.rar
>
>
> When we create database from our *.hbm mapping files, some of the data types are not mapped correctly to the db. For example, NHibernate ignores Precision and Scale properties for decimal type. Also there's strange behavior with AnsiString, for example this property
> <property name="Username" length="15" type="AnsiString" /> is mapped as nvarchar(1) on the database, shouldn't it be varchar(15)?
> We are using .NET 4, NHibernate 3.0 and SQL Server 2008

-- 
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-2647) Forward mapping and db types

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

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

Julian Maughan commented on NH-2647:
------------------------------------

...but in the description you say you are using SQL Server 2008. So it occurs in CE as well?

> Forward mapping and db types
> ----------------------------
>
>                 Key: NH-2647
>                 URL: http://216.121.112.228/browse/NH-2647
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 3.0.0.GA
>            Reporter: David Popiashvili
>            Priority: Minor
>         Attachments: NHibernateTest.rar
>
>
> When we create database from our *.hbm mapping files, some of the data types are not mapped correctly to the db. For example, NHibernate ignores Precision and Scale properties for decimal type. Also there's strange behavior with AnsiString, for example this property
> <property name="Username" length="15" type="AnsiString" /> is mapped as nvarchar(1) on the database, shouldn't it be varchar(15)?
> We are using .NET 4, NHibernate 3.0 and SQL Server 2008

-- 
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-2654) Any Doesn't Work

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

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

Fabio Maulo updated NH-2654:
----------------------------

    Component/s:     (was: Documentation)
                 Linq Provider

> Any Doesn't Work
> ----------------
>
>                 Key: NH-2654
>                 URL: http://216.121.112.228/browse/NH-2654
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Linq Provider
>    Affects Versions: 3.1.0
>            Reporter: Lee Timmins
>            Priority: Major
>
> I have created my own basic blog application.  For testing i have pre-populated some data such that every post contains atleast one comment (one to many relationship from Post to Comment).  I have the following test:
> [TestMethod]
> public void Any() {
>     var result = _session.Query<Post>()
>         .Any(p => p.Comments.Count == 0);
>     Assert.IsFalse(result);
> }
> However this test fails where as in version 2 (changing Query to Linq) it worked fine.
> I'd appreciate if this could be solved quickly as this is stopping me from upgrading.  Thanks

-- 
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-1192) Support bitwise operations

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

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

Alexey Gorbach commented on NH-1192:
------------------------------------

It is not fixed for oracle. It uses & in bitwise and operations, while it should call function bitand.

> Support bitwise operations
> --------------------------
>
>                 Key: NH-1192
>                 URL: http://216.121.112.228/browse/NH-1192
>             Project:  NHibernate
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.2.1
>            Reporter: Serguei Komarov
>            Priority: Major
>             Fix For: 2.1.0.Beta2
>
>
> Support bitwise operations like bitwise-and and bitwise-or via HQL or criteria expression.
> from Domain.Employee employee where (employee.Status & 1) > 0
> See related issue from Hibernate JIRA http://opensource.atlassian.com/projects/hibernate/browse/HHH-160
> Thank you in advance.

-- 
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-2647) Forward mapping and db types

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

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

David Popiashvili commented on NH-2647:
---------------------------------------

Yes, it's shown in hibernate.cfg.xml file.

> Forward mapping and db types
> ----------------------------
>
>                 Key: NH-2647
>                 URL: http://216.121.112.228/browse/NH-2647
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 3.0.0.GA
>            Reporter: David Popiashvili
>            Priority: Minor
>         Attachments: NHibernateTest.rar
>
>
> When we create database from our *.hbm mapping files, some of the data types are not mapped correctly to the db. For example, NHibernate ignores Precision and Scale properties for decimal type. Also there's strange behavior with AnsiString, for example this property
> <property name="Username" length="15" type="AnsiString" /> is mapped as nvarchar(1) on the database, shouldn't it be varchar(15)?
> We are using .NET 4, NHibernate 3.0 and SQL Server 2008

-- 
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-2647) Forward mapping and db types

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

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

Julian Maughan commented on NH-2647:
------------------------------------

In your test you are using the MsSqlCeDialect dialect?

> Forward mapping and db types
> ----------------------------
>
>                 Key: NH-2647
>                 URL: http://216.121.112.228/browse/NH-2647
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 3.0.0.GA
>            Reporter: David Popiashvili
>            Priority: Minor
>         Attachments: NHibernateTest.rar
>
>
> When we create database from our *.hbm mapping files, some of the data types are not mapped correctly to the db. For example, NHibernate ignores Precision and Scale properties for decimal type. Also there's strange behavior with AnsiString, for example this property
> <property name="Username" length="15" type="AnsiString" /> is mapped as nvarchar(1) on the database, shouldn't it be varchar(15)?
> We are using .NET 4, NHibernate 3.0 and SQL Server 2008

-- 
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-2526) Sybase ASE 15 support

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

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

Julian Maughan commented on NH-2526:
------------------------------------

Not sure if you saw this, but in the code I commented that temp tables can be created outside a transaction by changing the 'ddl in tran' setting to true on the tempdb database. However, there are some fairly dire warnings about doing so, such as: "WARNING! Data definition language (DDL) commands hold locks on system tables such as sysobjects. Avoid using them inside transactions; if you must use them, keep the transactions short. Using any DDL commands on tempdb within transactions may cause your system to grind to a halt. Always leave ddl in tran set to false in tempdb."

Changing the setting did improve the number of test passes considerably. It doesn't make sense to me that temp tables would be handled like other DDL statements.

> Sybase ASE 15 support
> ---------------------
>
>                 Key: NH-2526
>                 URL: http://216.121.112.228/browse/NH-2526
>             Project:  NHibernate
>          Issue Type: Improvement
>          Components: DataProviders / Dialects
>    Affects Versions: 3.0.0.GA
>            Reporter: Jim Hale Jr.
>            Priority: Major
>             Fix For: 3.2.0Alpha1
>
>         Attachments: SybaseAdoNet2ClientDriver.cs, SybaseAse15Dialect.cs
>
>
> The 3.0.0 release banished Sybase ASE users for reasons unknown to me.  I understand the criticism of the 2.x and 3.0.0 release candidate implementations of the Sybase ASE dialect (yes they were bad), but at least they let ASE users use NHibernate.  Better to have basic but functional support than no support at all.  This is especially important for ASE users considering the lack of Entity support by Sybase for ASE.  Removing ASE support forced NHibernate users to stay with the 2.12 release or pay for an Entity aware provider.  The comments I read regarding the removal of ASE support - specifically regarding the merging of the ASE and ASA dialects - also make no sense to me.  ASA and ASE are two different products with different keywords, SQL syntax, functions, and drivers.  Their dialects cannot be merged!  Same with the supposed support from the MS SQL 2000 dialect - this dialect uses MS keywords like 'TOP' that ASE does not support.
> Attached is a port of the Sybase ASE Dialect from the Java Hibernate project along with support for the ADO.NET driver provided by Sybase.  I am using it in a project currently and it at least appears to work.  I am only using the most basic of NHibernate features though so additional testing would be nice.  But it provides a start.
> Tested against Sybase 15.0.3.0 using .NET 4.0 runtime and Sybase.AdoNet2.AseClient.dll driver (version 1.15.305.0).

-- 
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: (NHV-115) Validator displays wrong error "The 'inverse' attribute is not declared." when "not-null" is missing

[Marko K. (J. <nh...@gm...>]

    [ http://216.121.112.228/browse/NHV-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20910#action_20910 ] 

Marko Kovačić commented on NHV-115:
-----------------------------------

I don't have any tests ready or know how to make them quickly, sorry.
It's just wrong error message in the exception.

> Validator displays wrong error "The 'inverse' attribute is not declared." when "not-null" is missing
> ----------------------------------------------------------------------------------------------------
>
>                 Key: NHV-115
>                 URL: http://216.121.112.228/browse/NHV-115
>             Project: NHibernate.Validator
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.3.0 GA
>            Reporter: Marko Kovačić
>
> I had a bidirectional mapping, with this on the child side:
> <many-to-one name="Subjekt" column="SubjektId" inverse="true" />
> But I kept ketting error message:
> XML validation error: The 'inverse' attribute is not declared.
> And that drived me crazy as the inverse attribute is obviously there... finally I've tried not-null="true" and the message dissapeared. So please just update the error message so people don't get stuck on this.
> Thank you.

-- 
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: (NHV-114) Remove dependency to Log4net

[Dario Q. (JIRA) <nh...@gm...>]

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

Dario Quintana closed NHV-114.
------------------------------

    Resolution: Fixed

> Remove dependency to Log4net
> ----------------------------
>
>                 Key: NHV-114
>                 URL: http://216.121.112.228/browse/NHV-114
>             Project: NHibernate.Validator
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.3.0 GA
>            Reporter: Dario Quintana
>            Assignee: Dario Quintana
>             Fix For: 1.3.1 GA
>
>
> Replace to NHibernate.IInternalLogger

-- 
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: (NHV-115) Validator displays wrong error "The 'inverse' attribute is not declared." when "not-null" is missing

[Dario Q. (JIRA) <nh...@gm...>]

    [ http://216.121.112.228/browse/NHV-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20909#action_20909 ] 

Dario Quintana commented on NHV-115:
------------------------------------

A simple test to reproduce the problem would be nice.
Thanks

> Validator displays wrong error "The 'inverse' attribute is not declared." when "not-null" is missing
> ----------------------------------------------------------------------------------------------------
>
>                 Key: NHV-115
>                 URL: http://216.121.112.228/browse/NHV-115
>             Project: NHibernate.Validator
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.3.0 GA
>            Reporter: Marko Kovačić
>
> I had a bidirectional mapping, with this on the child side:
> <many-to-one name="Subjekt" column="SubjektId" inverse="true" />
> But I kept ketting error message:
> XML validation error: The 'inverse' attribute is not declared.
> And that drived me crazy as the inverse attribute is obviously there... finally I've tried not-null="true" and the message dissapeared. So please just update the error message so people don't get stuck on this.
> Thank you.

-- 
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: (NHV-114) Remove dependency to Log4net

[Dario Q. (JIRA) <nh...@gm...>]

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

Dario Quintana updated NHV-114:
-------------------------------

    Fix Version/s: 1.3.1 GA

> Remove dependency to Log4net
> ----------------------------
>
>                 Key: NHV-114
>                 URL: http://216.121.112.228/browse/NHV-114
>             Project: NHibernate.Validator
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.3.0 GA
>            Reporter: Dario Quintana
>            Assignee: Dario Quintana
>             Fix For: 1.3.1 GA
>
>
> Replace to NHibernate.IInternalLogger

-- 
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] Reopened: (NHV-114) Remove dependency to Log4net

[Dario Q. (JIRA) <nh...@gm...>]

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

Dario Quintana reopened NHV-114:
--------------------------------


> Remove dependency to Log4net
> ----------------------------
>
>                 Key: NHV-114
>                 URL: http://216.121.112.228/browse/NHV-114
>             Project: NHibernate.Validator
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.3.0 GA
>            Reporter: Dario Quintana
>            Assignee: Dario Quintana
>             Fix For: 1.3.1 GA
>
>
> Replace to NHibernate.IInternalLogger

-- 
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-2653) Remove just added ExpressionTreeVisitor class

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

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

Patrick Earl resolved NH-2653.
------------------------------

       Resolution: Fixed
    Fix Version/s: 3.2.0Beta1

> Remove just added ExpressionTreeVisitor class
> ---------------------------------------------
>
>                 Key: NH-2653
>                 URL: http://216.121.112.228/browse/NH-2653
>             Project:  NHibernate
>          Issue Type: Task
>          Components: Linq Provider
>    Affects Versions: 3.2.0Alpha1
>            Reporter: Patrick Earl
>            Assignee: Patrick Earl
>             Fix For: 3.2.0Beta1
>
>
> This intermediate class is only half a solution to the problem.  We need to be clear on what the problem actually is before proceeding.

-- 
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-2654) Any Doesn't Work

[Lee T. (JIRA) <nh...@gm...>]

Any Doesn't Work
----------------

                 Key: NH-2654
                 URL: http://216.121.112.228/browse/NH-2654
             Project:  NHibernate
          Issue Type: Bug
          Components: Documentation
    Affects Versions: 3.1.0
            Reporter: Lee Timmins
            Priority: Major


I have created my own basic blog application.  For testing i have pre-populated some data such that every post contains atleast one comment (one to many relationship from Post to Comment).  I have the following test:

[TestMethod]
public void Any() {
    var result = _session.Query<Post>()
        .Any(p => p.Comments.Count == 0);

    Assert.IsFalse(result);
}

However this test fails where as in version 2 (changing Query to Linq) it worked fine.

I'd appreciate if this could be solved quickly as this is stopping me from upgrading.  Thanks

-- 
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-2436) Db2400 Use of parameter marker not valid

[Carlo D. (JIRA) <nh...@gm...>]

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

Carlo DiGiacomo commented on NH-2436:
-------------------------------------

I am using 3.1 and I am also having the same issue.

> Db2400 Use of parameter marker not valid
> ----------------------------------------
>
>                 Key: NH-2436
>                 URL: http://216.121.112.228/browse/NH-2436
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: DataProviders / Dialects, Linq Provider
>    Affects Versions: 3.0.0.CR1
>            Reporter: stephane borel
>            Priority: Minor
>
> Using db2 on iSeries when running:
> var query = from client in session.Query<Client>() where (client.name.Contains("XYZ")) orderby client.id select client;
> the following statement is generated:
> select client0_.ID as id0_, client0_.NAME as name0_ from DEVENV.CLIENTS client0_ where (client0_.NAME like ('%'||?||'%')) order by client0_.ID asc
> with parameter Name:p1 - Value:XYZ
> This causes error
> [iDB2SQLErrorException (0x80004005): SQL0418 Use of parameter marker not valid.]
> The reason is that db2 cannot guess the parameter's type. The parameters should be cast to the columns parameter.
> In this would generate the following statement:
> select client0_.ID as id0_, client0_.NAME as name0_ from DEVENV.CLIENTS client0_ where (client0_.NAME like ('%'||CAST(? as VARCHAR(255))||'%')) order by client0_.ID asc

-- 
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-2653) Remove just added ExpressionTreeVisitor class

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

Remove just added ExpressionTreeVisitor class
---------------------------------------------

                 Key: NH-2653
                 URL: http://216.121.112.228/browse/NH-2653
             Project:  NHibernate
          Issue Type: Task
          Components: Linq Provider
    Affects Versions: 3.2.0Alpha1
            Reporter: Patrick Earl
            Assignee: Patrick Earl


This intermediate class is only half a solution to the problem.  We need to be clear on what the problem actually is before proceeding.

-- 
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-2648) HQL with joins in sub-select creates wrong SQL

[Harald M. M. (J. <nh...@gm...>]

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

Harald M. Müller updated NH-2648:
---------------------------------

    Attachment: FromElementsForSubqueryFrom.gif
                ASTForSubqueryFrom.gif

I have attached two images that show that the AST is in in inconsistent state: The "_fromElementsByTableAlias" collection for the subquery contains, as expected, two nodes (the second one is the joined one). But the AST itself contains only one child ...

> HQL with joins in sub-select creates wrong SQL
> ----------------------------------------------
>
>                 Key: NH-2648
>                 URL: http://216.121.112.228/browse/NH-2648
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 3.2.0Beta1
>            Reporter: Harald M. Müller
>            Priority: Critical
>         Attachments: ASTForSubqueryFrom.gif, FromElementsForSubqueryFrom.gif, HQL_MissingJoinInExists.zip
>
>
> The following query is translated to wrong SQL - the join is missing from the sub-select:
>     SELECT ROOT FROM NHibernate.Test.NHSpecificTest.HQL_MissingJoinInExists.Sheet AS ROOT 
>                             WHERE (EXISTS (FROM NHibernate.Test.NHSpecificTest.HQL_MissingJoinInExists.Shelf AS inv  
>                                            JOIN ROOT.Folder AS ROOT_Folder 
>                                            WHERE (((ROOT_Folder.Shelf) = (inv) AND inv.Id = 1)) )) 
>                                   AND ROOT.Name = 'SomeName'
> (The query was created by a HQL generator of ours - hence the superfluous parentheses). The exceotion is:
> NHibernate.Exceptions.GenericADOException : could not execute query
> [ select sheet0_.Id as Id2_, sheet0_.Name as Name2_, sheet0_.Folder as Folder2_ from Sheet sheet0_ where (exists (select shelf1_.Id from Shelf shelf1_ where folder2_.Shelf=shelf1_.Id and shelf1_.Id=1)) and sheet0_.Name='SomeName' ]
> [SQL: select sheet0_.Id as Id2_, sheet0_.Name as Name2_, sheet0_.Folder as Folder2_ from Sheet sheet0_ where (exists (select shelf1_.Id from Shelf shelf1_ where folder2_.Shelf=shelf1_.Id and shelf1_.Id=1)) and sheet0_.Name='SomeName']
>   ----> System.Data.SqlClient.SqlException : The multi-part identifier "folder2_.Shelf" could not be bound.
> Since NHib 0.99 and in Hibernate, it has been possible to use joins inside subqueries. HQL allows it, and therefore, it should produce correct SQL (both syntactically and semantically). Actually, joins in subqueries are *necessary* if there are OR or NOT operators inside the subquery (some simpler queries can be rewritten with all Joins at top-level).
> I consider this bug critical because there is no workaround for
> * HQL generated for earlier NHib versions
> * manual HQL that needs OR or NOT inside a subquery
> * (I assume) the correct translation of Linq's .Any in the NHib.Linq provider
> I have attached a test case that shows the behavior.

-- 
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-2652) SchemaMetadataUpdater does not take Dialect default properties

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

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

Fabio Maulo resolved NH-2652.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 3.2.0Beta1

> SchemaMetadataUpdater does not take Dialect default properties
> --------------------------------------------------------------
>
>                 Key: NH-2652
>                 URL: http://216.121.112.228/browse/NH-2652
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Core, DataProviders / Dialects
>    Affects Versions: 3.2.0Alpha1
>            Reporter: Fabio Maulo
>             Fix For: 3.2.0Beta1
>
>


-- 
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-2652) SchemaMetadataUpdater does not take Dialect default properties

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

SchemaMetadataUpdater does not take Dialect default properties
--------------------------------------------------------------

                 Key: NH-2652
                 URL: http://216.121.112.228/browse/NH-2652
             Project:  NHibernate
          Issue Type: Bug
          Components: Core, DataProviders / Dialects
    Affects Versions: 3.2.0Alpha1
            Reporter: Fabio Maulo




-- 
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-2650) HQL + theta-style join + Enumerable() + select only one entity = strange proxies' behaviour while iterating

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

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

Fabio Maulo updated NH-2650:
----------------------------

    Component/s:     (was: DataProviders / Dialects)
                 Core

> HQL + theta-style join + Enumerable() + select only one entity = strange proxies' behaviour while iterating
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: NH-2650
>                 URL: http://216.121.112.228/browse/NH-2650
>             Project:  NHibernate
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 3.1.0
>            Reporter: Kirill Medvedev
>            Priority: Major
>
> I've created a test which consists of two classes:
> Man:
> <hibernate-mapping xmlns="urn:nhibernate-mapping-2.2" assembly="Domain" namespace="Domain" default-lazy="true">
>   <class name="Man" table="Men">
>     <id name="Id" column="Id">
>       <generator class="native"/>
>     </id>
>     <many-to-one name="Owner" class="Owner" column="OwnerId" cascade="save-update"/>
>     <property name="Name"/>
>   </class>
> </hibernate-mapping>
> Owner:
> <hibernate-mapping xmlns="urn:nhibernate-mapping-2.2" assembly="Domain" namespace="Domain" default-lazy="true">
>   <class name="Owner" table="Owners">
>     <id name="Id" column="Id">
>       <generator class="native"/>
>     </id>
>     <property name="Name"/>
>     <bag name="Men" cascade="save-update">
>       <key column="OwnerID"/>
>       <one-to-many class="Man"/>
>     </bag>
>   </class>
> </hibernate-mapping>
> If I write a simple hql-query without theta-joins, I get a lazily-loaded collection of proxies:
> IEnumerable<Man> men = session.CreateQuery("from Man").Enumerable<Man>();
> I can iterate through this collection without loading proxies:
> foreach (Man each in men) 
> {
>    //No code here, only iterating... Proxies are not loaded here, as expected.
> }
> But when I add theta-style join to this query...
> IEnumerable<Man> result = session.CreateQuery("select m from Man m left join m.Owner").Enumerable<Man>();
> NHibernate generates acceptable TSQL and builds SafetyEnumerable collection
> select man0_.Id as col_0_0_
> from   Men man0_
>        left outer join Owners owner1_
>          on man0_.OwnerId = owner1_.Id
> but (!) when I add iterating logic without accessing to any properties
> foreach (Man each in men) 
> {
>     //No code here! Only iterating through elements
> }
> new queries go to database each iteration, and load each entity:
> SELECT man0_.Id      as Id1_0_,
>        man0_.OwnerId as OwnerId1_0_,
>        man0_.Name    as Name1_0_
> FROM   Men man0_
> WHERE  man0_.Id = 5098 /* @p0 */
> Therefore I can't even convert this IEnumerable<Man> to List<Man> without loading the whole list of objects, because List constructor iterates through IEnumerable collection to add this collection to itself
> //public List(IEnumerable<T> collection) - constructor
> while (enumerator.MoveNext())
> {
>    this.Add(enumerator.Current);
> }
> Question: Is this behaviour designed to behave such way intentionally? It's strange that different hql queries return SafetyEnumerable collection which behaves differently while iterating through it (in case of non-theta joined queries, collection's entities are not loaded while iterating through it (without accessing any properties), but in theta-joined queries, entities are loaded while iterating through collection). Strange proxies' behaviour.
> Thank you.

-- 
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-2651) Regression when combining projections Conditional, Constant, and LikeExpression

[Francois W. (JIRA) <nh...@gm...>]

Regression when combining projections Conditional, Constant, and LikeExpression
-------------------------------------------------------------------------------

                 Key: NH-2651
                 URL: http://216.121.112.228/browse/NH-2651
             Project:  NHibernate
          Issue Type: Bug
          Components: Core
    Affects Versions: 3.1.0
            Reporter: Francois Ward
            Priority: Major
         Attachments: MissingParametersInConditionalWithLike.zip

As discussed on https://groups.google.com/forum/#!searchin/nhusers/regression$20conditional$20francois/nhusers/PQKwOhNkYqI/hJCf9HX_vv0J

This used to work in 2.1GA for sure, and I didn't notice the issue in 3.0, though it could have been there (I don't have a 3.0 environment handy anymore).

When combining Projections.Conditional, Constant in a LikeExpression, some parameters are not sent properly, in the wrong order or missing, resulting in invalid SQL

Test attached to reproduce the issue (hopefully I did it right)

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