May 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Updated: (ANN-161) Add support for custom code-based enums in EnumType - such as mapping ISO codes to gender Enums

by Frederic Leitenberger (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-161?page=co... ] Frederic Leitenberger updated ANN-161: -------------------------------------- Attachment: MappedEnum.java.patch Hello, i have developed an integrated solution for the custom Enum mapping problem. I created an Interface MappedEnum and modified the EnumType class accordingly. Now it is possible to define a custom Enum dbValue-Mapping like this: import org.hibernate.type.MappedEnum; public enum ExampleEnum implements MappedEnum { BLACK(100), // BLUE(200), RED(300), GREEN(400); private final int dbValue; private ExampleEnum(int dbValue) { this.dbValue = dbValue; } public int getDbValue() { return dbValue; } } I tested several scenarios: 1.) Saving an MappedEnum: Transaction tx = session.beginTransaction(); try { TestEntity testEntity = new TestEntity(); testEntity.setColor(ExampleEnum.BLUE); session.save(testEntity); tx.commit(); System.out.println(testEntity); } catch (Exception e) { tx.rollback(); throw e; } 2.) Loading an MappedEnum with Criteria and Restrictions.eq: session.createCriteria(TestEntity.class).add(Restrictions.eq("color", ExampleEnum.BLUE)); 3.) Loading an MappedEnum with Query and setParameter: session.createQuery("from TestEntity where color = ?").setParameter(0, ExampleEnum.BLUE); 4.) Loading an MappedEnum with Query and the dbValue directly: session.createQuery("from TestEntity where color = " + ExampleEnum.BLUE.getDbValue()) Everything worked fine. The trick is to replace the ordinal-enum-mapping by the dbValue-enum-Mapping inside the EnumType-class if the MappedEnum-interface is implemented. Therefore i replaced the internal array (which contained the enum-constants) by a HashMap. This enables me to put in arbitrary numbers as key. When the MappedEnum-interface is implemented the getDbValue() function for each constant is used to get the key. If it is not implemented the ordinal-value is used (like before). > Add support for custom code-based enums in EnumType - such as mapping ISO codes to gender Enums > ----------------------------------------------------------------------------------------------- > > Key: ANN-161 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-161 > Project: Hibernate Annotations > Issue Type: Improvement > Components: binder > Affects Versions: 3.1beta6 > Reporter: Leonardo Quijano > Priority: Minor > Attachments: MappedEnum.java.patch > > > Now, this could be seen as an improvement to EnumType that's specific to a business domain, but I'm thinking it could help in the general case. Right now we can map JDK enums to several database types, such as INT, VARCHAR, etc. Each of these approaches have some drawbacks, depending on the domain: > 1) The int mapping is not very reliable through refactorings. An enum that's mapped to a "0" or "2" integer value in the database could end up mapped as a different value if a future refactoring adds an additional enum with an ordinal of 0. > 2) The varchar mapping could use the enum name instead of its ordinal. But again, if the enum changes, the mapping gets lost and it needs manual changes. It's also heavier on the performance side. > A useful approach for enum mappings is to use common codes to represent them in the database. That depends of course of the domain logic that's being used. A useful example is the Human sex mapping, defined in ISO code 5218: > http://en.wikipedia.org/wiki/ISO_5218 > * 0 = not known, > * 1 = male, > * 2 = female, > * 9 = not specified. > For this to work, the Sex enum could have a property "isoCode" that specifies the mapping between the database integer code and the Java enum. > For other domain examples additional examples could be specified. > The EnumType could include a parameter that indicates the property to be evaluated for code-mapping, performing the translation in this way. Of course, reflection cache / byte-code generation / whatever could be specified to speed up the process. > As always, patches are offered if you think this improvement is viable. -- 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3296) SchemaExport ignores user-specified unique index name

by Sto (JIRA)

SchemaExport ignores user-specified unique index name ----------------------------------------------------- Key: HHH-3296 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3296 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.6 Environment: Hibernate 3.2.6 Oracle, MS SqlServer Reporter: Sto Priority: Trivial Can't provide user defined name for unique constraints -- 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-879) Enable joining the same association twice with Criteria

by Paul White (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-879?page=co... ] Paul White commented on HHH-879: -------------------------------- This limitation/bug is very dissapointing. I understand this it's a difficult problem to solve but I wish the Hibernate team was a lot more open about the kind of things you can and can't do with the criteria API in the documentation. I will have to undo a great deal of work and go back to SQL generation after discovering this limitation. > Enable joining the same association twice with Criteria > ------------------------------------------------------- > > Key: HHH-879 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-879 > Project: Hibernate3 > Issue Type: Improvement > Components: core > Reporter: Vladimir Bayanov > > Make double joining the same association with Criteria.createCriteria possible. See: http://forum.hibernate.org/viewtopic.php?t=931249 -- 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3295) Hibernate 3 Core source-zips are missing all classes in org.hibernate.hql.antlr

by S.Schnabl (JIRA)

Hibernate 3 Core source-zips are missing all classes in org.hibernate.hql.antlr ------------------------------------------------------------------------------- Key: HHH-3295 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3295 Project: Hibernate3 Issue Type: Bug Components: build Affects Versions: 3.2.6, 3.2.5 Environment: Win-XP, Hibernate 3 Core Reporter: S.Schnabl Priority: Minor The source-zip files of Hibernate 3 has only an empty org.hibernate.hql.antlr package. All classes in this package are missing in the released source-archive. This leads to the fact, that a build of hibernate isn't possible due to compile errors. -- 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-169) Migrate to Lucene 2.3.1 (index corruption possiblity in 2.3.0)

by Przemyslaw Jaskierski (JIRA)

Migrate to Lucene 2.3.1 (index corruption possiblity in 2.3.0) -------------------------------------------------------------- Key: HSEARCH-169 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-169 Project: Hibernate Search Issue Type: Bug Reporter: Przemyslaw Jaskierski http://svn.apache.org/repos/asf/lucene/java/tags/lucene_2_3_1/CHANGES.txt -- 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, 10 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HCANN-1) Move to sl4j

by Emmanuel Bernard (JIRA)

Move to sl4j ------------ Key: HCANN-1 URL: http://opensource.atlassian.com/projects/hibernate/browse/HCANN-1 Project: Hibernate Commons Annotations Issue Type: New Feature Reporter: Emmanuel Bernard Fix For: 3.1.0.CR1 -- 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, 10 months

1
2
0 / 0

[Hibernate-JIRA] Created: (ANN-739) @Id annotation of field does not mark get/set methods in Proxy to no require load of object

by Eduard Martinescu (JIRA)

@Id annotation of field does not mark get/set methods in Proxy to no require load of object ------------------------------------------------------------------------------------------- Key: ANN-739 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-739 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.1.GA, 3.3.0.ga Environment: Hibernate 3.2.5, Sybase 15 Reporter: Eduard Martinescu If you use field level annotations, the created proxy objects are unaware of the get/set methods for the id property, so any call to 'getId()' causes the object to be loaded, when it should just return the id without loading the object from the database. This results in excess database requests that are completely unnecissary. -- 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, 10 months

2
1
0 / 0

[Hibernate-JIRA] Created: (ANN-713) Use an ant task to deploy the maven artifacts

by Emmanuel Bernard (JIRA)

Use an ant task to deploy the maven artifacts --------------------------------------------- Key: ANN-713 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-713 Project: Hibernate Annotations Issue Type: New Feature Reporter: Emmanuel Bernard This is what we use in Seam* (I assume you are using Maven Ant Tasks to generate your deployment): <jar jarfile="${src.jar}" basedir="${src.dir}"> <include name="**/*.java" /> <exclude name="**/test/*.java" /> <patternset refid="meta.files" /> </jar> <artifact:remoteRepository id="offline.repository.jboss.org" url="file:///${offline.repository.jboss.org}" /> <artifact:deploy file="${bin.jar}"> <pom file="${pom.file} /> <remoteRepository refId="offine.repository.jboss.org" /> <attach file="${src.jar}" classifier="sources" /> </artifact:deploy> You can then commit the results to svn * Well, actually, it's all wrapped up in macrodef's, but this is them expanded out -- 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, 10 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HV-58) @Digits broken with string not representing a numeric

by Anthony Patricio (JIRA)

@Digits broken with string not representing a numeric ----------------------------------------------------- Key: HV-58 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-58 Project: Hibernate Validator Issue Type: Bug Components: validators Affects Versions: 3.0.0.ga Reporter: Anthony Patricio @Digits hibernate validator is not working. using @Pattern(regex=...) @Digits(integerDigits=5, message="PERMITTED BARCODE LENGTH MUST BE 5") The @Digits validator does not work properly (e.g. if I enter "efg" in the inputText, I should see the err msg in h:messages component). refer to: http://forum.hibernate.org/viewtopic.php?t=972868 -- 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1471) If the 'generated' attribute is set to 'insert' or 'always' on the property of a component it is ignored and the value is not read from the database.

by Shyamsunder (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1471?page=c... ] Shyamsunder commented on HHH-1471: ---------------------------------- I have used hibernate 3.2.6 GA library. But the the following column is never updated in database. I have added this column in an Entity and in a component. A select query is issued after the entity is saved. But lastModified column has null value. <property name="lastModified" column="LAST_MODIFIED" update="false" insert="false" generated="always" > Can some one post a working example? Also let me know if my hibernate mapping is valid. Thanks Shyam > If the 'generated' attribute is set to 'insert' or 'always' on the property of a component it is ignored and the value is not read from the database. > ----------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: HHH-1471 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1471 > Project: Hibernate3 > Issue Type: Bug > Components: core > Affects Versions: 3.1.2 > Reporter: Darran Lofthouse > Assignee: Steve Ebersole > Fix For: 3.2.2 > > Attachments: patch.txt > > > If the 'generated' attribute is set to 'insert' or 'always' on the property of a component it is ignored and the value is not read from the database. > Turning on debug logging shows no select statement being executed to retrieve the property. Using the generated attribute in the parent class works fine. > I have updated the existing ComponentTest test case so the Person class now has a username property that should be retrieved from the database with generated set to 'insert'. -- 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, 10 months

1
0
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 May 2008