June 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (BVAL-192) Add 'exclusive' boolean attribute to @DecimalMin/@DecimalMax constraints

by Jaro Kuruc (JIRA)

Add 'exclusive' boolean attribute to @DecimalMin/@DecimalMax constraints ------------------------------------------------------------------------ Key: BVAL-192 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-192 Project: Bean Validation Issue Type: Improvement Components: spec-general Affects Versions: 1.0 final Environment: Hibernate Validator 4.0.0.GA Reporter: Jaro Kuruc Attachments: patch.patch Hi, may I suggest to enhance @DecimalMin/@DecimalMax constraints with additional 'exclusive' boolean attribute? This would allow to define a constraints like: a positive non-zero decimal number @DecimalMin(value = "0.0", exclusive = true) a negative non-zero decimal number @DecimalMax(value = "0.0", exclusive = true) This makes sense when dealing with decimal numbers where one might want to allow a number regardless of the precision. @DecimalMin("0.0001") vs. @DecimalMin("0.000000001"), etc. To maintain backward compatibility, default value for new 'exclusive' boolean attribute should be false. -- 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, 2 months

3
11
0 / 0

[Hibernate-JIRA] Created: (BVAL-219) Consider interpolating the value in error messages

by Emmanuel Bernard (JIRA)

Consider interpolating the value in error messages -------------------------------------------------- Key: BVAL-219 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-219 Project: Bean Validation Issue Type: New Feature Reporter: Emmanuel Bernard The main drawback is that there is no formatting and that we will call value.toString() to resolve the value into string. -- 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, 2 months

3
9
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, 2 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, 2 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, 3 months

2
1
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, 3 months

5
20
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, 3 months

2
12
0 / 0

[Hibernate-JIRA] Created: (HHH-5533) Entity Manager documentation: example at the end of the bootstrapping section is invalid

by Kariem Hussein (JIRA)

Entity Manager documentation: example at the end of the bootstrapping section is invalid ---------------------------------------------------------------------------------------- Key: HHH-5533 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5533 Project: Hibernate Core Issue Type: Patch Components: documentation, entity-manager Reporter: Kariem Hussein The example at the end of the [bootstrapping section of the entity manager documentation|http://docs.jboss.org/hibernate/stable/entitymanager/refere...] contains syntax errors and invalid method calls. *Current version* {code} Ejb3Configuration cfg = new Ejb3Configuration(); EntityManagerFactory emf = cfg.addProperties( properties ) //add some properties .setInterceptor( myInterceptorImpl ) // set an interceptor .addAnnotatedClass( MyAnnotatedClass.class ) //add a class to be mapped .addClass( NonAnnotatedClass.class ) //add an hbm.xml file using the Hibernate convention .addRerousce( "mypath/MyOtherCLass.hbm.xml ) //add an hbm.xml file .addRerousce( "mypath/orm.xml ) //add an EJB3 deployment descriptor .configure("/mypath/hibernate.cfg.xml") //add a regular hibernate.cfg.xml .buildEntityManagerFactory(); //Create the entity manager factory {code} *Problems* - {{addRerousce}} instead of {{addResource}} - strings are not properly closed in lines 7 and 8 - formatting is not consistent (capitalization, spacing) - comments are not aligned -- 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, 3 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3465) HiRDB Support

by Tomoto Shimizu Washio (JIRA)

HiRDB Support ------------- Key: HHH-3465 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3465 Project: Hibernate3 Issue Type: New Feature Components: core Affects Versions: 3.2.5 Environment: 3.2.5 + HiRDB V8 + Type4 JDBC Driver Reporter: Tomoto Shimizu Washio Attachments: hirdbdialect.patch I would like to contribute with a dialect for HiRDB, Hitachi's RDBMS. (For more information, please see http://www.hitachi.co.jp/Prod/comp/soft1/global/prod/hirdb/) I added 4 classes and slightly modified 2 existing classes as shown below. Please look at the documentation at the top of the patch for explanations. org.hibernate.dialect.HiRDBDialect (added) org.hibernate.dialect.UserFuncDeclParser (added) org.hibernate.dialect.DialectFactory (modified) org.hibernate.dialect.function.AnsiTrimEmulationFunction (modified) org.hibernate.dialect.function.AnsiTrimEmulationFunctionWithTrimstrs (added) org.hibernate.dialect.function.TypeQualifiedSQLFunction (added) You may think this code is relatively large as a dialect. It is because I also implemented user-defined function support. As HiRDB requires '?' parameters to be qualified by 'as <type>' in user-defined function invocations, I made a parser for the type declarations that the user specified in the properties file, and a renderer for the type qualifier. See javadoc comments of HiRDBDialect and UserFuncDeclParser for more details. This patch is created on Hibernate 3.2.5.ga and tested on HiRDB V8 with Type4 JDBC Driver. The example configuration for HiRDB is shown below: hibernate.dialect org.hibernate.dialect.HiRDBDialect hibernate.connection.driver_class JP.co.Hitachi.soft.HiRDB.JDBC.HiRDBDriver hibernate.connection.url jdbc:hitachi:hirdb://DBID=@HIRDBENVGRP=C:/hirdb.ini hibernate.connection.username hitachi hibernate.connection.password hitachi -- 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, 3 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-5554) Customise column aliasing scheme

by Chris Pheby (JIRA)

Customise column aliasing scheme -------------------------------- Key: HHH-5554 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5554 Project: Hibernate Core Issue Type: Patch Components: core Affects Versions: 3.6.0.Beta4 Reporter: Chris Pheby Attachments: alias-patch.patch Currently, the column aliasing scheme is hardcoded in the method public String getAlias(Dialect dialect) of the Column class. Essentially, this constructs an alias by creating a prefix using any characters up to the first non-letter character in the column name. This is usually followed by '_' and a number for disambiguation. I am working with a legacy database where many columns share common prefixes such as 'CUS_', 'COL_'. These mean all the aliases end up being the same for many columns, making queries difficult to debug. This patch configures aliasing via Dialect, which was already being done for getMaxAliasLength(). This makes it possible to customise the behaviour by extending the Dialect being used. It does not otherwise change the standard behaviour. -- 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, 3 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues June 2011