July 2012 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-6549) ID and discrminator are nullable if a column attribute is supplied using HBM XML

by Gail Badner (JIRA)

ID and discrminator are nullable if a column attribute is supplied using HBM XML -------------------------------------------------------------------------------- Key: HHH-6549 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6549 Project: Hibernate Core Issue Type: Bug Components: metamodel Reporter: Gail Badner Assignee: Steve Ebersole Fix For: 4.0.0.next -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-6049) Improve error message about incompatible JDBC driver

by Sanne Grinovero (JIRA)

Improve error message about incompatible JDBC driver ---------------------------------------------------- Key: HHH-6049 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6049 Project: Hibernate Core Issue Type: Task Components: core Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 3.6.3 We should revert the workaround committed as part of (HHH-5642) Error configuring Hibernate with PostgreSQL JDBC3 8.2.511 driver and fail fast instead, with a good errormessage like "this jdbc driver compiled against jdk 1.3 or earlier..." -- 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, 8 months

3
9
0 / 0

[Hibernate-JIRA] Created: (HSHARDS-57) For a better "virtual shards" support!

by Colbert Philippe (JIRA)

For a better "virtual shards" support! -------------------------------------- Key: HSHARDS-57 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSHARDS-57 Project: Hibernate Shards Issue Type: Improvement Affects Versions: 3.0.0.Beta2 Environment: Windows XP Reporter: Colbert Philippe Assignee: Max Ross The current implementation of virtual shards leaves a lot to be desired when used in big corporate applications. A better way to model shards, is to identify a virtual shard by a pairing of "some name" + "an index" (example: Clients, 11). The name plays a role similar to namespaces. The index is always zero based and valid only within the namespace. There can be many shard namespaces with unique names. A configuration file (possibly XML) will map each virtual shard to a single physical shard. It's a simple mapping strategy. The mapping can allow overlaps of virtual shards into a single physical shard. This type of naming can make things more clear and easier to manage on the long-run. The big advantage to virtual shards over physical shards is that virtual shards can be easily persisted to file or database and retrieved again and still remain valid. Any change to the shard structure is fully controlled by the shard configuration file, without modifications to the persisted representation of the shard. This way the code can evolve separately from the physical shard architecture. With this kind of virtual shard, top-of-tree classes will map to a single shard namespace. The object will reside in any of the virtual shard indexes associated with the shard namespace. The resolution strategy becomes very simple because the set of shard indexes will be returned. -- 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, 8 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3464) SimpleExpression.ignoreCase uses SQL server lowercase function for left part and JAVA lowercase function for right part of expression

by Vitaliy Tymchyshyn (JIRA)

SimpleExpression.ignoreCase uses SQL server lowercase function for left part and JAVA lowercase function for right part of expression ------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-3464 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3464 Project: Hibernate3 Issue Type: Bug Components: query-criteria Affects Versions: 3.2.6 Environment: tried with PostgreSQL Reporter: Vitaliy Tymchyshyn Priority: Minor When using SimpleExpression.ignoreCase (e.g. Restrictions.eq().ignoreCase, hibernate makes 'lower(field)=?' SQL expression, passing lowercased strings to '?' parameter. This may produce unpredictable results depending on Database server lower implementation and current JAVA locale (see JDK javadoc). For example, I've tried with '\u0130' character as in JDK JavaDoc. Postgresql produces: unhappy=> select lower('İ'); lower ------- i̇ (1 row) unhappy=> select char_length(lower('İ')); char_length ------------- 2 (1 row) While Java with default locale produces single-character 'i̇'. Of course the restriction will not work - it can not find 'İ' in database. I'd recommend to use 'lower(field)=lower(?)' to use same lower casing function for both parts of expression. -- 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, 8 months

2
2
0 / 0

[Hibernate-JIRA] Created: (OGM-22) Support Session#list and JP-QL queries

by Emmanuel Bernard (JIRA)

Support Session#list and JP-QL queries -------------------------------------- Key: OGM-22 URL: http://opensource.atlassian.com/projects/hibernate/browse/OGM-22 Project: Hibernate OGM Issue Type: New Feature Components: query 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

13 years, 8 months

2
3
0 / 0

[Hibernate-JIRA] Created: (JPA-15) Criteria API based on MapKeyColumn is not working

by Edwin Dalorzo (JIRA)

Criteria API based on MapKeyColumn is not working ------------------------------------------------- Key: JPA-15 URL: http://opensource.atlassian.com/projects/hibernate/browse/JPA-15 Project: Java Persistence API Issue Type: Bug Environment: Hibernate 3.6.1 MySQL 5.0 Reporter: Edwin Dalorzo Attachments: log.txt, src.zip I defined an Employee entity having a map of phone numbers, where the key is the type of phone (home, office, mobile) and the value is the phone number as a String. @ElementCollection(fetch=FetchType.LAZY) @CollectionTable(name="emp_phone") @MapKeyColumn(name="phone_type") @Column(name="phone_num") private Map<String, String> phoneNumbers; Then I tried to write a Criteria API query using a map join, like this: CriteriaBuilder builder = entityManager.getCriteriaBuilder(); CriteriaQuery<Employee> criteria = builder.createQuery(Employee.class); Root<Employee> employeeRoot = criteria.from(Employee.class); criteria.select(employeeRoot); MapJoin<Employee, String, String> phoneRoot = employeeRoot.joinMap("phoneNumbers"); criteria.where(builder.equal(phoneRoot.key(), "HOME")); System.out.println(entityManager.createQuery(criteria).getResultList()); You get an NullPointerException java.lang.NullPointerException at org.hibernate.ejb.criteria.path.AbstractPathImpl.prepareAlias(AbstractPathImpl.java:246) at org.hibernate.ejb.criteria.path.AbstractPathImpl.render(AbstractPathImpl.java:253) at org.hibernate.ejb.criteria.predicate.ComparisonPredicate.render(ComparisonPredicate.java:173) at org.hibernate.ejb.criteria.QueryStructure.render(QueryStructure.java:258) at org.hibernate.ejb.criteria.CriteriaQueryImpl.render(CriteriaQueryImpl.java:340) at org.hibernate.ejb.criteria.CriteriaQueryCompiler.compile(CriteriaQueryCompiler.java:223) at org.hibernate.ejb.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:441) at com.dalorzo.Main.main(Main.java:57) Exception in thread "main" java.lang.RuntimeException: java.lang.NullPointerException at com.dalorzo.Main.main(Main.java:64) Caused by: java.lang.NullPointerException at org.hibernate.ejb.criteria.path.AbstractPathImpl.prepareAlias(AbstractPathImpl.java:246) at org.hibernate.ejb.criteria.path.AbstractPathImpl.render(AbstractPathImpl.java:253) at org.hibernate.ejb.criteria.predicate.ComparisonPredicate.render(ComparisonPredicate.java:173) at org.hibernate.ejb.criteria.QueryStructure.render(QueryStructure.java:258) at org.hibernate.ejb.criteria.CriteriaQueryImpl.render(CriteriaQueryImpl.java:340) at org.hibernate.ejb.criteria.CriteriaQueryCompiler.compile(CriteriaQueryCompiler.java:223) at org.hibernate.ejb.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:441) at com.dalorzo.Main.main(Main.java:57) If you change the query to filter on value instead of key, it works just fine criteria.where(builder.equal(phoneRoot.value(), "88750372")); I have attached a log with exceptions as well as the Employee entity and the Main class containing a main method. Also, the code in question runs perfectly fine in EclipseLink. -- 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, 8 months

6
8
0 / 0

[Hibernate-JIRA] (HHH-7385) upgrade to Gradle 1.0

by Strong Liu (JIRA)

13 years, 8 months

1
3
0 / 0

[Hibernate-JIRA] (HHH-7493) Documentation still refers to dom4j as an entity mode

by Gail Badner (JIRA)

13 years, 8 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-7305) NPE in LogicalConnectionImpl when multi tenancy is used without providing a release mode manually

by Christian kalkhoff (JIRA)

NPE in LogicalConnectionImpl when multi tenancy is used without providing a release mode manually ------------------------------------------------------------------------------------------------- Key: HHH-7305 URL: https://hibernate.onjira.com/browse/HHH-7305 Project: Hibernate ORM Issue Type: Bug Components: core Affects Versions: 4.1.3 Environment: cfg.setProperty(Environment.MULTI_TENANT, MultiTenancyStrategy.DATABASE.name()); Reporter: Christian kalkhoff Priority: Critical When multi tenancy is used and hibernate.connection.release_mode is not set, one gets a NPE in LogicalConnectionImpl because it accesses a (non-multi-tenancy)connection provider to determine the release mode. Stack trace: java.lang.NullPointerException at org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.determineConnectionReleaseMode(LogicalConnectionImpl.java:119) at org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.<init>(LogicalConnectionImpl.java:100) at org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.<init>(LogicalConnectionImpl.java:82) at org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.<init>(JdbcCoordinatorImpl.java:75) at org.hibernate.engine.transaction.internal.TransactionCoordinatorImpl.<init>(TransactionCoordinatorImpl.java:87) at org.hibernate.internal.SessionImpl.<init>(SessionImpl.java:249) at org.hibernate.internal.SessionFactoryImpl$SessionBuilderImpl.openSession(SessionFactoryImpl.java:1835) ... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

4
12
0 / 0

[Hibernate-JIRA] Created: (HHH-6608) @JoinColumns doesn't work inside an @Embedded member

by Joeri Hendrickx (JIRA)

@JoinColumns doesn't work inside an @Embedded member ---------------------------------------------------- Key: HHH-6608 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6608 Project: Hibernate Core Issue Type: Bug Components: annotations, metamodel Affects Versions: 4.0.0.CR1, 3.5.6 Environment: Version 3.5.6 and up, no DB Reporter: Joeri Hendrickx Attachments: hibernate-embedded-joincolumns.zip If you use multiple joincolumns on a @ManyToOne or @OneToOne field in an @Embedded class, hibernate will fail when building its metamodel with the following exception: Exception in thread "main" org.hibernate.MappingException: property [_model_MainEntity_embeddedEntity.referencedEntity] not found on entity [model.ReferencedEntity] at org.hibernate.mapping.PersistentClass.getRecursiveProperty(PersistentClass.java:379) at org.hibernate.cfg.annotations.TableBinder.bindFk(TableBinder.java:406) at org.hibernate.cfg.ToOneFkSecondPass.doSecondPass(ToOneFkSecondPass.java:111) at org.hibernate.cfg.AnnotationConfiguration.processEndOfQueue(AnnotationConfiguration.java:541) at org.hibernate.cfg.AnnotationConfiguration.processFkSecondPassInOrder(AnnotationConfiguration.java:523) at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:380) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1377) at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:954) at model.Test.main(Test.java:12) Caused by: org.hibernate.MappingException: property [_model_MainEntity_embeddedEntity.referencedEntity] not found on entity [model.ReferencedEntity] at org.hibernate.mapping.PersistentClass.getRecursiveProperty(PersistentClass.java:425) at org.hibernate.mapping.PersistentClass.getRecursiveProperty(PersistentClass.java:376) ... 8 more A test case is included. Just run model. Test with the hibernate libraries in the classpath. I get the impression this is because of the dot in the generated property name. Hibernate generates a synthetic property, named after the FQN of the owning entity (with dots replaces by underscores) appended by and underscore and the name of the property. But properties inside of embedded objects are represented with a dot; when Hibernate later tries to retrieve the same property, it incorrectly interprets this dot as a delimiter, and will look for `_model_MainEntity_embeddedEntity` (in the example above) instead; which it will not find. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

4
5
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 July 2012