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: Steven T. (JIRA) <nh...@gm...> - 2011-04-12 14:28:03
|
SoftLimitMRUCache continues growing despite any attempts to clear ----------------------------------------------------------------- Key: NHCH-37 URL: http://216.121.112.228/browse/NHCH-37 Project: NHibernate.Caches Issue Type: Bug Components: Other Affects Versions: 2.0.0GA Reporter: Steven Thacher Priority: Major We have discovered a small memory leak in our application, and we've been able to track it down to NHibernate using JetBrains dotTrace. It appears that as we make queries, the SessionFactoryImpl class continues to grow. The object within SessionFactoryImpl that seems to be holding on to the most memory is the SoftLimitMRUCache. This issue seems similar to NH-604 which was apparently resolved in 1.0.3, but I continue to see the problem in version 2.0. I've tried various approaches to clearing this cache, but nothing has worked for me thus far. I've tried the following: Attempt 1: Write a clear cache function that clears everything in the session factory: _sessionFactory.EvictQueries(); foreach (Type type in _sessionFactory.GetAllClassMetadata().Keys) _sessionFactory.Evict(type); foreach (string role in _sessionFactory.GetAllCollectionMetadata().Keys) _sessionFactory.EvictCollection(role); Attempt 2: Set the FlushType of our Session, then flush and clear the session before each query. Attempt 3: Change configuration properties in the config XML file and turn off the 2nd level cache. As I said, none of these attempts were successful. -- 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-12 14:11:03
|
Lazy Properties Causing An Exception With Castle Bytecode Provider ------------------------------------------------------------------ Key: NH-2646 URL: http://216.121.112.228/browse/NH-2646 Project: NHibernate Issue Type: Bug Components: ByteCode providers Affects Versions: 3.2.0Alpha1 Reporter: Ricardo Peres Attachments: UnitTests1.cs If we are using the "old" Castle bytecode provider, lazy properties do not work, even inside lazy classes: when an entity is loaded, it crashes with a NotImplementedException ("Specified method is not supported."). Attached is a sample. -- 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-12 14:00:13
|
[ http://216.121.112.228/browse/NH-2639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20896#action_20896 ] Ricardo Peres commented on NH-2639: ----------------------------------- It works fine with the old Castle bytecode provider. > Collection Is Null In Lazy Class > -------------------------------- > > Key: NH-2639 > URL: http://216.121.112.228/browse/NH-2639 > Project: NHibernate > Issue Type: Bug > Components: Core > Affects Versions: 3.2.0Alpha1 > Reporter: Ricardo Peres > Attachments: Test2.cs > > > A declared is declared as lazy and has a set property also lazy. When loading an entity, the set property is null. Mapping is made with the trunk version of by code mapping. -- 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-12 13:47:13
|
[ http://216.121.112.228/browse/NH-2638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20895#action_20895 ] Ricardo Peres commented on NH-2638: ----------------------------------- Using Castle bytecode provider it works fine, except that lazy properties crash even in lazy entities. I would say that the problem is with the new bytecode provider. > 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.0Alpha1 > 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: Paul S. (JIRA) <nh...@gm...> - 2011-04-12 13:43:14
|
[ http://216.121.112.228/browse/NH-2645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20894#action_20894 ] Paul Speranza commented on NH-2645: ----------------------------------- I just upgraded to NH 3.1 and now the exception is changed to Expression type 'NhDistinctExpression' is not supported by this SelectClauseVisitor. > NHibernate LINQ 3.0 connecting to Oracle ODP.Net Expression type 10005 is not supported by this SelectClauseVisitor. > -------------------------------------------------------------------------------------------------------------------- > > Key: NH-2645 > URL: http://216.121.112.228/browse/NH-2645 > Project: NHibernate > Issue Type: Bug > Components: Linq Provider > Affects Versions: 3.0.0.GA > Reporter: Paul Speranza > Priority: Critical > > I have the following LINQ query that is mapped to a view > QueryResult<List<PersonDemographic>> members = new QueryResult<List<PersonDemographic>>(); > var query = (from ms in this.Session.Query<MemberSummary>() > where ms.NameSearch.StartsWith(firstName.ToUpper()) > && ms.NameSearch2.StartsWith(lastName.ToUpper()) > select new PersonDemographic > { > FirstName = ms.FirstName.ToProperCase(), > LastName = ms.LastName.ToProperCase(), > PersonId = ms.Id, > Address = new Address > { > Line1 = ms.AddressLine1.ToProperCase(), > Line2 = ms.AddressLine2.ToProperCase(), > City = ms.City.ToProperCase(), > State = ms.State, > Zipcode = ms.Zipcode, > }, > PhoneNumber = new PhoneNumber > { > Number = string.IsNullOrWhiteSpace(ms.PhoneNumber) ? null : Regex.Replace(ms.PhoneNumber, @"(\d{3})(\d{3})(\d{4})", "$1-$2-$3") > } > }); > if (this.Session.Transaction.IsActive) > { > members.Data = query.Distinct().Take(15).ToList(); > } > else > { > using (var transaction = this.Session.BeginTransaction()) > { > members.Data = query.Distinct().Take(15).ToList(); > transaction.Commit(); > } > } > > The code is running under the transaction section. If I use it without a Distinct I have no problem. Adding the Distinct gives me an exception > {"Expression type 10005 is not supported by this SelectClauseVisitor."} > I can't find anything definitive. Can anyone help? > Thanks, Paul -- 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: RAB (JIRA) <nh...@gm...> - 2011-04-12 13:06:06
|
Dead Lock: delete with optimize ------------------------------- Key: NHSR-37 URL: http://216.121.112.228/browse/NHSR-37 Project: NHibernate.Search Issue Type: Bug Components: Core Affects Versions: 2.1.0 Reporter: RAB Assignee: Paul Hatcher Priority: Critical With this option, the index is optimized for each transaction. x.SetProperty("hibernate.search.default.optimizer.transaction_limit.max", "0"); Delete workflow: • Delete-Work is performed. • Delete-Work opens an index reader and lock the provider. • Delete-Work is finished. • CleanUp is performed. • All index readers are closed. • CleanUp starts the optimizer. • Optimizer opens an index writer and lock the provider. • Back on the CleanUp method. • All index writer are closed. • For each locked provider Monitor.Exit (provider) is called. • Finish. Monitor.Enter(provider) was executed twice but Monitor.Exit(provider) only once. Delete the next time we have a dead lock. Line 204 - 224 LockProvider in Backend\Workspace Now: private void LockProvider(IDirectoryProvider provider) { // Make sure to use a semaphore object syncLock = searchFactoryImplementor.GetLockableDirectoryProviders()[provider]; Monitor.Enter(syncLock); try { if (!lockedProviders.Contains(provider)) { lockedProviders.Add(provider); dpStatistics.Add(provider, new DPStatistics()); } } catch (Exception) { // NB This is correct here, we release the lock *only* if we have an error Monitor.Exit(syncLock); throw; } } Solving: private void LockProvider(IDirectoryProvider provider) { //Provider only lock once if (!lockedProviders.Contains(provider)) { // Make sure to use a semaphore object syncLock = searchFactoryImplementor.GetLockableDirectoryProviders()[provider]; Monitor.Enter(syncLock); try { lockedProviders.Add(provider); dpStatistics.Add(provider, new DPStatistics()); } catch (Exception) { // NB This is correct here, we release the lock *only* if we have an error Monitor.Exit(syncLock); throw; } } } -- 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: Paul S. (JIRA) <nh...@gm...> - 2011-04-12 12:50:06
|
NHibernate LINQ 3.0 connecting to Oracle ODP.Net Expression type 10005 is not supported by this SelectClauseVisitor. -------------------------------------------------------------------------------------------------------------------- Key: NH-2645 URL: http://216.121.112.228/browse/NH-2645 Project: NHibernate Issue Type: Bug Components: Linq Provider Affects Versions: 3.0.0.GA Reporter: Paul Speranza Priority: Critical I have the following LINQ query that is mapped to a view QueryResult<List<PersonDemographic>> members = new QueryResult<List<PersonDemographic>>(); var query = (from ms in this.Session.Query<MemberSummary>() where ms.NameSearch.StartsWith(firstName.ToUpper()) && ms.NameSearch2.StartsWith(lastName.ToUpper()) select new PersonDemographic { FirstName = ms.FirstName.ToProperCase(), LastName = ms.LastName.ToProperCase(), PersonId = ms.Id, Address = new Address { Line1 = ms.AddressLine1.ToProperCase(), Line2 = ms.AddressLine2.ToProperCase(), City = ms.City.ToProperCase(), State = ms.State, Zipcode = ms.Zipcode, }, PhoneNumber = new PhoneNumber { Number = string.IsNullOrWhiteSpace(ms.PhoneNumber) ? null : Regex.Replace(ms.PhoneNumber, @"(\d{3})(\d{3})(\d{4})", "$1-$2-$3") } }); if (this.Session.Transaction.IsActive) { members.Data = query.Distinct().Take(15).ToList(); } else { using (var transaction = this.Session.BeginTransaction()) { members.Data = query.Distinct().Take(15).ToList(); transaction.Commit(); } } The code is running under the transaction section. If I use it without a Distinct I have no problem. Adding the Distinct gives me an exception {"Expression type 10005 is not supported by this SelectClauseVisitor."} I can't find anything definitive. Can anyone help? Thanks, Paul -- 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-12 11:48:06
|
[ http://216.121.112.228/browse/NH-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabio Maulo updated NH-2644: ---------------------------- Issue Type: Improvement (was: New Feature) > schemaaction is not supported in joinedsubclass > ----------------------------------------------- > > Key: NH-2644 > URL: http://216.121.112.228/browse/NH-2644 > Project: NHibernate > Issue Type: Improvement > Components: Core > Affects Versions: 3.2.0Alpha1 > Reporter: Giovanni Bismondo > Priority: Minor > > schemaaction is not supported in joinedsubclass -- 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: Giovanni B. (JIRA) <nh...@gm...> - 2011-04-12 11:02:04
|
schemaaction is not supported in joinedsubclass ----------------------------------------------- Key: NH-2644 URL: http://216.121.112.228/browse/NH-2644 Project: NHibernate Issue Type: New Feature Components: Core Affects Versions: 3.2.0Alpha1 Reporter: Giovanni Bismondo Priority: Minor schemaaction is not supported in joinedsubclass -- 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: Julian M. (JIRA) <nh...@gm...> - 2011-04-12 09:40:02
|
[ http://216.121.112.228/browse/NH-2643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Maughan resolved NH-2643. -------------------------------- Resolution: Fixed Fix Version/s: 3.2.0Beta1 Thanks. I also found a reference to 'use_outer_join' in the documentation. Removed in r5673. > MSSQL configuration template is still using "use_outer_join" > ------------------------------------------------------------ > > Key: NH-2643 > URL: http://216.121.112.228/browse/NH-2643 > Project: NHibernate > Issue Type: Bug > Components: Core > Affects Versions: 3.2.0Alpha1 > Reporter: cremor > Priority: Minor > Fix For: 3.2.0Beta1 > > > The example file MSSQL.cfg.xml in the binary download package of 3.2.0.Alpha1 still has the (now removed) "use_outer_join" setting in it. -- 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: Julian M. (JIRA) <nh...@gm...> - 2011-04-12 09:20:04
|
[ http://216.121.112.228/browse/NH-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Maughan updated NH-2587: ------------------------------- Summary: .Cacheable().Fetch() throws 'Exception occurred getter of xxx' (was: .Cacheable().Fetch() throws 'Exception occurred getter of xxx' Options ) > .Cacheable().Fetch() throws 'Exception occurred getter of xxx' > -------------------------------------------------------------- > > Key: NH-2587 > URL: http://216.121.112.228/browse/NH-2587 > Project: NHibernate > Issue Type: Bug > Components: Linq Provider > Affects Versions: 3.1.0 > Reporter: Eduardo Segura > Assignee: Patrick Earl > Priority: Major > Attachments: CacheableFetchTest.zip > > > This query: > IList<ParentObject> pos = session.Query<ParentObject>().Cacheable().Fetch(po => po.ChildObjects).ToList(); > throws this exception: > NHibernate.PropertyAccessException: Exception occurred getter of CacheableFetchTest.Entity`1[[System.Guid, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].Id ---> System.Reflection.TargetException: Object does not match target type.. > For a detailed discussion, including full exception stacks, please see: > http://groups.google.com/group/nhusers/browse_thread/thread/dfdbe987d8450b0a/cb812c856e07ee0a -- 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-12 05:48:05
|
MSSQL configuration template is still using "use_outer_join" ------------------------------------------------------------ Key: NH-2643 URL: http://216.121.112.228/browse/NH-2643 Project: NHibernate Issue Type: Bug Components: Core Affects Versions: 3.2.0Alpha1 Reporter: cremor Priority: Minor The example file MSSQL.cfg.xml in the binary download package of 3.2.0.Alpha1 still has the (now removed) "use_outer_join" setting in it. -- 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-12 03:33:38
|
[ http://216.121.112.228/browse/NH-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20892#action_20892 ] Patrick Earl commented on NH-2587: ---------------------------------- The rabbit hole goes deep on this one. It's fundamentally related to complications between result transformers and caching. This is apparently fixed in Hibernate 4.0, but it looks like there would be a substantial amount of work to figure out exactly what and how to port. Because fetching can create duplicate rows, Linq adds a distinct result transformer. I'll think more on this. > .Cacheable().Fetch() throws 'Exception occurred getter of xxx' Options > ----------------------------------------------------------------------- > > Key: NH-2587 > URL: http://216.121.112.228/browse/NH-2587 > Project: NHibernate > Issue Type: Bug > Components: Linq Provider > Affects Versions: 3.1.0 > Reporter: Eduardo Segura > Assignee: Patrick Earl > Priority: Major > Attachments: CacheableFetchTest.zip > > > This query: > IList<ParentObject> pos = session.Query<ParentObject>().Cacheable().Fetch(po => po.ChildObjects).ToList(); > throws this exception: > NHibernate.PropertyAccessException: Exception occurred getter of CacheableFetchTest.Entity`1[[System.Guid, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].Id ---> System.Reflection.TargetException: Object does not match target type.. > For a detailed discussion, including full exception stacks, please see: > http://groups.google.com/group/nhusers/browse_thread/thread/dfdbe987d8450b0a/cb812c856e07ee0a -- 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: Dan J. (JIRA) <nh...@gm...> - 2011-04-11 22:46:13
|
[ http://216.121.112.228/browse/NH-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20891#action_20891 ] Dan Jasek commented on NH-2611: ------------------------------- I need to hook into the Execute operation on the Provider. ActiveRecord currently opens a session when the Linq query is defined, but it never releases it. This is because it can't tell when the query will actually be called and the session will be used. The easiest solution I found was to get the session when the Linq query was actually executed, and release it immediately afterward. This way, the query can be created detached, moved between SessionScopes, etc with no problem. It will simply use the session available when the query is actually executed. To do that, I need to tweak the NH provider a bit. I could create my own Queryable/Provider, but that causes issues with extension methods and other references (Futures) and it looks like I would need to take a dependency on Remotion in ActiveRecord. What do you mean by, "Not enough. We are casting it for Future..." I saw the way Linq queries can be turned into Futures, but I did not see an issue with what I am doing. This is why I set ExecuteFuture to virtual as well. If you are interested The thread about this on the AR group is here: http://groups.google.com/group/castle-project-users/browse_frm/thread/be987e3084dad707 And the custom provider I wrote based off of these edits can be found here: https://github.com/oillio/Castle.ActiveRecord/blob/master/src/Castle.ActiveRecord/Framework/ARQueryProvider.cs > 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: Patrick E. (JIRA) <nh...@gm...> - 2011-04-11 20:06:35
|
[ http://216.121.112.228/browse/NH-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20890#action_20890 ] Patrick Earl commented on NH-2587: ---------------------------------- Unfortunately(?) I already have a failing test case based on your earlier code. At the moment it's not clear to me what's going on. The result transformer hint on the mailing list is interesting though. I'm naturally happy to have any hints or insights anyone can provide. I can't promise I'll be able to fix this quickly, but I can say that I'll be looking at it as time permits. > .Cacheable().Fetch() throws 'Exception occurred getter of xxx' Options > ----------------------------------------------------------------------- > > Key: NH-2587 > URL: http://216.121.112.228/browse/NH-2587 > Project: NHibernate > Issue Type: Bug > Components: Linq Provider > Affects Versions: 3.1.0 > Reporter: Eduardo Segura > Assignee: Patrick Earl > Priority: Major > Attachments: CacheableFetchTest.zip > > > This query: > IList<ParentObject> pos = session.Query<ParentObject>().Cacheable().Fetch(po => po.ChildObjects).ToList(); > throws this exception: > NHibernate.PropertyAccessException: Exception occurred getter of CacheableFetchTest.Entity`1[[System.Guid, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].Id ---> System.Reflection.TargetException: Object does not match target type.. > For a detailed discussion, including full exception stacks, please see: > http://groups.google.com/group/nhusers/browse_thread/thread/dfdbe987d8450b0a/cb812c856e07ee0a -- 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: Eduardo S. (JIRA) <nh...@gm...> - 2011-04-11 19:43:32
|
[ http://216.121.112.228/browse/NH-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20889#action_20889 ] Eduardo Segura commented on NH-2587: ------------------------------------ And on my birthday, no less! :). By the way, Patrick, I can code a 'proper' NHibernate test if that would help (and given that this issue has now 21 votes.) Let me know. I'll be happy to help. And thanks for looking into this. > .Cacheable().Fetch() throws 'Exception occurred getter of xxx' Options > ----------------------------------------------------------------------- > > Key: NH-2587 > URL: http://216.121.112.228/browse/NH-2587 > Project: NHibernate > Issue Type: Bug > Components: Linq Provider > Affects Versions: 3.1.0 > Reporter: Eduardo Segura > Assignee: Patrick Earl > Priority: Major > Attachments: CacheableFetchTest.zip > > > This query: > IList<ParentObject> pos = session.Query<ParentObject>().Cacheable().Fetch(po => po.ChildObjects).ToList(); > throws this exception: > NHibernate.PropertyAccessException: Exception occurred getter of CacheableFetchTest.Entity`1[[System.Guid, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].Id ---> System.Reflection.TargetException: Object does not match target type.. > For a detailed discussion, including full exception stacks, please see: > http://groups.google.com/group/nhusers/browse_thread/thread/dfdbe987d8450b0a/cb812c856e07ee0a -- 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: Luis F. (JIRA) <nh...@gm...> - 2011-04-11 19:24:32
|
[ http://216.121.112.228/browse/NH-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20888#action_20888 ] Luis Fernando commented on NH-2587: ----------------------------------- Great news, it's good to know that the developers listen to the community. Thank you guys. > .Cacheable().Fetch() throws 'Exception occurred getter of xxx' Options > ----------------------------------------------------------------------- > > Key: NH-2587 > URL: http://216.121.112.228/browse/NH-2587 > Project: NHibernate > Issue Type: Bug > Components: Linq Provider > Affects Versions: 3.1.0 > Reporter: Eduardo Segura > Assignee: Patrick Earl > Priority: Major > Attachments: CacheableFetchTest.zip > > > This query: > IList<ParentObject> pos = session.Query<ParentObject>().Cacheable().Fetch(po => po.ChildObjects).ToList(); > throws this exception: > NHibernate.PropertyAccessException: Exception occurred getter of CacheableFetchTest.Entity`1[[System.Guid, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].Id ---> System.Reflection.TargetException: Object does not match target type.. > For a detailed discussion, including full exception stacks, please see: > http://groups.google.com/group/nhusers/browse_thread/thread/dfdbe987d8450b0a/cb812c856e07ee0a -- 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-11 18:33:38
|
[ http://216.121.112.228/browse/NH-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Earl reassigned NH-2587: -------------------------------- Assignee: Patrick Earl > .Cacheable().Fetch() throws 'Exception occurred getter of xxx' Options > ----------------------------------------------------------------------- > > Key: NH-2587 > URL: http://216.121.112.228/browse/NH-2587 > Project: NHibernate > Issue Type: Bug > Components: Linq Provider > Affects Versions: 3.1.0 > Reporter: Eduardo Segura > Assignee: Patrick Earl > Priority: Major > Attachments: CacheableFetchTest.zip > > > This query: > IList<ParentObject> pos = session.Query<ParentObject>().Cacheable().Fetch(po => po.ChildObjects).ToList(); > throws this exception: > NHibernate.PropertyAccessException: Exception occurred getter of CacheableFetchTest.Entity`1[[System.Guid, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].Id ---> System.Reflection.TargetException: Object does not match target type.. > For a detailed discussion, including full exception stacks, please see: > http://groups.google.com/group/nhusers/browse_thread/thread/dfdbe987d8450b0a/cb812c856e07ee0a -- 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-11 18:33:05
|
[ http://216.121.112.228/browse/NH-2587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Earl updated NH-2587: ----------------------------- Priority: Major (was: Minor) > .Cacheable().Fetch() throws 'Exception occurred getter of xxx' Options > ----------------------------------------------------------------------- > > Key: NH-2587 > URL: http://216.121.112.228/browse/NH-2587 > Project: NHibernate > Issue Type: Bug > Components: Linq Provider > Affects Versions: 3.1.0 > Reporter: Eduardo Segura > Priority: Major > Attachments: CacheableFetchTest.zip > > > This query: > IList<ParentObject> pos = session.Query<ParentObject>().Cacheable().Fetch(po => po.ChildObjects).ToList(); > throws this exception: > NHibernate.PropertyAccessException: Exception occurred getter of CacheableFetchTest.Entity`1[[System.Guid, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].Id ---> System.Reflection.TargetException: Object does not match target type.. > For a detailed discussion, including full exception stacks, please see: > http://groups.google.com/group/nhusers/browse_thread/thread/dfdbe987d8450b0a/cb812c856e07ee0a -- 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-11 18:04:00
|
[ http://216.121.112.228/browse/NH-2533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Earl resolved NH-2533. ------------------------------ Resolution: Fixed Fix Version/s: 3.2.0Beta1 There was divergent discussion on the mailing list about skip/take. The "SELECT" clause is not mandatory in hql, so I avoided the syntactically long route of "SELECT SKIP s TAKE t c FROM Class c". Since the majority of SQL dialects use the limit clause at the end, I decided to place SKIP and TAKE there instead of as a less conventional prefix. This incidentally made the implementation easier since the SELECT/FROM clause is still the root of the query, and the rest of the information is optionally attached to the query. > Support paging in HQL > --------------------- > > Key: NH-2533 > URL: http://216.121.112.228/browse/NH-2533 > Project: NHibernate > Issue Type: New Feature > Components: Core > Affects Versions: 3.0.0.GA > Reporter: Patrick Earl > Assignee: Patrick Earl > Priority: Minor > Fix For: 3.2.0Beta1 > > > As per the discussion on the mailing list, this would add [SKIP x] [TAKE y] after the order by clause. -- 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-11 18:00:00
|
[ http://216.121.112.228/browse/NH-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Earl resolved NH-2640. ------------------------------ Resolution: Fixed Fix Version/s: 3.2.0Beta1 > HQL Having clause is ignored without preceeding group by > -------------------------------------------------------- > > Key: NH-2640 > URL: http://216.121.112.228/browse/NH-2640 > Project: NHibernate > Issue Type: Bug > Components: Core > Affects Versions: 3.2.0Alpha1 > Reporter: Patrick Earl > Assignee: Patrick Earl > 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 |
From: Patrick E. (JIRA) <nh...@gm...> - 2011-04-11 17:58:01
|
[ http://216.121.112.228/browse/NH-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Earl resolved NH-2641. ------------------------------ Resolution: Fixed Fix Version/s: 3.2.0Beta1 > HQL does not throw exception on unexpected trailing tokens > ---------------------------------------------------------- > > Key: NH-2641 > URL: http://216.121.112.228/browse/NH-2641 > Project: NHibernate > Issue Type: Bug > Components: Core > Affects Versions: 3.2.0Alpha1 > Reporter: Patrick Earl > Assignee: Patrick Earl > 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 |
From: Roger (JIRA) <nh...@gm...> - 2011-04-11 17:31:05
|
BatcherDataReaderWrapper.GetValue has a typo -------------------------------------------- Key: NH-2642 URL: http://216.121.112.228/browse/NH-2642 Project: NHibernate Issue Type: Bug Components: Core Affects Versions: 3.2.0Alpha1 Reporter: Roger Attachments: batcherdatareaderwrapper.patch The datareader decorator has a typo here class BatcherDataReaderWrapper object GetValue(int) return reader.GETDECIMAL() test + fix 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: Patrick E. (JIRA) <nh...@gm...> - 2011-04-11 17:05:02
|
HQL does not throw exception on unexpected trailing tokens ---------------------------------------------------------- Key: NH-2641 URL: http://216.121.112.228/browse/NH-2641 Project: NHibernate Issue Type: Bug Components: Core Affects Versions: 3.2.0Alpha1 Reporter: Patrick Earl Assignee: Patrick Earl -- 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-11 17:03:06
|
HQL Having clause is ignored without preceeding group by -------------------------------------------------------- Key: NH-2640 URL: http://216.121.112.228/browse/NH-2640 Project: NHibernate Issue Type: Bug Components: Core Affects Versions: 3.2.0Alpha1 Reporter: Patrick Earl Assignee: Patrick Earl -- 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 |