March 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-5562) Improve how event listeners are handled and introduce a serivice pattern for integrators to leverage

by Steve Ebersole (JIRA)

Improve how event listeners are handled and introduce a serivice pattern for integrators to leverage ---------------------------------------------------------------------------------------------------- Key: HHH-5562 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5562 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.6.0.CR1 Main points: # de-dup listener instances registered by classname # define a service pattern to allow integrations (search, validator and envers as main targets) to auto register their event listeners -- 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

15 years

2
12
0 / 0

[Hibernate-JIRA] Created: (HHH-6060) Go back and document @since for api/spi contracts added for 4.0 development

by Steve Ebersole (JIRA)

Go back and document @since for api/spi contracts added for 4.0 development --------------------------------------------------------------------------- Key: HHH-6060 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6060 Project: Hibernate Core Issue Type: Task Reporter: Steve Ebersole Assignee: Steve Ebersole Priority: Trivial I have also started adding @jira to name the jira key(s) for the issue(s) which introduced that contract to help gain insight into its genesis. A nice-to-have would be a doclet tag processor to convert that into the URL during javadoc generation. -- 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

15 years

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5697) Support for multi-tenancy

by Steve Ebersole (JIRA)

Support for multi-tenancy ------------------------- Key: HHH-5697 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5697 Project: Hibernate Core Issue Type: New Feature Components: core Reporter: Steve Ebersole Fix For: 4.0.0.Alpha2 Thinking that all that is really needed here is the ability to tell the Session (session creation options?) which tenant it is for. Then, this could be "handled" or "applied" by the {{ConnectionProvider}} -- 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

15 years

1
8
0 / 0

[Hibernate-JIRA] Created: (HHH-6053) Create an interface for centralizing the contract that is shared between Session and StatelessSession

by Steve Ebersole (JIRA)

Create an interface for centralizing the contract that is shared between Session and StatelessSession ----------------------------------------------------------------------------------------------------- Key: HHH-6053 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6053 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 4.0.0.Alpha2 Define the shared methods once. -- 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

15 years

1
1
0 / 0

[Hibernate-JIRA] Commented: (HHH-951) setMaxResults causes "ORA-00918: column ambiguously defined" exception

by Danilo Ghirardelli (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-951?page=co... ] Danilo Ghirardelli commented on HHH-951: ---------------------------------------- Same problem for me, Hibernate 3.6.1 Final on Oracle 10 and 11. I was struck with this and I found a workaround, if could help anybody. My original query was like: {code} Criteria crit = ses.createCriteria(MyClass.class); // Tons of conditions crit.setMaxResults(50); {code} I changed it in a DetachedCriteria to "help" hibernate, like this: {code} DetachedCriteria crit = DetachedCriteria.forClass(MyClass.class); // Tons of conditions (the same as before) crit.setProjection(Projections.distinct(Projections.property("id"))); Criteria outerCrit = ses.createCriteria(MyClass.class); outerCrit.add(Subqueries.propertyIn("id", crit)); outerCrit.setMaxResults(50); {code} This trick will get rid of all join conditions from the "external" query, so the "SELECT * FROM query WHERE ROWNUM <= ?" doesn't have the ambiguous column problem anymore. Obviously an "IN" condition might be really heavy for the db, depending on cases. I hope the query planner is smart enough to understand that the external "IN" has no real meaning and can be simplified internally. For what I've tested, it seems that this is the case on the latest versions of Oracle, but might not be true for all cases. Hope this helps, anyway. > setMaxResults causes "ORA-00918: column ambiguously defined" exception > ----------------------------------------------------------------------- > > Key: HHH-951 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-951 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.0.5, 3.1 beta 2, 3.5.3, 3.6.1 > Environment: hibernate3.0.5, hibernate3.1b2, Oracle 9 > Reporter: Karel Sommer > Attachments: Hibernate_SQL_HHH-5579.txt, Hibernate_StackTrace_HHH-5579.txt, TestCase_for_Hibernate_Core_Issue_HHH-5579.zip > > > when create criteria with associations, i get this error: > ORA-00918: column ambiguously defined > mapping: > <class name="User" table="FRAME_USER" dynamic-update="true" dynamic-insert="true"> > <id name="id" type="long" unsaved-value="null"> > <column name="ID" not-null="true"/> > <generator class="sequence"> > <param name="sequence">frame_user_seq</param> > </generator> > </id> > <version type="timestamp" column="stamp" name="timestamp" unsaved-value="null"/> > <property name="user_name" type="string" not-null="true"/> > <property name="blocked" type="yes_no" not-null="true"/> > <property name="access_logon" type="timestamp"/> > <property name="denied_logon" type="timestamp"/> > <property name="inactivity_time" type="long"/> > <property name="session_count" type="long"/> > <idbag name="terminalGroups" table="FRAME_USER_TERMINAL" fetch="join" outer-join="true"> > <collection-id column="ID" type="long"> > <generator class="sequence"> > <param name="sequence">frame_user_terminal_seq</param> > </generator> > </collection-id> > <key column="id_user"/> > <many-to-many column="id_terminal_groups" class="TerminalGroup" fetch="join" outer-join="true"/> > </idbag> > </class> > <class name="TerminalGroup" table="FRAME_TERMINAL_GROUPS" dynamic-update="true" dynamic-insert="true"> > <id name="id" type="long" unsaved-value="null"> > <column name="ID" not-null="true"/> > <generator class="sequence"> > <param name="sequence">frame_terminal_groups_seq</param> > </generator> > </id> > <version type="timestamp" column="stamp" name="timestamp" unsaved-value="null"/> > <property name="name" column="group_name" type="string" not-null="true"/> > <idbag name="terminals" table="FRAME_TERMINAL_REL" fetch="join" outer-join="true"> > <collection-id column="ID" type="long" > > <generator class="sequence"> > <param name="sequence">frame_terminal_rel_seq</param> > </generator> > </collection-id> > <key column="id_term_group"/> > <many-to-many column="id_term" class="Terminal" fetch="join" outer-join="true"/> > </idbag> > </class> > <class name="Terminal" table="FRAME_TERMINAL" where="status != 'D'" dynamic-update="true" dynamic-insert="true"> > <id name="id" type="long" unsaved-value="null"> > <column name="ID" not-null="true"/> > <generator class="sequence"> > <param name="sequence">frame_terminal_seq</param> > </generator> > </id> > <version type="timestamp" column="stamp" name="timestamp" unsaved-value="null"/> > <property name="status" type="char" not-null="true"/> > <property name="mac" type="string" not-null="true"/> > <property name="name" column="ident" type="string" not-null="true"/> > <property name="description" type="string"/> > code: > session.createCriteria(User.class) > .add(Restrictions.like("user_name", "%") > .createCriteria("terminalGroups") > .add( Restrictions.like("group_name", "%"). > .setProjection(Projections.rowCount()) > .uniqueResult(); -- 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

15 years

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3769) Enabling jmx statistics cause OOM

by Sid (JIRA)

Enabling jmx statistics cause OOM --------------------------------- Key: HHH-3769 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3769 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.2.0.ga Reporter: Sid It looks like when org.hibernate.jmx.StatisticsService.statisticsEnabled=true all query strings get logged to org.hibernate.stat.StatisticsImpl.queryStatistics. There is a clear method in org.hibernate.stat.StatisticsImpl that reset all statistics but i don't see this method being called other than when some one calls org.hibernate.jmx.StatisticsService.clear() As queryStatistics is a HasMap this will causes OOM. -- 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

15 years

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-6051) Create a sessionfactory scoped ServiceRegistry

by Steve Ebersole (JIRA)

Create a sessionfactory scoped ServiceRegistry ---------------------------------------------- Key: HHH-6051 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6051 Project: Hibernate Core Issue Type: Task Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 4.0.0.Alpha2 Create a {{ServiceRegistry}} implementation that is scoped to the {{SessionFactory}} -- 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

15 years

1
2
0 / 0

[Hibernate-JIRA] Commented: (HHH-1050) HQL Unions

by giovanni stiwes (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1050?page=c... ] giovanni stiwes commented on HHH-1050: -------------------------------------- someone managed to run the union in mysql 5.5 > HQL Unions > ---------- > > Key: HHH-1050 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1050 > Project: Hibernate Core > Issue Type: New Feature > Components: query-hql > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Fix For: antlr-rework > > > Add the ability to define unions in HQL. Support will be initially limited to only: > 1) scalar queries : select id from Animal union select id from Car > 2) the same entity : from Animal where ... union from Animal where ... > Support both UNION and UNION ALL -- 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

15 years

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1050) HQL Unions

by giovanni stiwes (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1050?page=c... ] giovanni stiwes commented on HHH-1050: -------------------------------------- I'm having the same problem (query truncation) > HQL Unions > ---------- > > Key: HHH-1050 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1050 > Project: Hibernate Core > Issue Type: New Feature > Components: query-hql > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Fix For: antlr-rework > > > Add the ability to define unions in HQL. Support will be initially limited to only: > 1) scalar queries : select id from Animal union select id from Car > 2) the same entity : from Animal where ... union from Animal where ... > Support both UNION and UNION ALL -- 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

15 years

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3593) be able to configure statistics enablement

by John Mazzitelli (JIRA)

be able to configure statistics enablement ------------------------------------------ Key: HHH-3593 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3593 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: John Mazzitelli Priority: Minor Right now, in order to enable Hibernate to collect and emit statistics to monitoring tools, your application has to manually execute code similar to the following: StatisticsService mBean = new StatisticsService(); SessionFactory sessionFactory = ...get hibernate session factory... mBean.setSessionFactory(sessionFactory); ObjectName objectName = new ObjectName("Hibernate:application=MY_APP_NAME,type=statistics"); MBeanServer mbs = ManagementFactory.getPlatformMBeanServer(); mbs.registerMBean(mBean, objectName); sessionFactory.getStatistics().setStatisticsEnabled(true); It would be nice if this was configurable, so a user of Hibernate doesn't need to write this code. For example: hibernate.statistics.enabled=true hibernate.statistics.objectname=Hibernate:application=MY_APP_NAME,type=statistics hibernate.statistics.mbeanserver=*platform* This would turn on Hibernate statistics and tell it to register the Statistics MBean in the JVM's platform MBean Server (ManagementFactory.getPlatformMBeanServer). Of course, *platform* would only be valid on Java5 or higher VMs. Note that hibernate will need to allow the object name to be configurable as well. Or... hibernate.statistics.enabled=true hibernate.statistics.objectname=Hibernate:application=MY_APP_NAME,type=statistics hibernate.statistics.mbeanserver=my_mbs_name This tells Hibernate to register the MBean in the named MBeanServer where the "my_mbs_name" is the default domain name of the MBeanServer you want (if it doesn't exist, Hibernate should create the MBeanServer with the named default domain). In fact, I had the Remoting project do something similar, so you can see code that gets the MBeanServer using these two ways by looking at the .patch attached to: https://jira.jboss.org/jira/browse/JBREM-746 and its related fix. -- 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

15 years

3
10
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues March 2011