July 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-94) Deprecate ContextHelper

by Emmanuel Bernard (JIRA)

Deprecate ContextHelper ----------------------- Key: HSEARCH-94 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-94 Project: Hibernate Search Issue Type: Task Components: documentation Reporter: Emmanuel Bernard Priority: Trivial Fix For: 3.0.0.beta4 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-95) Deprecate ContextHelper

by Emmanuel Bernard (JIRA)

Deprecate ContextHelper ----------------------- Key: HSEARCH-95 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-95 Project: Hibernate Search Issue Type: Deprecation Components: engine Affects Versions: 3.0.0.beta3 Reporter: Emmanuel Bernard Priority: Minor Fix For: 3.0.0.beta4 use session.getSearchFactory() instead -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HV-34) AbstractLuhnValidator and EANValidator perform unnecessary calculations in some circumstances

by WATANABE Takashi (JIRA)

AbstractLuhnValidator and EANValidator perform unnecessary calculations in some circumstances --------------------------------------------------------------------------------------------- Key: HV-34 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-34 Project: Hibernate Validator Issue Type: Bug Components: validators Reporter: WATANABE Takashi Priority: Trivial Attachments: 20070710_2205.patch.txt There are decimal digits other than ASCII ones. e.g. full width digits(from \uff10 to \uff19) So if a Japanese customer(or someone) entered full width digits, the current AbstractLuhnValidator and EANValidator would perform some unnecessary calculations. BTW, I think I'm going to use them with something like @Pattern(regex="^\\d*$", message="Must be ASCII digits") and @NotNull. Becase I don't like my customers to enter full width digits rather than ASCII ones. Otherwise, it might be possible for them to handle all decimal digits in the world(Unicode). Then, I would use them with @Pattern(regex="^\\d*$") anyway ;-) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

2
6
0 / 0

[Hibernate-JIRA] Created: (HHH-2727) Wiki for documentation

by Elliotte Rusty Harold (JIRA)

Wiki for documentation ---------------------- Key: HHH-2727 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2727 Project: Hibernate3 Issue Type: Improvement Components: documentation Environment: http://www.hibernate.org/hib_docs/v3/reference/en/html/ Reporter: Elliotte Rusty Harold Put the reference documentation into a WIKI so me and others can fix small errors, and improve it without having to login to Jira and fill out a bug report for every minor typo. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

2
1
0 / 0

[Hibernate-JIRA] Commented: (HHH-1311) Session.load is O(n) when outside a transaction

by Matt Sgarlata (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1311?page=c... ] Matt Sgarlata commented on HHH-1311: ------------------------------------ I changed around how my view was rendered so that the Hibernate cache was no longer accessed during JSP rendering and my view rendering time went from 120 seconds to 4 seconds. > Session.load is O(n) when outside a transaction > ----------------------------------------------- > > Key: HHH-1311 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1311 > Project: Hibernate3 > Issue Type: Improvement > Components: core > Affects Versions: 3.0.5 > Reporter: Matt Sgarlata > > When retrieving objects from the session-level cache, session.load is O(n) when outside a transaction, where n = the number of objects currently contained in the session-level cache. This is because after each object is retrieved Hibernate iterates through all objects in the session and sets the lock mode to LockMode.NONE. This means reading all objects from the Hibernate session-level cache while outside a transaction is an O(n^2) operation instead of an O(n) operation. > If my understanding is correct, all objects in the session should already have that lock mode unless a different lock mode was specifically requested by the user. Thus iterating through all objects in the session is not necessary in the vast majority of cases. I think performance could be improved here by maintaining a cache of the objects in the session that are currently locked. Then performance of session.load would be O(m) where m is the number of objects which are currently locked in the session. In the vast majority of cases this would effectively make session.load a O(1) operation since objects in the session typically are not locked. > The other solution for me, of course, would be to just wrap all web requests so that I begin transactions at the start of the request and end transactions at the end of the request. However, I don't want to do that because transactions require database resources and I feel it's not necessary to incur that overhead on the read-only screens in my application. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

1
0
0 / 0

[Hibernate-JIRA] Created: (EJB-304) Multiple @OneToMany(fetch=FetchType.EAGER) realized by List not supported

by Morten Andersen-Gott (JIRA)

Multiple @OneToMany(fetch=FetchType.EAGER) realized by List not supported ------------------------------------------------------------------------- Key: EJB-304 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-304 Project: Hibernate Entity Manager Issue Type: Bug Affects Versions: 3.2.0.cr1 Environment: JBoss4.0.4.GA Reporter: Morten Andersen-Gott Having more than one relationship on en entity annotated with @OneToMany(fetch=FetchType.EAGER) causes exception when deploying the ejb3 module: org.hibernate.HibernateException: cannot simultaneously fetch multiple bags. This bug is thoroughly explained here: http://www.jroller.com/page/eyallupu?entry=hibernate_exception_simultaneo... and depends on HHH-1718 "Have multiple bag fetches revert to subselect fetching for all but one of the bags" The temporary solution in HHH-1413 - disallowing multiple bag fetches is unsuitable to ejb3 environment, because the spec does not disallow it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

2
3
0 / 0

[Hibernate-JIRA] Updated: (HHH-1718) Have multiple bag fetches revert to subselect fetching for all but one of the bags

by Christian Bauer (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1718?page=c... ] Christian Bauer updated HHH-1718: --------------------------------- Comment: was deleted > Have multiple bag fetches revert to subselect fetching for all but one of the bags > ---------------------------------------------------------------------------------- > > Key: HHH-1718 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1718 > Project: Hibernate3 > Issue Type: Improvement > Components: core, query-criteria, query-hql > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Fix For: hql+collection > > > Follow on to HHH-1413. Multiple bag fetches were simply disallowed as the resolution to that particular case in the interest of working around that issue. > The correct longer term solution is to not fetch all the bags at once, ideally reverting to subselect fetching for all but one of the bags. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

1
0
0 / 0

[Hibernate-JIRA] Updated: (HHH-1718) Have multiple bag fetches revert to subselect fetching for all but one of the bags

by Christian Bauer (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1718?page=c... ] Christian Bauer updated HHH-1718: --------------------------------- Comment: was deleted > Have multiple bag fetches revert to subselect fetching for all but one of the bags > ---------------------------------------------------------------------------------- > > Key: HHH-1718 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1718 > Project: Hibernate3 > Issue Type: Improvement > Components: core, query-criteria, query-hql > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Fix For: hql+collection > > > Follow on to HHH-1413. Multiple bag fetches were simply disallowed as the resolution to that particular case in the interest of working around that issue. > The correct longer term solution is to not fetch all the bags at once, ideally reverting to subselect fetching for all but one of the bags. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1718) Have multiple bag fetches revert to subselect fetching for all but one of the bags

by Morten Andersen-Gott (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1718?page=c... ] Morten Andersen-Gott commented on HHH-1718: ------------------------------------------- As this is a show stopper for people using Hibernate as the persistence provider in a JPA solution I can't understand why the issue is categorized as an "Improvement" and not a "Bug". Maybe recategorizing it as a Bug would speed things up? > Have multiple bag fetches revert to subselect fetching for all but one of the bags > ---------------------------------------------------------------------------------- > > Key: HHH-1718 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1718 > Project: Hibernate3 > Issue Type: Improvement > Components: core, query-criteria, query-hql > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Fix For: hql+collection > > > Follow on to HHH-1413. Multiple bag fetches were simply disallowed as the resolution to that particular case in the interest of working around that issue. > The correct longer term solution is to not fetch all the bags at once, ideally reverting to subselect fetching for all but one of the bags. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1718) Have multiple bag fetches revert to subselect fetching for all but one of the bags

by Morten Andersen-Gott (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1718?page=c... ] Morten Andersen-Gott commented on HHH-1718: ------------------------------------------- What does awaiting test case mean? How far along is this fix? Is there an estimate on when we might expect a fix for this? As our object graph grows with several *ToMany relationships realized by Lists this issue is becoming more of a pain every day. Using IndexColumn ties our implementation to Hibernate, which isn't something we want to do. (We are sticking to the JPA spec when mapping our objects) > Have multiple bag fetches revert to subselect fetching for all but one of the bags > ---------------------------------------------------------------------------------- > > Key: HHH-1718 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1718 > Project: Hibernate3 > Issue Type: Improvement > Components: core, query-criteria, query-hql > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Fix For: hql+collection > > > Follow on to HHH-1413. Multiple bag fetches were simply disallowed as the resolution to that particular case in the interest of working around that issue. > The correct longer term solution is to not fetch all the bags at once, ideally reverting to subselect fetching for all but one of the bags. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues July 2007