Menu
▾
▴
nhibernate-issues — Updates to JIRA issues are sent to this list
You can subscribe to this list here.
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(110) |
Nov
(296) |
Dec
(107) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
(212) |
Feb
(263) |
Mar
(161) |
Apr
(183) |
May
(183) |
Jun
(75) |
Jul
(106) |
Aug
(88) |
Sep
(227) |
Oct
(143) |
Nov
(154) |
Dec
(53) |
| 2008 |
Jan
(77) |
Feb
|
Mar
|
Apr
(6) |
May
(103) |
Jun
(296) |
Jul
(54) |
Aug
|
Sep
(379) |
Oct
(283) |
Nov
(224) |
Dec
(214) |
| 2009 |
Jan
(129) |
Feb
(257) |
Mar
(136) |
Apr
(12) |
May
(329) |
Jun
(434) |
Jul
(375) |
Aug
(171) |
Sep
|
Oct
|
Nov
|
Dec
(54) |
| 2010 |
Jan
(198) |
Feb
(76) |
Mar
(3) |
Apr
(1) |
May
|
Jun
(62) |
Jul
(210) |
Aug
(447) |
Sep
(330) |
Oct
(257) |
Nov
(133) |
Dec
(453) |
| 2011 |
Jan
(240) |
Feb
(128) |
Mar
(442) |
Apr
(320) |
May
(428) |
Jun
(141) |
Jul
(13) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Fabio M. (JIRA) <nh...@gm...> - 2011-04-08 05:44:58
|
[ http://216.121.112.228/browse/NH-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20853#action_20853 ]
Fabio Maulo commented on NH-2611:
---------------------------------
sorry... I mean: "if you can't ...."
> Allow injectable/inheritance of Linq query provider
> ---------------------------------------------------
>
> Key: NH-2611
> URL: http://216.121.112.228/browse/NH-2611
> Project: NHibernate
> Issue Type: New Feature
> Components: Linq Provider
> Affects Versions: 3.1.0
> Reporter: Dan Jasek
> Priority: Minor
> Attachments: LinqVisibility.patch
>
>
> I have one final request for relaxing incaptulation in NH. These changes will allow me to create a custom Query Provider for ActiveRecord which properly manages the session lifecycle when executig a linq query.
> The applied patch makes a couple of methods in Linq.NhQueryProvider virtual or protected.
> It also moves the access of the internal session from PrepareQuery to Execute. If you can't make this change, could you make SetParameters protected instead?
> Finally, it adds a constructor to Linq.NhQueryable which will allow me to insert my custom query provider when creating a Query.
> 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
|
|
From: cremor (JIRA) <nh...@gm...> - 2011-04-08 05:33:54
|
[ http://216.121.112.228/browse/NH-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20852#action_20852 ]
cremor commented on NH-2623:
----------------------------
But in case of deferrable constraints Transaction.Commit can throw exceptions because of constraint violations and I'd like to handle these the same way like when they are thrown during flushing.
> ISQLExceptionConverter isn't used in AdoTransaction
> ---------------------------------------------------
>
> Key: NH-2623
> URL: http://216.121.112.228/browse/NH-2623
> Project: NHibernate
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.1.0
> Reporter: cremor
> Priority: Minor
> Attachments: NH2623.zip
>
>
> The attached test shows that exceptions that are thrown from the driver in Transaction.Begin/Commit/Rollback are not passed to an ISQLExceptionConverter.
--
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
|
|
From: Fabio M. (JIRA) <nh...@gm...> - 2011-04-08 05:26:55
|
[ http://216.121.112.228/browse/NH-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20851#action_20851 ]
Fabio Maulo commented on NH-2611:
---------------------------------
can you explain the reason because you need a custom IQueryProvider to work with NH ?
If you can do it here please use our dev-list.
Thanks.
> Allow injectable/inheritance of Linq query provider
> ---------------------------------------------------
>
> Key: NH-2611
> URL: http://216.121.112.228/browse/NH-2611
> Project: NHibernate
> Issue Type: New Feature
> Components: Linq Provider
> Affects Versions: 3.1.0
> Reporter: Dan Jasek
> Priority: Minor
> Attachments: LinqVisibility.patch
>
>
> I have one final request for relaxing incaptulation in NH. These changes will allow me to create a custom Query Provider for ActiveRecord which properly manages the session lifecycle when executig a linq query.
> The applied patch makes a couple of methods in Linq.NhQueryProvider virtual or protected.
> It also moves the access of the internal session from PrepareQuery to Execute. If you can't make this change, could you make SetParameters protected instead?
> Finally, it adds a constructor to Linq.NhQueryable which will allow me to insert my custom query provider when creating a Query.
> 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
|
|
From: Fabio M. (JIRA) <nh...@gm...> - 2011-04-08 05:24:47
|
[ http://216.121.112.228/browse/NH-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabio Maulo updated NH-2611:
----------------------------
Issue Type: New Feature (was: Patch)
Summary: Allow injectable/inheritance of Linq query provider (was: Allow inheritance of Linq query provider)
> Allow injectable/inheritance of Linq query provider
> ---------------------------------------------------
>
> Key: NH-2611
> URL: http://216.121.112.228/browse/NH-2611
> Project: NHibernate
> Issue Type: New Feature
> Components: Linq Provider
> Affects Versions: 3.1.0
> Reporter: Dan Jasek
> Priority: Minor
> Attachments: LinqVisibility.patch
>
>
> I have one final request for relaxing incaptulation in NH. These changes will allow me to create a custom Query Provider for ActiveRecord which properly manages the session lifecycle when executig a linq query.
> The applied patch makes a couple of methods in Linq.NhQueryProvider virtual or protected.
> It also moves the access of the internal session from PrepareQuery to Execute. If you can't make this change, could you make SetParameters protected instead?
> Finally, it adds a constructor to Linq.NhQueryable which will allow me to insert my custom query provider when creating a Query.
> 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
|
|
From: Fabio M. (JIRA) <nh...@gm...> - 2011-04-08 05:22:56
|
[ http://216.121.112.228/browse/NH-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20850#action_20850 ]
Fabio Maulo commented on NH-2611:
---------------------------------
Not enough.
We are casting it for Future...
Going to change the issue title and type.
> Allow inheritance of Linq query provider
> ----------------------------------------
>
> Key: NH-2611
> URL: http://216.121.112.228/browse/NH-2611
> Project: NHibernate
> Issue Type: Patch
> Components: Linq Provider
> Affects Versions: 3.1.0
> Reporter: Dan Jasek
> Priority: Minor
> Attachments: LinqVisibility.patch
>
>
> I have one final request for relaxing incaptulation in NH. These changes will allow me to create a custom Query Provider for ActiveRecord which properly manages the session lifecycle when executig a linq query.
> The applied patch makes a couple of methods in Linq.NhQueryProvider virtual or protected.
> It also moves the access of the internal session from PrepareQuery to Execute. If you can't make this change, could you make SetParameters protected instead?
> Finally, it adds a constructor to Linq.NhQueryable which will allow me to insert my custom query provider when creating a Query.
> 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
|
|
From: Fabio M. (JIRA) <nh...@gm...> - 2011-04-08 05:10:47
|
[ http://216.121.112.228/browse/NH-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabio Maulo resolved NH-2612.
-----------------------------
Resolution: Fixed
Fix Version/s: 3.2.0
> Move the lambda con to the same namespace than Configuration
> ------------------------------------------------------------
>
> Key: NH-2612
> URL: http://216.121.112.228/browse/NH-2612
> Project: NHibernate
> Issue Type: Improvement
> Components: Core
> Affects Versions: 3.1.0
> Reporter: Jose F. Romaniello
> Fix For: 3.2.0
>
>
> I love the lambda configuration; this one:
> http://fabiomaulo.blogspot.com/2009/07/nhibernate-configuration-through.html
> but it is not easy to discover, and each time I'd use it I have to look to other projects or go to Fabio's blog.
> I don't want to screw the statistics on Fabio's blog :)
> My suggestion is to move the lambdas to the same namespace than the configuration. I know it is a breaking change but i guess other can live with that :)
--
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
|
|
From: Fabio M. (JIRA) <nh...@gm...> - 2011-04-08 05:04:49
|
[ http://216.121.112.228/browse/NH-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabio Maulo closed NH-2614.
---------------------------
Resolution: Won't Fix
> Have HQL Support "Where Property = null"
> ----------------------------------------
>
> Key: NH-2614
> URL: http://216.121.112.228/browse/NH-2614
> Project: NHibernate
> Issue Type: Improvement
> Components: DataProviders / Dialects
> Affects Versions: 3.2.0
> Reporter: Ricardo Peres
>
> HQL, as SQL, only allows comparison with null with syntax "where property is null" instead of the ordinary "where property = null". Sometimes, we do not know if the value that we want to filter by is null or not, when we use properties, for example:
> var q = session.Query("from MyEntity e where e.Property = :value").SetProperty("value", someValue);
> If someValue is null, we would have to rewrite the query as:
> var q = session.Query("from MyEntity e where e.Property is null");
> I believe it would be helpful if HQL could support the same syntax for null and non-null values.
--
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
|
|
From: Ricardo P. (JIRA) <nh...@gm...> - 2011-04-08 05:03:05
|
[ http://216.121.112.228/browse/NH-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20849#action_20849 ]
Ricardo Peres commented on NH-2632:
-----------------------------------
I think it is not entirely fixed... It doesn't throw, but, now, if I mark the class as not lazy, lazy properties are ignored (treated as not lazy). Perhaps matter for a new JIRA issue?
> Lazy Properties Causing An Exception If Containing Class Is Set To Not Lazy
> ---------------------------------------------------------------------------
>
> Key: NH-2632
> URL: http://216.121.112.228/browse/NH-2632
> Project: NHibernate
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.1.0
> Reporter: Ricardo Peres
> Fix For: 3.2.0
>
>
> As discussed in NHibernate-Development (http://groups.google.com/group/nhibernate-development/browse_thread/thread/703b76e5b82595d6), when a property is set to lazy but its containing class is set to not lazy, an exception occurs when loading an entity of this 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
|
|
From: Fabio M. (JIRA) <nh...@gm...> - 2011-04-08 05:02:54
|
[ http://216.121.112.228/browse/NH-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20848#action_20848 ]
Fabio Maulo commented on NH-2629:
---------------------------------
Please send us a mapping and classes to recreate the issue.
Thanks.
P.S. do it ASAP if you want it fixed for NH3.2
> Typedef reference in composite key (in hbm files)
> -------------------------------------------------
>
> Key: NH-2629
> URL: http://216.121.112.228/browse/NH-2629
> Project: NHibernate
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.0.0.GA
> Reporter: Massimiliano Alberti
>
> I'm using a UserType. I have a typedef at the beginning of the file, like this:
> <?xml version="1.0" encoding="utf-8" ?>
> <hibernate-mapping xmlns="urn:nhibernate-mapping-2.2" default-lazy="false">
> <typedef name="AnsiStringTrimmed" class="Utils.AnsiStringTrimmed, Utils" />
> If I reference AnsiStringTrimmed in a property it works, like this:
> <property name="Field" type="AnsiStringTrimmed" not-null="true" length="6" />
> But if I try to use it in a key-property element it doesn't work, like this:
> <composite-id name="PKey" class="Project.PKey, Project">
> <key-property name="Field" type="AnsiStringTrimmed" length="3" />
> I get a MappingException like this: Could not determine type for: AnsiStringTrimmed, for columns: NHibernate.Mapping.Column(Field).
> If I use the full name of the usertype it works correctly (Utils.AnsiStringTrimmed, Utils)
--
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
|
|
From: Fabio M. (JIRA) <nh...@gm...> - 2011-04-08 05:00:47
|
[ http://216.121.112.228/browse/NH-2627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabio Maulo resolved NH-2627.
-----------------------------
Resolution: Fixed
Fix Version/s: 3.2.0
> Cloning subcriteria loses WithClause
> ------------------------------------
>
> Key: NH-2627
> URL: http://216.121.112.228/browse/NH-2627
> Project: NHibernate
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.2.0
> Reporter: Vitaliy Litovskiy
> Fix For: 3.2.0
>
> Attachments: subcriteria_clone_fix.patch
>
>
> Method CloneSubcriteria in Subcriteria class doesn't clone the original WithClause.
> steps to reproduce in pseudo code:
> var criteria = DetachedCriteria.For<Model>();
> criteria.AddAlias("Collection", "item", JoinType.LeftOuterJoin, Restrictions.Eq("item.Property", "somve value"))
> var cloneCriteria = CriteriaTransformer.Clone(criteria);
> As a result criteria and cloneCriteria will return different results. This is cause by additional ON conditions for JOIN are lost in the SQL.
> It seems that i've found how to fix the issue, but i haven't set up the development environment yet and cant build NHibernate solution and run tests. The possible patch is attached.
--
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
|
|
From: Ricardo P. (JIRA) <nh...@gm...> - 2011-04-08 04:47:56
|
[ http://216.121.112.228/browse/NH-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20847#action_20847 ]
Ricardo Peres commented on NH-2620:
-----------------------------------
In this case, why does the property exist in IStatelessSession?
> Stateless Session, Named SQL Query and Flush Mode
> -------------------------------------------------
>
> Key: NH-2620
> URL: http://216.121.112.228/browse/NH-2620
> Project: NHibernate
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.1.0
> Reporter: Ricardo Peres
>
> When the flush mode for a named SQL query is specified and the named query is called by a stateless session, it throws a method not found exception due to the fact that StatelessSessionImpl does not have a FlushMode property.
> Example:
> <hibernate-mapping xmlns="urn:nhibernate-mapping-2.2" auto-import="false" namespace="NHibernateGeneratorsTest.Domain" assembly="NHibernateGeneratorsTest">
> <query name="AllCustomers" read-only="true" cacheable="false" flush-mode="never" fetch-size="500">
> <![CDATA[
> from Customer c
> ]]>
> </query>
> </hibernate-mapping>
> using (IStatelessSession session = factory.OpenStatelessSession())
> {
> session.GetNamedQuery("AllCustomers").List();
> }
--
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
|
|
From: Fabio M. (JIRA) <nh...@gm...> - 2011-04-08 04:43:51
|
[ http://216.121.112.228/browse/NH-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabio Maulo closed NH-2631.
---------------------------
Resolution: Not an Issue
Please have a look to NHibernate.Test.SqlTest.Custom.Oracle there are various examples.
> Selectable stored procedure with ORACLE
> ---------------------------------------
>
> Key: NH-2631
> URL: http://216.121.112.228/browse/NH-2631
> Project: NHibernate
> Issue Type: Bug
> Components: Core, DataProviders / Dialects
> Affects Versions: 3.0.0.GA
> Reporter: Anupam Mishra
> Priority: Minor
> Attachments: Stored Procedure Problem.txt
>
>
> Following is my Stored Procedure:
> create or replace PROCEDURE GETPERSONTEST (io_cursor IN OUT sys_refcursor)
> IS
> BEGIN
> OPEN io_cursor FOR
> SELECT EMP_ID,EMP_NAME,EMP_PASSWORD,TEAM_ASSOCIATED_WITH,IS_CAPTAIN,NO_OF_MOM,BALANCE FROM employee ;
> END GETPERSONTEST;
> Nhibernate Mapping:
> <sql-query name="selemployee" callable="true">
> <return class="DomainObject.Employee,DomainObject" >
> <return-property name="EmployeeId" column="Emp_ID"/>
> <return-property name="EmployeeName" column="EMP_NAME"/>
> <return-property name="EmployeePassword" column="EMP_PASSWORD"/>
> <return-property name="TeamAssociatedWith" column="TEAM_ASSOCIATED_WITH"/>
> <return-property name="IsCaptain" column="IS_CAPTAIN"/>
> <return-property name="NumberOfMOM" column="NO_OF_MOM"/>
> <return-property name="Balance" column="BALANCE"/>
> </return>
> {call GETPERSONTEST(?)}
> </sql-query>
> Problem in Executing throwing following exception
> Exception stack trace is attached.
> could not execute query
> [ {call GETPERSONTEST(@p0)} ]
> It will be a great help if suggest some approach to make it work.
> As this problem is coming with every version of NHibernate.Create ,Update and Delete is working fine only facing this problem in case of select.
--
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
|
|
From: Fabio M. (JIRA) <nh...@gm...> - 2011-04-08 04:37:47
|
[ http://216.121.112.228/browse/NH-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabio Maulo updated NH-2631:
----------------------------
Component/s: DataProviders / Dialects
Summary: Selectable stored procedure with ORACLE (was: Problem in executing stored procedure with NHibernate 3 as well.)
> Selectable stored procedure with ORACLE
> ---------------------------------------
>
> Key: NH-2631
> URL: http://216.121.112.228/browse/NH-2631
> Project: NHibernate
> Issue Type: Bug
> Components: Core, DataProviders / Dialects
> Affects Versions: 3.0.0.GA
> Reporter: Anupam Mishra
> Priority: Minor
> Attachments: Stored Procedure Problem.txt
>
>
> Following is my Stored Procedure:
> create or replace PROCEDURE GETPERSONTEST (io_cursor IN OUT sys_refcursor)
> IS
> BEGIN
> OPEN io_cursor FOR
> SELECT EMP_ID,EMP_NAME,EMP_PASSWORD,TEAM_ASSOCIATED_WITH,IS_CAPTAIN,NO_OF_MOM,BALANCE FROM employee ;
> END GETPERSONTEST;
> Nhibernate Mapping:
> <sql-query name="selemployee" callable="true">
> <return class="DomainObject.Employee,DomainObject" >
> <return-property name="EmployeeId" column="Emp_ID"/>
> <return-property name="EmployeeName" column="EMP_NAME"/>
> <return-property name="EmployeePassword" column="EMP_PASSWORD"/>
> <return-property name="TeamAssociatedWith" column="TEAM_ASSOCIATED_WITH"/>
> <return-property name="IsCaptain" column="IS_CAPTAIN"/>
> <return-property name="NumberOfMOM" column="NO_OF_MOM"/>
> <return-property name="Balance" column="BALANCE"/>
> </return>
> {call GETPERSONTEST(?)}
> </sql-query>
> Problem in Executing throwing following exception
> Exception stack trace is attached.
> could not execute query
> [ {call GETPERSONTEST(@p0)} ]
> It will be a great help if suggest some approach to make it work.
> As this problem is coming with every version of NHibernate.Create ,Update and Delete is working fine only facing this problem in case of select.
--
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
|
|
From: Fabio M. (JIRA) <nh...@gm...> - 2011-04-08 04:35:50
|
[ http://216.121.112.228/browse/NH-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabio Maulo closed NH-2620.
---------------------------
Resolution: Not an Issue
NotSupportedException in stateless session is a clear explication, it mean: Not Supported by the class you are using.
> Stateless Session, Named SQL Query and Flush Mode
> -------------------------------------------------
>
> Key: NH-2620
> URL: http://216.121.112.228/browse/NH-2620
> Project: NHibernate
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.1.0
> Reporter: Ricardo Peres
>
> When the flush mode for a named SQL query is specified and the named query is called by a stateless session, it throws a method not found exception due to the fact that StatelessSessionImpl does not have a FlushMode property.
> Example:
> <hibernate-mapping xmlns="urn:nhibernate-mapping-2.2" auto-import="false" namespace="NHibernateGeneratorsTest.Domain" assembly="NHibernateGeneratorsTest">
> <query name="AllCustomers" read-only="true" cacheable="false" flush-mode="never" fetch-size="500">
> <![CDATA[
> from Customer c
> ]]>
> </query>
> </hibernate-mapping>
> using (IStatelessSession session = factory.OpenStatelessSession())
> {
> session.GetNamedQuery("AllCustomers").List();
> }
--
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
|
|
From: Fabio M. (JIRA) <nh...@gm...> - 2011-04-08 04:32:53
|
[ http://216.121.112.228/browse/NH-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabio Maulo closed NH-2623.
---------------------------
Resolution: Not an Issue
It is a transaction exception, not an exception executing an SQL command.
> ISQLExceptionConverter isn't used in AdoTransaction
> ---------------------------------------------------
>
> Key: NH-2623
> URL: http://216.121.112.228/browse/NH-2623
> Project: NHibernate
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.1.0
> Reporter: cremor
> Priority: Minor
> Attachments: NH2623.zip
>
>
> The attached test shows that exceptions that are thrown from the driver in Transaction.Begin/Commit/Rollback are not passed to an ISQLExceptionConverter.
--
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
|
|
From: Fabio M. (JIRA) <nh...@gm...> - 2011-04-07 23:14:47
|
[ http://216.121.112.228/browse/NH-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabio Maulo resolved NH-2632.
-----------------------------
Resolution: Fixed
Fix Version/s: 3.2.0
> Lazy Properties Causing An Exception If Containing Class Is Set To Not Lazy
> ---------------------------------------------------------------------------
>
> Key: NH-2632
> URL: http://216.121.112.228/browse/NH-2632
> Project: NHibernate
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.1.0
> Reporter: Ricardo Peres
> Fix For: 3.2.0
>
>
> As discussed in NHibernate-Development (http://groups.google.com/group/nhibernate-development/browse_thread/thread/703b76e5b82595d6), when a property is set to lazy but its containing class is set to not lazy, an exception occurs when loading an entity of this 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
|
|
From: Ricardo P. (JIRA) <nh...@gm...> - 2011-04-07 21:24:55
|
[ http://216.121.112.228/browse/NH-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20843#action_20843 ]
Ricardo Peres commented on NH-2632:
-----------------------------------
using (ISession session = sessionFactory.OpenSession())
using (ITransaction tx = session.BeginTransaction())
{
Customer c = new Customer{ Name = "Ricardo Peres", Address = "Portugal" };
Order o = new Order{ Date = DateTime.Today, Customer = c };
session.Save(c);
tx.Commit();
}
using (ISession session = sessionFactory.OpenSession())
{
Customer c = session.Query<Customer>().First();
}
> Lazy Properties Causing An Exception If Containing Class Is Set To Not Lazy
> ---------------------------------------------------------------------------
>
> Key: NH-2632
> URL: http://216.121.112.228/browse/NH-2632
> Project: NHibernate
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.1.0
> Reporter: Ricardo Peres
>
> As discussed in NHibernate-Development (http://groups.google.com/group/nhibernate-development/browse_thread/thread/703b76e5b82595d6), when a property is set to lazy but its containing class is set to not lazy, an exception occurs when loading an entity of this 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
|
|
From: Ricardo P. (JIRA) <nh...@gm...> - 2011-04-07 21:07:55
|
[ http://216.121.112.228/browse/NH-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20842#action_20842 ]
Ricardo Peres commented on NH-2632:
-----------------------------------
Sorry, Fabio:
mapper.Class<Order>(ca =>
{
ca.Table("`ORDER`");
ca.Lazy(false);
ca.Id(x => x.Id, map =>
{
map.Column("`ID`");
map.Generator(Generators.HighLow, g => g.Params(new { max_lo = "1000" }));
});
ca.Property(x => x.Date, x =>
{
x.NotNullable(true);
x.Column("`DATE`");
});
ca.ManyToOne(c => c.Customer, a =>
{
a.Column("`CUSTOMERID`");
a.NotNullable(true);
a.Cascade(Cascade.All);
a.Fetch(FetchKind.Join);
});
}
> Lazy Properties Causing An Exception If Containing Class Is Set To Not Lazy
> ---------------------------------------------------------------------------
>
> Key: NH-2632
> URL: http://216.121.112.228/browse/NH-2632
> Project: NHibernate
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.1.0
> Reporter: Ricardo Peres
>
> As discussed in NHibernate-Development (http://groups.google.com/group/nhibernate-development/browse_thread/thread/703b76e5b82595d6), when a property is set to lazy but its containing class is set to not lazy, an exception occurs when loading an entity of this 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
|
|
From: Dario Q. (JIRA) <nh...@gm...> - 2011-04-07 20:38:47
|
[ http://216.121.112.228/browse/NHV-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dario Quintana updated NHV-113:
-------------------------------
Priority: Major (was: Trivial)
> Integration with System.ComponentModel.DataAnnotations
> ------------------------------------------------------
>
> Key: NHV-113
> URL: http://216.121.112.228/browse/NHV-113
> Project: NHibernate.Validator
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.4.0 Alpha1
> Reporter: Ricardo Peres
> Priority: Major
>
> .NET 3.5 has a set of APIs dealing with attribute-based entity validation: System.ComponentModel.DataAnnotations. It defines a base attribute class, ValidationAttribute. This is becoming, IMO, the de facto standard for this type of validation (for example, the Enterprise Library 5 Validation Application Block is built on top of it.
> My proposal is that EmbeddedRuleArgsAttribute derives from ValidationAttribute, so that we can have a base validation class that exists in standard .NET.
--
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
|
|
From: Fabio M. (JIRA) <nh...@gm...> - 2011-04-07 19:57:55
|
[ http://216.121.112.228/browse/NH-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20841#action_20841 ]
Fabio Maulo commented on NH-2632:
---------------------------------
The mapping of Order class ?
> Lazy Properties Causing An Exception If Containing Class Is Set To Not Lazy
> ---------------------------------------------------------------------------
>
> Key: NH-2632
> URL: http://216.121.112.228/browse/NH-2632
> Project: NHibernate
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.1.0
> Reporter: Ricardo Peres
>
> As discussed in NHibernate-Development (http://groups.google.com/group/nhibernate-development/browse_thread/thread/703b76e5b82595d6), when a property is set to lazy but its containing class is set to not lazy, an exception occurs when loading an entity of this 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
|
|
From: Fabio M. (JIRA) <nh...@gm...> - 2011-04-07 19:31:46
|
[ http://216.121.112.228/browse/NH-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabio Maulo resolved NH-2630.
-----------------------------
Resolution: Fixed
Fix Version/s: 3.2.0
> Truncate SQL parameter logging of very long strings
> ---------------------------------------------------
>
> Key: NH-2630
> URL: http://216.121.112.228/browse/NH-2630
> Project: NHibernate
> Issue Type: Improvement
> Components: Core
> Affects Versions: 3.1.0
> Reporter: cremor
> Priority: Minor
> Fix For: 3.2.0
>
>
> Similar to NH-2518 it would be great if very long strings (that would be mapped to a CLOB, VARCHAR(MAX) or a similar column) would be truncated in the SQL parameter logging.
> A good max length would be 4000 chars in my opinion.
--
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
|
|
From: Fabio M. (JIRA) <nh...@gm...> - 2011-04-07 19:11:49
|
[ http://216.121.112.228/browse/NH-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabio Maulo updated NH-2624:
----------------------------
Priority: Minor (was: Critical)
> MultiCriteria does not work with criteria created using JoinQueryOver
> ---------------------------------------------------------------------
>
> Key: NH-2624
> URL: http://216.121.112.228/browse/NH-2624
> Project: NHibernate
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.1.0
> Reporter: xelibrion
> Assignee: Richard Brown
> Priority: Minor
>
> I've got exception
> System.InvalidCastException: Unable to cast object of type 'Subcriteria' to type 'NHibernate.Impl.CriteriaImpl'.
> at NHibernate.Impl.MultiCriteriaImpl.CreateCriteriaLoaders() in d:\CSharp\NH\NH\nhibernate\src\NHibernate\Impl\MultiCriteriaImpl.cs:line 287
> at NHibernate.Impl.MultiCriteriaImpl.List() in d:\CSharp\NH\NH\nhibernate\src\NHibernate\Impl\MultiCriteriaImpl.cs:line 73
> in code
> var queryOver = Session.QueryOver<Post>()
> .Fetch(x => x.Author).Eager
> .Fetch(x => x.Blog).Eager
> .JoinQueryOver(x => x.SearchRequests)
> .Where(x => x.Id == context.SearchRequestId)
> .TransformUsing(Transformers.DistinctRootEntity)
> .Skip(context.PageIndex*pageSize)
> .Take(pageSize);
> Session.CreateMultiCriteria()
> .Add(queryOver.UnderlyingCriteria)
> .Add(queryOver.ToRowCountQuery().UnderlyingCriteria)
> .List();
> I've found workaround using JoinAlias
--
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
|
|
From: Fabio M. (JIRA) <nh...@gm...> - 2011-04-07 19:09:52
|
[ http://216.121.112.228/browse/NH-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabio Maulo updated NH-2631:
----------------------------
Priority: Minor (was: Major)
> Problem in executing stored procedure with NHibernate 3 as well.
> ----------------------------------------------------------------
>
> Key: NH-2631
> URL: http://216.121.112.228/browse/NH-2631
> Project: NHibernate
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.0.0.GA
> Reporter: Anupam Mishra
> Priority: Minor
> Attachments: Stored Procedure Problem.txt
>
>
> Following is my Stored Procedure:
> create or replace PROCEDURE GETPERSONTEST (io_cursor IN OUT sys_refcursor)
> IS
> BEGIN
> OPEN io_cursor FOR
> SELECT EMP_ID,EMP_NAME,EMP_PASSWORD,TEAM_ASSOCIATED_WITH,IS_CAPTAIN,NO_OF_MOM,BALANCE FROM employee ;
> END GETPERSONTEST;
> Nhibernate Mapping:
> <sql-query name="selemployee" callable="true">
> <return class="DomainObject.Employee,DomainObject" >
> <return-property name="EmployeeId" column="Emp_ID"/>
> <return-property name="EmployeeName" column="EMP_NAME"/>
> <return-property name="EmployeePassword" column="EMP_PASSWORD"/>
> <return-property name="TeamAssociatedWith" column="TEAM_ASSOCIATED_WITH"/>
> <return-property name="IsCaptain" column="IS_CAPTAIN"/>
> <return-property name="NumberOfMOM" column="NO_OF_MOM"/>
> <return-property name="Balance" column="BALANCE"/>
> </return>
> {call GETPERSONTEST(?)}
> </sql-query>
> Problem in Executing throwing following exception
> Exception stack trace is attached.
> could not execute query
> [ {call GETPERSONTEST(@p0)} ]
> It will be a great help if suggest some approach to make it work.
> As this problem is coming with every version of NHibernate.Create ,Update and Delete is working fine only facing this problem in case of select.
--
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
|
|
From: Fabio M. (JIRA) <nh...@gm...> - 2011-04-07 17:31:46
|
[ http://216.121.112.228/browse/NH-2628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabio Maulo resolved NH-2628.
-----------------------------
Resolution: Fixed
Fix Version/s: 3.2.0
Fixed fixing NH-2622
> Fails to create proxy for class with method that has argument "ref of Dictionary<string, string>"
> -------------------------------------------------------------------------------------------------
>
> Key: NH-2628
> URL: http://216.121.112.228/browse/NH-2628
> Project: NHibernate
> Issue Type: Bug
> Components: ByteCode providers
> Affects Versions: 3.2.0
> Reporter: Pavel Peker
> Priority: Critical
> Fix For: 3.2.0
>
>
> fails in DefaultMethodEmitter.cs
> private static void SaveRefArguments(ILGenerator IL, ParameterInfo[] parameters)
> when class has method with parameter "ref Dictionary<string, string>"
> typeName = typeName.Replace("&", "");
> System.Type unboxedType = System.Type.GetType(typeName);
> IL.Emit(OpCodes.Unbox_Any, unboxedType);
> System.Type.GetType(typeName) returns null in this case. Changed code above into
> string typeName = param.ParameterType.FullName;
> instead
> string typeName = param.ParameterType.Name;
> and it fixed problem.
--
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
|
|
From: Fabio M. (JIRA) <nh...@gm...> - 2011-04-07 17:19:48
|
[ http://216.121.112.228/browse/NH-2622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabio Maulo resolved NH-2622.
-----------------------------
Resolution: Fixed
Fix Version/s: 3.2.0
> Proxying fails for methods with out and ref arguments
> -----------------------------------------------------
>
> Key: NH-2622
> URL: http://216.121.112.228/browse/NH-2622
> Project: NHibernate
> Issue Type: Bug
> Components: ByteCode providers
> Affects Versions: 3.2.0
> Reporter: Patrick Earl
> Priority: Critical
> Fix For: 3.2.0
>
>
> There is an ignored test case in DynamicProxyTests/ProxiedMembers. One required fix is to change
> string typeName = param.ParameterType.Name;
> to:
> string typeName = param.ParameterType.FullName;
> in:
> DefaultMethodEmitter.cs
> However, after doing this, the test still crashes the runtime, likely due to invalid IL being generated.
--
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
|
35 messages has been excluded from this view by a project administrator.
