November 2012 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-6769) invalid Character - problem with aliasing

by bahadir guldiken (JIRA)

invalid Character - problem with aliasing ----------------------------------------- Key: HHH-6769 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6769 Project: Hibernate Core Issue Type: Bug Components: core, query-hql Affects Versions: 3.2.6 Environment: oracle 10g, glassfish2.1, solarıs 10, Hibernate3.2.6GA Reporter: bahadir guldiken We have a system running for months without any problem. But somewhat it started to get intermittently: javax.persistence.PersistenceException: org.hibernate.exception.SQLGrammarException: could not execute query ORA-00911 illegal character When we enabled "show_sql" from persistence.xml, we get the following query: Hibernate: select party?dent0_.identity_id as identity1_36_, party?dent0_.description as descript2_36_, party?dent0_.identification_type_id as identifi9_36_, party?dent0_.identity_no as identity3_36_, party?dent0_.issue_date as issue4_36_, party?dent0_.lang_id as lang10_36_, party?dent0_.name as name36_, party?dent0_.party_id as party11_36_, party?dent0_.scan_image as scan6_36_, party?dent0_.validFor_end_date as validFor7_36_, party?dent0_.validFor_start_date as validFor8_36_ from party_identification party?dent0_ where party?dent0_.identity_no=?|#] It seems the aliasing "from party_identification party?dent0_" causing the problem by putting '?'. We suspected from locale or other things but turned away since restarting application was solving the problem for a random period. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

2
3
0 / 0

[Hibernate-JIRA] Created: (BVAL-223) Add formatter syntax for interpolated messages

by Emmanuel Bernard (JIRA)

Add formatter syntax for interpolated messages ---------------------------------------------- Key: BVAL-223 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-223 Project: Bean Validation Issue Type: New Feature Components: spec-general Reporter: Emmanuel Bernard -- 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

11 years, 11 months

3
8
0 / 0

[Hibernate-JIRA] Created: (HHH-6105) PostgreSQL problem when using @Lob on String field

by Roelof Jan Koekoek (JIRA)

PostgreSQL problem when using @Lob on String field -------------------------------------------------- Key: HHH-6105 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6105 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.6.3, 3.6.2, 3.6.1, 3.6.0 Environment: postgresql:8.3-606.jdbc3 Reporter: Roelof Jan Koekoek After upgrading from 3.5.6 to 3.6 we ran into issues using @Lob on String fields previously mapping to PostgreSQL's TEXT type. When loading these fields the PostgreSQL driver returns a: "org.postgresql.util.PSQLException: Bad value for type long: Text content..." The problem can be traced to Hibernates ClobTypeDescriptor which calls a resultSet.getClob("lobfield"). Apparently it expects an OID pointing to a clob and not the text field. I found a lengthy discussion on this subject here: http://groups.google.com/group/pgsql.interfaces.jdbc/browse_thread/thread... At the bottom of the discussion a workaround is mentioned. Using @Type(type="org.hibernate.type.StringClobType") on the @Lob String fields gets things working as before, but this is a deprecated solution. -- 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

11 years, 11 months

4
3
0 / 0

[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

11 years, 11 months

2
1
0 / 0

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

by Steve Ebersole (JIRA)

11 years, 11 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

11 years, 11 months

5
20
0 / 0

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

by Martin (JIRA)

11 years, 11 months

2
2
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

11 years, 11 months

2
12
0 / 0

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

by Jonathan Wood (JIRA)

11 years, 11 months

3
23
0 / 0

[Hibernate-JIRA] (OGM-233) OGM is not polymorphic

by Jonathan Wood (JIRA)

11 years, 11 months

3
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues November 2012