January 2013 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (ANN-787) @UniqueConstraint annotation not creating unique indexes

by Avinash THM (JIRA)

@UniqueConstraint annotation not creating unique indexes -------------------------------------------------------- Key: ANN-787 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-787 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.1.GA Environment: hibernate-core 3.3.1GA, hibernate-annotations 3.4.0GA, DB2 version 9.1 Reporter: Avinash THM Priority: Minor Unique indexes are not being created when using @UniqueConstraint annotation. The tables are created properly with primary keys and foreign keys, but the unique indexes are not created. I have posted the issue in hibernate forum (http://forum.hibernate.org/viewtopic.php?t=991505&highlight=) but didnt get any reply. I have also seen a couple of posts for the same problem. can anybody help me out with this issue? -- 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

13 years, 2 months

2
1
0 / 0

[Hibernate-JIRA] (HV-684) Some follow-up tasks/minor todos

by Gunnar Morling (JIRA)

13 years, 2 months

1
2
0 / 0

[Hibernate-JIRA] (HHH-7552) New StrategySelectorService

by Steve Ebersole (JIRA)

13 years, 2 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-4857) Sharing some of the config info from Ejb3Configuration and SessionFactoryImpl

by Chris Baxter (JIRA)

Sharing some of the config info from Ejb3Configuration and SessionFactoryImpl ----------------------------------------------------------------------------- Key: HHH-4857 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4857 Project: Hibernate Core Issue Type: New Feature Components: core, entity-manager Reporter: Chris Baxter Priority: Minor In our system, we have each clients data in a separate DB instance. We're using JPA (via hibernate) on top of that to get at the data. The problem here is that for each client DB supported by one of our jboss servers, we have to have an instance of EntityManagerFactory compete with an Ejb3Configuration instance. Each config instance takes up around 20 MBs of permanent space, so if we have have 1000 client DBs supported by a jboss instance, it takes up a hugh amount of memory for information that will always be the same (the DB schemas are always the exact same in each client DB) across all EntityManagerFactory instances. So what I want to know is if there is a way to only have one instance of Ejb3Configuration that can be shared across all of the EntityManagerFactory instances that are spawning my EntityManagers. This would be huge as it would help me save many gigs of memory that never can be collected (old gen in jboss). I prototyped some changes locally to Ejb3Configuration (to allow an instance of AnnotationConfiguration to be supplied in the constructor, allowing sharing across all instanced of this class) and to SessionFactoryImpl (to share some of the properties like entityPersisters, classMetadata and such) and I was able to reduce the footprint to 20 MBs for the first DB and then under a MB for each additional DB. The changes I made were a bit quick and dirty though, just to see if it was possible. So I'm taking out this feature request to see if this is a piece of work that you guys can do (or I can contribute after refactoring to a more suitable approach) and integrate into the main code for hibernate-core and hibernate-entitymanager. Let me know if this is something you guys think to be a valuable addition. -- 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

13 years, 2 months

5
20
0 / 0

[Hibernate-JIRA] (JPA-37) org.hibernate.HibernateException: Wrong column type in for column. Found: smallint, expected: integer

by Matti Linnanvuori (JIRA)

13 years, 2 months

1
2
0 / 0

[Hibernate-JIRA] (HHH-7548) whitespace char throwing StringIndexOutOfBoundsException

by Martin (JIRA)

13 years, 2 months

2
2
0 / 0

[Hibernate-JIRA] (HHH-7861) EntityManager.find() throws EntityNotFoundException when entity is not found

by Zbyněk Roubalík (JIRA)

13 years, 2 months

4
38
0 / 0

[Hibernate-JIRA] Created: (HV-477) Investigate how parameter and return value validation can be consolidated

by Gunnar Morling (JIRA)

Investigate how parameter and return value validation can be consolidated ------------------------------------------------------------------------- Key: HV-477 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-477 Project: Hibernate Validator Issue Type: Improvement Components: engine Reporter: Gunnar Morling Fix For: 4.x Currently there are some redundancies in the code for parameter and for return value validation ({{ValidatorImpl}}. Maybe it's possible to generify and unify the existing code and use it in both cases. -- 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

13 years, 2 months

2
12
0 / 0

[Hibernate-JIRA] (HHH-7928) Regression caused by HHH-6361

by Steve Ebersole (JIRA)

13 years, 2 months

2
11
0 / 0

[Hibernate-JIRA] (OGM-230) OGM em.find() is not polymorphic

by Jonathan Wood (JIRA)

13 years, 2 months

3
23
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 January 2013