March 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-5687) Extract SQL keywords from DatabaseMetaData

by Steve Ebersole (JIRA)

Extract SQL keywords from DatabaseMetaData ------------------------------------------ Key: HHH-5687 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5687 Project: Hibernate Core Issue Type: New Feature Components: core Reporter: Steve Ebersole Fix For: 4.0.0.Alpha1 {{java.sql.DatabaseMetaData.html#getSQLKeywords}} is defined to return the (comma separated list of) keywords for the given database above-and-beyond the set of standard (SQL 2003) keywords. We should leverage this information while we build the JbdcServices to build out a fuller picture of database keywords to allow Dialect developers a choice between defining keywords themselves versus utilizing the extracted information. This would become part of the {{org.hibernate.engine.jdbc.spi.ExtractedDatabaseMetaData}}. The list of SQL 2003 keywords can be found at http://savage.net.au/SQL/sql-2003-2.bnf.html#xref-keywords -- 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, 6 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5981) Clarify Session.disconnect() and Session.reconnect() behavior

by Steve Ebersole (JIRA)

Clarify Session.disconnect() and Session.reconnect() behavior ------------------------------------------------------------- Key: HHH-5981 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5981 Project: Hibernate Core Issue Type: Remove Feature Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 4.0.0.Alpha1 Specific changes: # disallow disconnect() except in cases where the user supplied the connection to the session # disallow disconnect() if there is an existing, active transaction associated with the Session. # remove reconnect() (it has been deprecated for some time now) # disallow reconnect(Connection) unless the user initially supplied the connection to the Session -- 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, 6 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5949) Migrate, complete and integrate TransactionFactory as a service

by Steve Ebersole (JIRA)

Migrate, complete and integrate TransactionFactory as a service --------------------------------------------------------------- Key: HHH-5949 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5949 Project: Hibernate Core Issue Type: Task Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 4.0.0.Alpha1 Migrate and finalize the work done t implement TransactionFactory as a Service from the SourceForge Hibernate Git repo. Then integrate it into SessionFactory et al. -- 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, 6 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-687) Expose core of query engine as SPI for use by alternative object sources (independent of Hibernate Core)

by Emmanuel Bernard (JIRA)

Expose core of query engine as SPI for use by alternative object sources (independent of Hibernate Core) -------------------------------------------------------------------------------------------------------- Key: HSEARCH-687 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-687 Project: Hibernate Search Issue Type: New Feature Components: engine, query Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard Fix For: 3.4.0 -- 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, 6 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5980) CacheKey is storing references to entities instead of identifiers

by Ian Brandt (JIRA)

CacheKey is storing references to entities instead of identifiers ----------------------------------------------------------------- Key: HHH-5980 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5980 Project: Hibernate Core Issue Type: Bug Components: caching (L2), core Affects Versions: 3.6.1 Environment: Ehcache 2.3.2. Reporter: Ian Brandt Attachments: hibernate-cachekey-bug.tgz I'm hitting an issue seemingly similar to HHH-3383, but with {{CacheKey.key}} instead of {{QueryKey.key}}. Forum Reference: [CacheKey holds reference to entire entity instance as key?|https://forums.hibernate.org/viewtopic.php?f=1&t=1009769&sid=f0f931b...]. In our app this is resulting in what is essentially a significant memory leak, as we have a rather large and highly connected model with cache regions defined for each entity and collection. We're managing it by clearing the cache via JMX every couple days when our old gen space fills up. Of course it's not unbounded, where if we were to approximate the retained heap dominated across all the regions where this is occurring we could constrain their max entries so to keep things within available RAM. I'm attaching a minimal app modeled after the tutorial in the docs that demonstrates at least two cases: {noformat} 23:56:48,229 ERROR App:63 - CacheKey.key in region 'org.hibernate.bug.cachekey.EntityA.entityBs' isn't an Integer or Integer[], it's an: EntityA [id=1, nk1=2, nk2=3]! 23:56:48,229 ERROR App:63 - CacheKey.key in region 'org.hibernate.bug.cachekey.EntityA.entityBs' isn't an Integer or Integer[], it's an: EntityA [id=2, nk1=4, nk2=5]! 23:56:48,229 ERROR App:63 - CacheKey.key in region 'org.hibernate.bug.cachekey.EntityB' isn't an Integer or Integer[], it's an: EntityB [id1=4, id2=203, nk2=5, nk3=2003]! 23:56:48,229 ERROR App:63 - CacheKey.key in region 'org.hibernate.bug.cachekey.EntityB' isn't an Integer or Integer[], it's an: EntityB [id1=2, id2=103, nk2=3, nk3=1003]! 23:56:48,229 ERROR App:63 - CacheKey.key in region 'org.hibernate.bug.cachekey.EntityB' isn't an Integer or Integer[], it's an: EntityB [id1=2, id2=102, nk2=3, nk3=1002]! 23:56:48,230 ERROR App:63 - CacheKey.key in region 'org.hibernate.bug.cachekey.EntityB' isn't an Integer or Integer[], it's an: EntityB [id1=2, id2=101, nk2=3, nk3=1001]! 23:56:48,230 ERROR App:63 - CacheKey.key in region 'org.hibernate.bug.cachekey.EntityB' isn't an Integer or Integer[], it's an: EntityB [id1=4, id2=200, nk2=5, nk3=2000]! 23:56:48,230 ERROR App:63 - CacheKey.key in region 'org.hibernate.bug.cachekey.EntityB' isn't an Integer or Integer[], it's an: EntityB [id1=2, id2=100, nk2=3, nk3=1000]! 23:56:48,230 ERROR App:63 - CacheKey.key in region 'org.hibernate.bug.cachekey.EntityB' isn't an Integer or Integer[], it's an: EntityB [id1=4, id2=202, nk2=5, nk3=2002]! 23:56:48,230 ERROR App:63 - CacheKey.key in region 'org.hibernate.bug.cachekey.EntityB' isn't an Integer or Integer[], it's an: EntityB [id1=4, id2=201, nk2=5, nk3=2001]! {noformat} My apologies that the attached isn't a unit test, but I can't yet claim to understand how this manifests nor the internals enough to narrow it down that far. I looked briefly at {{FunctionalTestCase}} per http://hibernate.org/issuetracker, but after cloning 3.6 with Git I couldn't find any examples of its usage. Rather than get hung up I pushed ahead with the attached. Just FYI in our app we're also seeing {{EntityA}} cached as a key in its own region, as opposed to just its collection regions as above, but I haven't managed to reproduce that yet minimally. We seem to have many regions with entities in {{CacheKey.key}}, so there may be other situations that I haven't had a chance to single out yet. -- 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, 6 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5979) EntityMode.DOM4J Query mangles binary data

by Steve Mitchell (JIRA)

EntityMode.DOM4J Query mangles binary data ------------------------------------------ Key: HHH-5979 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5979 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.6.1 Environment: PostgreSQL, JSE6 Reporter: Steve Mitchell Attachments: Foo.java Using EntityMode.DOM4J to query a table with binary data (bytea), the bytes come back hex-encoded in an XML element, but with the MSB of each byte flipped. -- 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, 6 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5977) Add tests for @JoinColumn using secondary table

by Emmanuel Bernard (JIRA)

Add tests for @JoinColumn using secondary table ----------------------------------------------- Key: HHH-5977 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5977 Project: Hibernate Core Issue Type: Improvement Components: annotations Reporter: Emmanuel Bernard Priority: Minor Fix For: 3.6.2, 4.0.0.Alpha1 -- 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, 6 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HV-444) Default group sequence defined with programmatic API is not used if the configured class doesn't define programmatic constraints

by Kevin Pollet (JIRA)

Default group sequence defined with programmatic API is not used if the configured class doesn't define programmatic constraints -------------------------------------------------------------------------------------------------------------------------------- Key: HV-444 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-444 Project: Hibernate Validator Issue Type: Bug Components: engine Affects Versions: 4.2.0.Beta1 Reporter: Kevin Pollet Fix For: 4.2.0.Beta2 If constraints and default group sequence are defined with the programmatic API the following code doesn't work (no validation error) . {code} class A { String a; } class B extends A { } public interface Foo { } ConstraintMapping mapping = new ConstraintMapping(); mapping.type( B.class ) .defaultGroupSequence( Foo.class, B.class ) .type( A.class ) .property( "a", ElementType.FIELD ) .constraint( NotNullDef.class ).groups( Foo.class ); HibernateValidatorConfiguration config = Validation.byProvider( HibernateValidator.class ).configure(); ValidatorFactory factory = config.addMapping( mapping ).buildValidatorFactory(); Validator validator = factory.getValidator(); validator.validate( new B() ); {code} -- 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, 6 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HV-440) Extend programmatic API to allow the definition of default group sequence provider

by Kevin Pollet (JIRA)

Extend programmatic API to allow the definition of default group sequence provider ---------------------------------------------------------------------------------- Key: HV-440 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-440 Project: Hibernate Validator Issue Type: Task Components: engine Affects Versions: 4.2.0.Beta2 Reporter: Kevin Pollet -- 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, 6 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5975) javax.persistence.metamodel.Metamodel.managedType(Class<X> cls) does not accept embeddable classes

by Jaroslaw Lewandowski (JIRA)

javax.persistence.metamodel.Metamodel.managedType(Class<X> cls) does not accept embeddable classes -------------------------------------------------------------------------------------------------- Key: HHH-5975 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5975 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.6.0 Reporter: Jaroslaw Lewandowski Passing class annotated by @Embedable javax.persistence.metamodel.Metamodel.managedType(Class<X> cls) is causing IllegalArgumentException to be thrown. Regarding to the spec it suppose to: "Return the metamodel managed type representing the entity, mapped superclass, or embeddable class." What's interesting Metamodel.managedTypes() returns such classes. -- 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, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues March 2011