March 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3830) Problem with inheritance and @ManyToMany relation

by Jiri Vanek (JIRA)

Problem with inheritance and @ManyToMany relation ------------------------------------------------- Key: HHH-3830 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3830 Project: Hibernate Core Issue Type: Bug Components: envers Reporter: Jiri Vanek problem is descibed here <a href="http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220618#4220618">http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220618#4220618</a> -- 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, 7 months

2
2
0 / 0

[Hibernate-JIRA] Created: (EJB-358) Upgrade to ASM 3.1

by Juergen Zimmermann (JIRA)

Upgrade to ASM 3.1 ------------------ Key: EJB-358 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-358 Project: Hibernate Entity Manager Issue Type: New Feature Components: EntityManager Affects Versions: 3.3.2.GA Reporter: Juergen Zimmermann Hibernate EntityManager depends on ASM 2.2.3 JAX-RS will be the new spec for RESTful web services in Java. The reference implementation (aka Jersey) is available at https://jersey.dev.java.net and uses ASM 3.1. Therefore, Hibernate cannot be combined with the reference implementation of JAX-RS. -- 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, 7 months

4
6
0 / 0

[Hibernate-JIRA] Created: (EJB-369) Upgrade to CGLIB 2.2 (and thus ASM 3.1)

by Juergen Zimmermann (JIRA)

Upgrade to CGLIB 2.2 (and thus ASM 3.1) --------------------------------------- Key: EJB-369 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-369 Project: Hibernate Entity Manager Issue Type: Task Affects Versions: 3.4.0.CR1 Reporter: Juergen Zimmermann CGLIB 2.2 is now available and integrates with ASM 3.1 -- instead of the old, incompatible 2.1.3 -- 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, 7 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-178) Some collection lazy loading lead to AssertionFailure

by Emmanuel Bernard (JIRA)

Some collection lazy loading lead to AssertionFailure ----------------------------------------------------- Key: HSEARCH-178 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-178 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.0.1.GA 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

15 years, 7 months

6
25
0 / 0

[Hibernate-JIRA] Created: (HBX-947) When generating @Version annotation reveng tools should provide ability to set @Generated(GenerationTime.ALWAYS) and insertable = false, updatable = false for @Column

by MG (JIRA)

When generating @Version annotation reveng tools should provide ability to set @Generated(GenerationTime.ALWAYS) and insertable = false, updatable = false for @Column ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: HBX-947 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-947 Project: Hibernate Tools Issue Type: Improvement Components: hbm2java, hbm2seam, reverse-engineer Affects Versions: 3.2beta9, 3.2beta10, 3.2LATER Environment: all Reporter: MG Priority: Minor When generating @Version annotation reveng tools should provide ability to set @Generated(GenerationTime.ALWAYS) and insertable = false, updatable = false for @Column. This behavior sould be configurable via reveng file (I think) This is needed in case version or timestamp is maintained by DB and not hibernate. (Ex: sybase timestamp) hbm.xml have also similar constructs for that, so reveng into hbm.xml might be also impacted. Thanks -- 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, 7 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3420) MatchMode doesn't escape wildcard characters

by Hontvári József (JIRA)

MatchMode doesn't escape wildcard characters -------------------------------------------- Key: HHH-3420 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3420 Project: Hibernate3 Issue Type: Bug Components: query-criteria Affects Versions: 3.2.2 Environment: MySQL Reporter: Hontvári József Priority: Minor One can think that by specifying e.g. MatchMode.START in a "like" restriction Hibernate takes care of escaping SQL LIKE wildcard characters in the supplied pattern. It doesn't, actually Hibernate only inserts a % before the first character. I am not sure what was the intent of the original author (Gavin King), so the issue may only be missing documentation. However I don't see any other useful purpose of this class then providing database independent escaping. It seems that all databases use the % wildcard, so there is no need to provide database indpeendence to that. It can be argued that this might create a security problem for an unaware developer, so I set issue type to bug. -- 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, 7 months

3
2
0 / 0

[Hibernate-JIRA] Created: (ANN-489) add @AttributeOverride with formula support

by Amir Pashazadeh (JIRA)

add @AttributeOverride with formula support ------------------------------------------- Key: ANN-489 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-489 Project: Hibernate Annotations Type: Improvement Components: binder Versions: 3.2.0.ga Reporter: Amir Pashazadeh @AttributeOverride currently just have name and column properties, there can be an alternative with formula support (instead of column support). -- 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, 7 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HBX-1035) Safety: 'Run SchemaExport' menu option

by Karel-Henk Nijhuis (JIRA)

Safety: 'Run SchemaExport' menu option -------------------------------------- Key: HBX-1035 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1035 Project: Hibernate Tools Issue Type: Improvement Components: eclipse Reporter: Karel-Henk Nijhuis The 'Run SchemaExport' option that is accessible from the configuration context menu inside the Eclipse 'Hibernate Configurations' view does not give any feedback. Choosing this option, however, results in executing DDL on the database which erases all data inside the configured database. The schema export option could also be interpreted as a way to get the schema's SQL without executing the DDL. I would suggest to give more appropriate feedback before this operation is run. -- 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, 7 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3499) NamingStrategy should support naming foreign keys and indexes

by Geoffrey De Smet (JIRA)

NamingStrategy should support naming foreign keys and indexes ------------------------------------------------------------- Key: HHH-3499 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3499 Project: Hibernate Core Issue Type: Improvement Components: metamodel Affects Versions: 3.3.1 Reporter: Geoffrey De Smet hbm2ddl always generates foreign key constraints based on hashcodes, like this: alter table apple add index FK365FA4BB24B1D45C (lemon_id), add constraint FK365FA4BB24B1D45C foreign key (lemon_id) references lemon (id); Some databases don't support enough characters for foreign key names to generate a readable foreign key name, so that's a sensible default. However, those of use that use databases like MySQL etc, would like a readable foreign key name, such as: alter table apple add index FK_Apple_lemon (lemon_id), add constraint FK365FA4BB24B1D45C foreign key (lemon_id) references lemon (id); We can do that by annotating every entity with @Index in JPA, or specifying it in a hbm file, but we can't do it generally, by extending DefaultNamingStrategy or ImprovedNamingStrategy. Here's a proposition on how we could do it: - In the NamingStrategy interface, next to the method foreignKeyColumnName, add a method: public String foreignKeyConstraintName(String propertyName, String propertyEntityName, String propertyTableName, String referencedColumnName - DefaultNamingStrategy and ImprovedNamingStrategy should implement it as it is now, based on hashcodes. - If a mapping has an @Index JPA annotation or it's specified in a hbm file, that override counts. -- 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, 7 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3773) NPE when generating schema containing OneToMany relations

by Tobias Hill (JIRA)

NPE when generating schema containing OneToMany relations ---------------------------------------------------------- Key: HHH-3773 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3773 Project: Hibernate Core Issue Type: Bug Components: envers Reporter: Tobias Hill I have an entity P having a one-to-many relation to an entity C. I mark P as @Audited. I do not mark C as @Audited. Neither do I mark the field containing the relation from P to Cs. When building the schema I get: java.lang.NullPointerException at org.hibernate.envers.configuration.metadata.CollectionMetadataGenerator.addOneToManyAttached(CollectionMetadataGenerator.java:164) at org.hibernate.envers.configuration.metadata.CollectionMetadataGenerator.addCollection(CollectionMetadataGenerator.java:150) at org.hibernate.envers.configuration.metadata.AuditMetadataGenerator.addValue(AuditMetadataGenerator.java:141) at org.hibernate.envers.configuration.metadata.AuditMetadataGenerator.addProperties(AuditMetadataGenerator.java:161) at org.hibernate.envers.configuration.metadata.AuditMetadataGenerator.generateSecondPass(AuditMetadataGenerator.java:385) If I mark C as @Audited it goes away and the schema is generated as supposed to. -- 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, 7 months

3
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues March 2009