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: Ricardo P. (JIRA) <nh...@gm...> - 2011-04-08 23:36:53
|
Id Property With Private Setter Not Set With Lazy Classes
---------------------------------------------------------
Key: NH-2638
URL: http://216.121.112.228/browse/NH-2638
Project: NHibernate
Issue Type: Bug
Components: Core
Affects Versions: 3.2.0
Reporter: Ricardo Peres
Attachments: Test.cs
When I have a class with a private id setter, if the class is lazy, then the id is not set.
No exception occurs, it simply is not set. Mapping is done with the new mapping by code.
Tested with the trunk version, as of 00:00.
--
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: Igor K. (JIRA) <nh...@gm...> - 2011-04-08 18:57:03
|
[ http://216.121.112.228/browse/NH-2637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20867#action_20867 ]
Igor Krupin commented on NH-2637:
---------------------------------
Oh, sorry.
The bug is this. I have a database table called STUDENT.
So we have something like
STUDENT.FIRSTNAME
STUDENT.LASTNAME
In Oracle we uppercase everything (I hate Oracle, but whatever).
Then, we have a class called Student, with properties FirstName and LastName (mixed case).
The we do something like:
ISQLQuery query = session.CreateSQLQuery("SELECT FIRSTNAME, LASTNAME FROM STUDENT");
query.SetResultTransformer(Transformers.AliasToBean(typeof(Student)));
PROBLEM:
AiasToBean will complain that it can't find setter property "FIRSTNAME". I traced the code to NHibernate.Properties.BasicPropertyAccessor.GetSetterOrNull method. It's looking for FIRSTNAME property, case sensitive, and can't find it.
Igor
> NHibernate.Properties.BasicPropertyAccessor.GetSetterOrNull is case sensitive
> -----------------------------------------------------------------------------
>
> Key: NH-2637
> URL: http://216.121.112.228/browse/NH-2637
> Project: NHibernate
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.1.0
> Reporter: Igor Krupin
> Priority: Major
> Attachments: Capture.PNG
>
>
> We are running NH 2.1 and discovered this bug trying to upgrade to NH 3.1. We do a lot of AliasToBean stuff, mapping tables to DTOs, and AliasToBean will call this method to get the properties. Problem is, it's case sensitive now! Reading code comments i see this:
> ============ <CODE SNIPPET> ================
> BindingFlags bindingFlags = BindingFlags.Instance | BindingFlags.Public | BindingFlags.NonPublic | BindingFlags.DeclaredOnly;
> if (type.IsValueType)
> {
> // the BindingFlags.IgnoreCase is important here because if type is a struct, the GetProperty method does
> // not ignore case by default. If type is a class, it _does_ ignore case... we're better off explicitly
> // stating that casing should be ignored so we get the same behavior for both structs and classes
> bindingFlags = bindingFlags | BindingFlags.IgnoreCase;
> }
> ============ </CODE SNIPPET> ================
> "If type is a class, it _does_ ignore case..." -- incorrect. By default in classes case will _not_ be ignored, you explicitly have to specify it using a flag, same as you do for value type.
> The fix for this is rather simple, just add the BindingFlags.IgnoreCase flag and all's good. No need for the "if (type.IsValueType)" anymore either. GetGetterOrNull suffers from the same.
> Thank You!!!
> Igor
--
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 18:40:01
|
[ http://216.121.112.228/browse/NH-2637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20866#action_20866 ]
Fabio Maulo commented on NH-2637:
---------------------------------
which is the bug ?
I can't see it.
> NHibernate.Properties.BasicPropertyAccessor.GetSetterOrNull is case sensitive
> -----------------------------------------------------------------------------
>
> Key: NH-2637
> URL: http://216.121.112.228/browse/NH-2637
> Project: NHibernate
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.1.0
> Reporter: Igor Krupin
> Priority: Major
> Attachments: Capture.PNG
>
>
> We are running NH 2.1 and discovered this bug trying to upgrade to NH 3.1. We do a lot of AliasToBean stuff, mapping tables to DTOs, and AliasToBean will call this method to get the properties. Problem is, it's case sensitive now! Reading code comments i see this:
> ============ <CODE SNIPPET> ================
> BindingFlags bindingFlags = BindingFlags.Instance | BindingFlags.Public | BindingFlags.NonPublic | BindingFlags.DeclaredOnly;
> if (type.IsValueType)
> {
> // the BindingFlags.IgnoreCase is important here because if type is a struct, the GetProperty method does
> // not ignore case by default. If type is a class, it _does_ ignore case... we're better off explicitly
> // stating that casing should be ignored so we get the same behavior for both structs and classes
> bindingFlags = bindingFlags | BindingFlags.IgnoreCase;
> }
> ============ </CODE SNIPPET> ================
> "If type is a class, it _does_ ignore case..." -- incorrect. By default in classes case will _not_ be ignored, you explicitly have to specify it using a flag, same as you do for value type.
> The fix for this is rather simple, just add the BindingFlags.IgnoreCase flag and all's good. No need for the "if (type.IsValueType)" anymore either. GetGetterOrNull suffers from the same.
> Thank You!!!
> Igor
--
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: Igor K. (JIRA) <nh...@gm...> - 2011-04-08 18:18:03
|
[ http://216.121.112.228/browse/NH-2637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20865#action_20865 ]
Igor Krupin commented on NH-2637:
---------------------------------
Here's a link to MSDN documentation for "Type.GetProperty Method (String)"
http://msdn.microsoft.com/en-us/library/kz0a8sxy.aspx
"The search for name is case-sensitive. The search includes public static and public instance properties."
> NHibernate.Properties.BasicPropertyAccessor.GetSetterOrNull is case sensitive
> -----------------------------------------------------------------------------
>
> Key: NH-2637
> URL: http://216.121.112.228/browse/NH-2637
> Project: NHibernate
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.1.0
> Reporter: Igor Krupin
> Priority: Major
> Attachments: Capture.PNG
>
>
> We are running NH 2.1 and discovered this bug trying to upgrade to NH 3.1. We do a lot of AliasToBean stuff, mapping tables to DTOs, and AliasToBean will call this method to get the properties. Problem is, it's case sensitive now! Reading code comments i see this:
> ============ <CODE SNIPPET> ================
> BindingFlags bindingFlags = BindingFlags.Instance | BindingFlags.Public | BindingFlags.NonPublic | BindingFlags.DeclaredOnly;
> if (type.IsValueType)
> {
> // the BindingFlags.IgnoreCase is important here because if type is a struct, the GetProperty method does
> // not ignore case by default. If type is a class, it _does_ ignore case... we're better off explicitly
> // stating that casing should be ignored so we get the same behavior for both structs and classes
> bindingFlags = bindingFlags | BindingFlags.IgnoreCase;
> }
> ============ </CODE SNIPPET> ================
> "If type is a class, it _does_ ignore case..." -- incorrect. By default in classes case will _not_ be ignored, you explicitly have to specify it using a flag, same as you do for value type.
> The fix for this is rather simple, just add the BindingFlags.IgnoreCase flag and all's good. No need for the "if (type.IsValueType)" anymore either. GetGetterOrNull suffers from the same.
> Thank You!!!
> Igor
--
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: Igor K. (JIRA) <nh...@gm...> - 2011-04-08 18:11:50
|
[ http://216.121.112.228/browse/NH-2637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Krupin updated NH-2637:
----------------------------
Attachment: Capture.PNG
> NHibernate.Properties.BasicPropertyAccessor.GetSetterOrNull is case sensitive
> -----------------------------------------------------------------------------
>
> Key: NH-2637
> URL: http://216.121.112.228/browse/NH-2637
> Project: NHibernate
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.1.0
> Reporter: Igor Krupin
> Priority: Major
> Attachments: Capture.PNG
>
>
> We are running NH 2.1 and discovered this bug trying to upgrade to NH 3.1. We do a lot of AliasToBean stuff, mapping tables to DTOs, and AliasToBean will call this method to get the properties. Problem is, it's case sensitive now! Reading code comments i see this:
> ============ <CODE SNIPPET> ================
> BindingFlags bindingFlags = BindingFlags.Instance | BindingFlags.Public | BindingFlags.NonPublic | BindingFlags.DeclaredOnly;
> if (type.IsValueType)
> {
> // the BindingFlags.IgnoreCase is important here because if type is a struct, the GetProperty method does
> // not ignore case by default. If type is a class, it _does_ ignore case... we're better off explicitly
> // stating that casing should be ignored so we get the same behavior for both structs and classes
> bindingFlags = bindingFlags | BindingFlags.IgnoreCase;
> }
> ============ </CODE SNIPPET> ================
> "If type is a class, it _does_ ignore case..." -- incorrect. By default in classes case will _not_ be ignored, you explicitly have to specify it using a flag, same as you do for value type.
> The fix for this is rather simple, just add the BindingFlags.IgnoreCase flag and all's good. No need for the "if (type.IsValueType)" anymore either. GetGetterOrNull suffers from the same.
> Thank You!!!
> Igor
--
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: Igor K. (JIRA) <nh...@gm...> - 2011-04-08 18:09:50
|
NHibernate.Properties.BasicPropertyAccessor.GetSetterOrNull is case sensitive
-----------------------------------------------------------------------------
Key: NH-2637
URL: http://216.121.112.228/browse/NH-2637
Project: NHibernate
Issue Type: Bug
Components: Core
Affects Versions: 3.1.0
Reporter: Igor Krupin
Priority: Major
We are running NH 2.1 and discovered this bug trying to upgrade to NH 3.1. We do a lot of AliasToBean stuff, mapping tables to DTOs, and AliasToBean will call this method to get the properties. Problem is, it's case sensitive now! Reading code comments i see this:
============ <CODE SNIPPET> ================
BindingFlags bindingFlags = BindingFlags.Instance | BindingFlags.Public | BindingFlags.NonPublic | BindingFlags.DeclaredOnly;
if (type.IsValueType)
{
// the BindingFlags.IgnoreCase is important here because if type is a struct, the GetProperty method does
// not ignore case by default. If type is a class, it _does_ ignore case... we're better off explicitly
// stating that casing should be ignored so we get the same behavior for both structs and classes
bindingFlags = bindingFlags | BindingFlags.IgnoreCase;
}
============ </CODE SNIPPET> ================
"If type is a class, it _does_ ignore case..." -- incorrect. By default in classes case will _not_ be ignored, you explicitly have to specify it using a flag, same as you do for value type.
The fix for this is rather simple, just add the BindingFlags.IgnoreCase flag and all's good. No need for the "if (type.IsValueType)" anymore either. GetGetterOrNull suffers from the same.
Thank You!!!
Igor
--
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: Patrick E. (JIRA) <nh...@gm...> - 2011-04-08 17:53:49
|
[ http://216.121.112.228/browse/NH-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Earl resolved NH-2636.
------------------------------
Resolution: Fixed
These are now exposed by means of an intermediate class that "unhides" the members.
> Expose ExpressionTreeVisitor Members
> ------------------------------------
>
> Key: NH-2636
> URL: http://216.121.112.228/browse/NH-2636
> Project: NHibernate
> Issue Type: Task
> Components: Linq Provider
> Affects Versions: 3.1.0
> Reporter: Patrick Earl
> Assignee: Patrick Earl
> Fix For: 3.2.0
>
>
> These members were hidden by the internalize, but are generally useful outside of NH. See this message.
> http://groups.google.com/group/nhusers/browse_thread/thread/25c6865b9a846963
--
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: Patrick E. (JIRA) <nh...@gm...> - 2011-04-08 17:50:52
|
Expose ExpressionTreeVisitor Members
------------------------------------
Key: NH-2636
URL: http://216.121.112.228/browse/NH-2636
Project: NHibernate
Issue Type: Task
Components: Linq Provider
Affects Versions: 3.1.0
Reporter: Patrick Earl
Assignee: Patrick Earl
Fix For: 3.2.0
These members were hidden by the internalize, but are generally useful outside of NH. See this message.
http://groups.google.com/group/nhusers/browse_thread/thread/25c6865b9a846963
--
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 16:26:06
|
[ http://216.121.112.228/browse/NH-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabio Maulo resolved NH-2635.
-----------------------------
Resolution: Fixed
Fix Version/s: 3.2.0
> Mapping by code
> ---------------
>
> Key: NH-2635
> URL: http://216.121.112.228/browse/NH-2635
> Project: NHibernate
> Issue Type: New Feature
> Components: Core
> Affects Versions: 3.1.0
> Reporter: Fabio Maulo
> Assignee: Fabio Maulo
> Fix For: 3.2.0
>
>
> Would be nice to have an embedded and well ConfORMed API to write mappings by code instead XML.
--
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 16:25:55
|
Mapping by code
---------------
Key: NH-2635
URL: http://216.121.112.228/browse/NH-2635
Project: NHibernate
Issue Type: New Feature
Components: Core
Affects Versions: 3.1.0
Reporter: Fabio Maulo
Assignee: Fabio Maulo
Would be nice to have an embedded and well ConfORMed API to write mappings by code instead XML.
--
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 15:46:06
|
[ http://216.121.112.228/browse/NH-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabio Maulo updated NH-2634:
----------------------------
Priority: Minor (was: Major)
> NHibernate generates wrong select-query
> ---------------------------------------
>
> Key: NH-2634
> URL: http://216.121.112.228/browse/NH-2634
> Project: NHibernate
> Issue Type: Bug
> Components: Core, QueryOver
> Affects Versions: 3.1.0
> Reporter: Kirill Medvedev
> Priority: Minor
> Attachments: NH_Bug.zip
>
>
> While transferring legacy project to NHibernate I found a bug... Nhibernate generates wrong SELECT query => GenericADOException occurs. See attachment. 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
|
|
From: Fabio M. (JIRA) <nh...@gm...> - 2011-04-08 15:46:02
|
[ http://216.121.112.228/browse/NH-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20863#action_20863 ]
Fabio Maulo commented on NH-2634:
---------------------------------
It seems yo have a wrong mapping in a collection.
The key of the collection point only to a part of the composite id of the related entity.
> NHibernate generates wrong select-query
> ---------------------------------------
>
> Key: NH-2634
> URL: http://216.121.112.228/browse/NH-2634
> Project: NHibernate
> Issue Type: Bug
> Components: Core, QueryOver
> Affects Versions: 3.1.0
> Reporter: Kirill Medvedev
> Priority: Major
> Attachments: NH_Bug.zip
>
>
> While transferring legacy project to NHibernate I found a bug... Nhibernate generates wrong SELECT query => GenericADOException occurs. See attachment. 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
|
|
From: Fabio M. (JIRA) <nh...@gm...> - 2011-04-08 14:20:14
|
[ http://216.121.112.228/browse/NH-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20862#action_20862 ]
Fabio Maulo commented on NH-2514:
---------------------------------
Thanks to attach the test in our JIRA avoiding us yo jump around the NET to see a test.
NET jumping is our preferred sport and we are payed to play it.
> CLONE -log4net DEBUG enabled and the query parameters Log parameters problem
> ----------------------------------------------------------------------------
>
> Key: NH-2514
> URL: http://216.121.112.228/browse/NH-2514
> Project: NHibernate
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.0.0.Alpha1
> Reporter: Joao Braganca
> Priority: Major
> Attachments: gorbach-NHibernateSandbox-d80415c.zip
>
>
> Hi,
> You have a problem in for example HQLQueryPlan class for example method void PerformList(QueryParameters queryParameters, ISessionImplementor session, IList results)
> when the log debug is on.
> if (log.IsDebugEnabled)
> {
> log.Debug("find: " + SourceQuery);
> queryParameters.LogParameters(session.Factory);
> }
> LogParameters method is throwing an exception in certain cases. The exception is the following:
> Could not execute query[SQL: SQL not available]
> NHibernate.Exceptions.GenericADOException: Could not execute query[SQL: SQL not available] ---> System.InvalidCastException: Unable to cast object of type 'System.Int32' to type 'System.String'.
> at NHibernate.Type.AbstractStringType.ToString(Object val) in C:\Program Files\NHibernatesvn\trunk\nhibernate\src\NHibernate\Type\AbstractStringType.cs:line 32
> at NHibernate.Type.NullableType.ToLoggableString(Object value, ISessionFactoryImplementor factory) in C:\Program Files\NHibernatesvn\trunk\nhibernate\src\NHibernate\Type\NullableType.cs:line 109
> at NHibernate.Impl.Printer.ToString(IDictionary`2 namedTypedValues) in C:\Program Files\NHibernatesvn\trunk\nhibernate\src\NHibernate\Impl\Printer.cs:line 71
> at NHibernate.Engine.QueryParameters.LogParameters(ISessionFactoryImplementor factory) in C:\Program Files\NHibernatesvn\trunk\nhibernate\src\NHibernate\Engine\QueryParameters.cs:line 213
> at NHibernate.Engine.Query.HQLQueryPlan.PerformList(QueryParameters queryParameters, ISessionImplementor session, IList results) in C:\Program Files\NHibernatesvn\trunk\nhibernate\src\NHibernate\Engine\Query\HQLQueryPlan.cs:line 254
> at NHibernate.Impl.SessionImpl.List(String query, QueryParameters queryParameters, IList results) in C:\Program Files\NHibernatesvn\trunk\nhibernate\src\NHibernate\Impl\SessionImpl.cs:line 629
>
> Do you want me to create the unit test? I did not want to since the unit test will simply pass since for it not to pass, you must change the App.config to use the following
> settings:
> <log4net debug="true">
> <root>
> <priority value="DEBUG" />
> <appender-ref ref="console" />
> </root>
--
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 14:15:49
|
[ http://216.121.112.228/browse/NH-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabio Maulo updated NH-2634:
----------------------------
Priority: Major (was: Critical)
> NHibernate generates wrong select-query
> ---------------------------------------
>
> Key: NH-2634
> URL: http://216.121.112.228/browse/NH-2634
> Project: NHibernate
> Issue Type: Bug
> Components: Core, QueryOver
> Affects Versions: 3.1.0
> Reporter: Kirill Medvedev
> Priority: Major
> Attachments: NH_Bug.zip
>
>
> While transferring legacy project to NHibernate I found a bug... Nhibernate generates wrong SELECT query => GenericADOException occurs. See attachment. 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
|
|
From: Fabio M. (JIRA) <nh...@gm...> - 2011-04-08 14:13:49
|
[ http://216.121.112.228/browse/NH-2633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fabio Maulo resolved NH-2633.
-----------------------------
Resolution: Fixed
Fix Version/s: 3.2.0
> MapperByCode don't Register Component
> -------------------------------------
>
> Key: NH-2633
> URL: http://216.121.112.228/browse/NH-2633
> Project: NHibernate
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.2.0
> Reporter: li yongjing
> Fix For: 3.2.0
>
>
> //a class with components
> public class Person1
> {
> public int Id { get; set; }
> public string Test { get; set; }
> public Name Name { get; set; }
> public Address Address { get; set; }
> }
> public class Name
> {
> public string First { get; set; }
> public string Last { get; set; }
> }
> public class Address
> {
> public string Street { get; set; }
> public int CivicNumber { get; set; }
> }
> [Test]
> public void ComponentMappingJustOnceDemo()
> {
> var mapper = new ModelMapper();
> mapper.Component<Name>(comp =>
> {
> comp.Property(name => name.First);
> comp.Property(name => name.Last);
> });
> mapper.Component<Address>(comp =>
> {
> comp.Property(address => address.CivicNumber);
> comp.Property(address => address.Street);
> });
> mapper.Class<Person1>(cm =>
> {
> cm.Id(person => person.Id, map => map.Generator(Generators.HighLow));
> cm.Property(person => person.Test);
> cm.Component(person => person.Name, comp => { });
> cm.Component(person => person.Address, comp => { });
> });
> var hbmMapping = mapper.CompileMappingForAllExplicitAddedEntities();
> Console.Write(hbmMapping.AsString());
> }
--
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: Alexey G. (JIRA) <nh...@gm...> - 2011-04-08 13:02:49
|
[ http://216.121.112.228/browse/NH-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Gorbach updated NH-2514:
-------------------------------
Attachment: gorbach-NHibernateSandbox-d80415c.zip
The project with falling test is available here git://github.com/gorbach/NHibernateSandbox.git (branch NH-2514)
> CLONE -log4net DEBUG enabled and the query parameters Log parameters problem
> ----------------------------------------------------------------------------
>
> Key: NH-2514
> URL: http://216.121.112.228/browse/NH-2514
> Project: NHibernate
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.0.0.Alpha1
> Reporter: Joao Braganca
> Priority: Major
> Attachments: gorbach-NHibernateSandbox-d80415c.zip
>
>
> Hi,
> You have a problem in for example HQLQueryPlan class for example method void PerformList(QueryParameters queryParameters, ISessionImplementor session, IList results)
> when the log debug is on.
> if (log.IsDebugEnabled)
> {
> log.Debug("find: " + SourceQuery);
> queryParameters.LogParameters(session.Factory);
> }
> LogParameters method is throwing an exception in certain cases. The exception is the following:
> Could not execute query[SQL: SQL not available]
> NHibernate.Exceptions.GenericADOException: Could not execute query[SQL: SQL not available] ---> System.InvalidCastException: Unable to cast object of type 'System.Int32' to type 'System.String'.
> at NHibernate.Type.AbstractStringType.ToString(Object val) in C:\Program Files\NHibernatesvn\trunk\nhibernate\src\NHibernate\Type\AbstractStringType.cs:line 32
> at NHibernate.Type.NullableType.ToLoggableString(Object value, ISessionFactoryImplementor factory) in C:\Program Files\NHibernatesvn\trunk\nhibernate\src\NHibernate\Type\NullableType.cs:line 109
> at NHibernate.Impl.Printer.ToString(IDictionary`2 namedTypedValues) in C:\Program Files\NHibernatesvn\trunk\nhibernate\src\NHibernate\Impl\Printer.cs:line 71
> at NHibernate.Engine.QueryParameters.LogParameters(ISessionFactoryImplementor factory) in C:\Program Files\NHibernatesvn\trunk\nhibernate\src\NHibernate\Engine\QueryParameters.cs:line 213
> at NHibernate.Engine.Query.HQLQueryPlan.PerformList(QueryParameters queryParameters, ISessionImplementor session, IList results) in C:\Program Files\NHibernatesvn\trunk\nhibernate\src\NHibernate\Engine\Query\HQLQueryPlan.cs:line 254
> at NHibernate.Impl.SessionImpl.List(String query, QueryParameters queryParameters, IList results) in C:\Program Files\NHibernatesvn\trunk\nhibernate\src\NHibernate\Impl\SessionImpl.cs:line 629
>
> Do you want me to create the unit test? I did not want to since the unit test will simply pass since for it not to pass, you must change the App.config to use the following
> settings:
> <log4net debug="true">
> <root>
> <priority value="DEBUG" />
> <appender-ref ref="console" />
> </root>
--
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 10:41:59
|
[ http://216.121.112.228/browse/NH-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20860#action_20860 ]
Ricardo Peres commented on NH-2632:
-----------------------------------
I see. So, a lazy property can only exist (or, at least, be lazy) inside a lazy class.
The documentation doesn't say this explicitly.
> 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: Anupam M. (JIRA) <nh...@gm...> - 2011-04-08 08:47:55
|
[ http://216.121.112.228/browse/NH-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20859#action_20859 ]
Anupam Mishra commented on NH-2631:
-----------------------------------
I have replicated the same example.But still it is not working with Oracle 10 g .
It is giving following error
Exception:Could not create the driver from NHibernate.Driver.OracleDataClientDriver.
Inner Message:Unable to find the requested .Net Framework Data Provider. It may not be installed.
<session-factory>
<!--<property name="hibernate.connection.release_mode">on_close</property>-->
<property name="connection.provider">NHibernate.Connection.DriverConnectionProvider</property>
<property name="dialect">NHibernate.Dialect.Oracle10gDialect </property>
</session-factory>
Can u please help
> 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: Kirill M. (JIRA) <nh...@gm...> - 2011-04-08 08:44:58
|
[ http://216.121.112.228/browse/NH-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20858#action_20858 ]
Kirill Medvedev commented on NH-2634:
-------------------------------------
I've checked another ways to retrieve data. Criteria API and HQL behave the same way, as QueryOver, and cause an exception.
IList<Item> items = session.QueryOver<Item>().Skip(1).Take(20).List();
IList<Item> items = session.CreateCriteria<Item>().SetFirstResult(1).SetMaxResults(20).List<Item>();
IList<Item> items = session.CreateQuery("from Item").SetFirstResult(1).SetMaxResults(20).List<Item>();
> NHibernate generates wrong select-query
> ---------------------------------------
>
> Key: NH-2634
> URL: http://216.121.112.228/browse/NH-2634
> Project: NHibernate
> Issue Type: Bug
> Components: Core, QueryOver
> Affects Versions: 3.1.0
> Reporter: Kirill Medvedev
> Priority: Critical
> Attachments: NH_Bug.zip
>
>
> While transferring legacy project to NHibernate I found a bug... Nhibernate generates wrong SELECT query => GenericADOException occurs. See attachment. 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
|
|
From: Kirill M. (JIRA) <nh...@gm...> - 2011-04-08 07:57:50
|
NHibernate generates wrong select-query
---------------------------------------
Key: NH-2634
URL: http://216.121.112.228/browse/NH-2634
Project: NHibernate
Issue Type: Bug
Components: Core, QueryOver
Affects Versions: 3.1.0
Reporter: Kirill Medvedev
Priority: Critical
Attachments: NH_Bug.zip
While transferring legacy project to NHibernate I found a bug... Nhibernate generates wrong SELECT query => GenericADOException occurs. See attachment. 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
|
|
From: cremor (JIRA) <nh...@gm...> - 2011-04-08 06:49:58
|
[ http://216.121.112.228/browse/NH-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20857#action_20857 ]
cremor commented on NH-2623:
----------------------------
As far as I know it's not possible to create deferrable constraints with hbm2ddl, so how would I create a test for it?
The case shown in the unit test should already demonstrate my other use case: Network connection failures. My ISQLExceptionConverter knows all that error numbers that indicate a connection problem. I get the same error numbers when a connection problem occurs during Transaction.Begin/Commit/Rollback, so it would make sense to handle it the same way.
> 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: li y. (JIRA) <nh...@gm...> - 2011-04-08 06:09:54
|
[ http://216.121.112.228/browse/NH-2633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20856#action_20856 ]
li yongjing commented on NH-2633:
---------------------------------
Hi,Can you add get private property method in ForClass<> class?
> MapperByCode don't Register Component
> -------------------------------------
>
> Key: NH-2633
> URL: http://216.121.112.228/browse/NH-2633
> Project: NHibernate
> Issue Type: Bug
> Components: Core
> Affects Versions: 3.2.0
> Reporter: li yongjing
>
> //a class with components
> public class Person1
> {
> public int Id { get; set; }
> public string Test { get; set; }
> public Name Name { get; set; }
> public Address Address { get; set; }
> }
> public class Name
> {
> public string First { get; set; }
> public string Last { get; set; }
> }
> public class Address
> {
> public string Street { get; set; }
> public int CivicNumber { get; set; }
> }
> [Test]
> public void ComponentMappingJustOnceDemo()
> {
> var mapper = new ModelMapper();
> mapper.Component<Name>(comp =>
> {
> comp.Property(name => name.First);
> comp.Property(name => name.Last);
> });
> mapper.Component<Address>(comp =>
> {
> comp.Property(address => address.CivicNumber);
> comp.Property(address => address.Street);
> });
> mapper.Class<Person1>(cm =>
> {
> cm.Id(person => person.Id, map => map.Generator(Generators.HighLow));
> cm.Property(person => person.Test);
> cm.Component(person => person.Name, comp => { });
> cm.Component(person => person.Address, comp => { });
> });
> var hbmMapping = mapper.CompileMappingForAllExplicitAddedEntities();
> Console.Write(hbmMapping.AsString());
> }
--
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: li y. (JIRA) <nh...@gm...> - 2011-04-08 06:04:47
|
MapperByCode don't Register Component
-------------------------------------
Key: NH-2633
URL: http://216.121.112.228/browse/NH-2633
Project: NHibernate
Issue Type: Bug
Components: Core
Affects Versions: 3.2.0
Reporter: li yongjing
//a class with components
public class Person1
{
public int Id { get; set; }
public string Test { get; set; }
public Name Name { get; set; }
public Address Address { get; set; }
}
public class Name
{
public string First { get; set; }
public string Last { get; set; }
}
public class Address
{
public string Street { get; set; }
public int CivicNumber { get; set; }
}
[Test]
public void ComponentMappingJustOnceDemo()
{
var mapper = new ModelMapper();
mapper.Component<Name>(comp =>
{
comp.Property(name => name.First);
comp.Property(name => name.Last);
});
mapper.Component<Address>(comp =>
{
comp.Property(address => address.CivicNumber);
comp.Property(address => address.Street);
});
mapper.Class<Person1>(cm =>
{
cm.Id(person => person.Id, map => map.Generator(Generators.HighLow));
cm.Property(person => person.Test);
cm.Component(person => person.Name, comp => { });
cm.Component(person => person.Address, comp => { });
});
var hbmMapping = mapper.CompileMappingForAllExplicitAddedEntities();
Console.Write(hbmMapping.AsString());
}
--
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:56:55
|
[ http://216.121.112.228/browse/NH-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20855#action_20855 ]
Fabio Maulo commented on NH-2632:
---------------------------------
No. It is by design.
You can activate the logger and see the WARNING.
> 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:54:58
|
[ http://216.121.112.228/browse/NH-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20854#action_20854 ]
Fabio Maulo commented on NH-2623:
---------------------------------
Then try to provide a test for the case you are trying to solve.
btw the case is completely different and we should throw a TransactionException with, as most, the inner exception converted by NH (as the exception on flush).
> 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
|
35 messages has been excluded from this view by a project administrator.
