February 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-4787) AuditProperty.isNull() doesn't generate "tab.col is null" SQL clause as expected

by Eric Citaire (JIRA)

AuditProperty.isNull() doesn't generate "tab.col is null" SQL clause as expected -------------------------------------------------------------------------------- Key: HHH-4787 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4787 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.3.0.GA Environment: Hibernate 3.3.0.GA, Envers 1.2.2, HSQLDB Database Reporter: Eric Citaire Priority: Critical AuditProperty.isNull() generate a SQL condition like this : "tab.col=?" where the bind variable is mapped to a null value. This doesn't work : most database engines will return false in every case. It should use the "is null" test instead : "tab.col is null" http://en.wikipedia.org/wiki/SQL#Null_and_Three-Valued_Logic_.283VL.29 -- 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, 2 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HV-442) Make clear in the documentation, which types are supported for built-in constraints

by Gunnar Morling (JIRA)

Make clear in the documentation, which types are supported for built-in constraints ----------------------------------------------------------------------------------- Key: HV-442 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-442 Project: Hibernate Validator Issue Type: Bug Components: documentation Affects Versions: 4.1.0.Final Reporter: Gunnar Morling Fix For: 4.2.0.CR1 Hibernate Validator supports the standard constraints defined in the Bean Validation AP at more types than required by the specification. E.g. @Min/@Max are supported for Strings, which is beyond what's defined in the spec. We should make clear in the documentation (http://docs.jboss.org/hibernate/validator/4.1/reference/en-US/html/valida...) which types are supported by HV in addition to the BV specification (for @Past/@Future we already do describe this for the Joda types for example). Furthermore the annotation processor documentation says (reference guide and web site): > Have you ever caught yourself by unintentionally doing things like > annotating Strings with @Min to specify a minimum length (instead of using @Size) > ...? > Then the Hibernate Validator Annotation Processor is the right thing for you. This example is misleading, as the AP won't mark this situation as an erronous (the described misunderstanding, that @Min would refer to the String length can still happen, though). -- 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, 2 months

2
14
0 / 0

[Hibernate-JIRA] Created: (HHH-2579) scope bytecode provider selection to session factory

by Steve Ebersole (JIRA)

scope bytecode provider selection to session factory ---------------------------------------------------- Key: HHH-2579 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2579 Project: Hibernate3 Issue Type: Improvement Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: cfg-rework currently this is one of those "static" config params (classloader wide). -- 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, 2 months

1
5
0 / 0

[Hibernate-JIRA] Created: (HHH-3574) ANY mapping ignores lazy="false"

by Manuel Dominguez Sarmiento (JIRA)

ANY mapping ignores lazy="false" -------------------------------- Key: HHH-3574 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3574 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Reporter: Manuel Dominguez Sarmiento We have a use case for eager fetching of an <any> association. The DTD accepts lazy="false|true", however at runtime it doesn't make any difference. Digging deeper, we see that org.hibernate.mapping.Any does not have a lazy property, furthermore, it does not extend Fetchable. This explains why it will not work as expected. There are two possible resolutions: 1) Implement eager fetching for <any> associations, unless there is some technical difficulty in doing so. Of course lazy fetching won't be possible using joins because of the nature of this type of associations, however it should be simple enough with a second select. This means that the XML config should handle lazy="false|true" but not fetch="join|select|subselect|etc" 2) Fix the DTD in case this can't be done to avoid confusion (less desirable). -- 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, 3 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5276) Table REVINFO created in the default schema even if the property is otherwise set

by Pascal-Eric Servais (JIRA)

Table REVINFO created in the default schema even if the property is otherwise set --------------------------------------------------------------------------------- Key: HHH-5276 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5276 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.5.2 Environment: Hibernate 3.5.2 Mysql (Ver 14.14 Distrib 5.1.37, for debian-linux-gnu (i486)) mysql-connector version 5.1.12 java version "1.6.0_0" OpenJDK Runtime Environment (IcedTea6 1.6.1) (6b16-1.6.1-3ubuntu3) OpenJDK Server VM (build 14.0-b16, mixed mode) Reporter: Pascal-Eric Servais This issue was first related here : http://community.jboss.org/message/545287 but here is a copy. Partial configuration : [META-INF/persistence.xml] <persistence version="2.0" <persistence-unit name="party" transaction-type="RESOURCE_LOCAL"> ... <properties> <property name="hibernate.hbm2ddl.auto" value="update" /> <property name="hibernate.dialect" value="org.hibernate.dialect.MySQLDialect" /> <property name="javax.persistence.jdbc.url" value="jdbc:mysql://localhost/MODEL?useUnicode=true&characterEncoding=UTF-8" /> <property name="javax.persistence.jdbc.driver" value="com.mysql.jdbc.Driver" /> <property name="javax.persistence.jdbc.user" value="root" /> <property name="javax.persistence.jdbc.password" value="" /> ... <property name="org.hibernate.envers.default_schema" value="AUDIT"/> ...  </persistence-unit> [META-INF/orm.xml] <entity-mappings xmlns="http://java.sun.com/xml/ns/persistence/orm" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence/orm http://java.sun.com/xml/ns/persistence/orm_2_0.xsd" version="2.0"> <access>FIELD</access> <entity class="com.company.model.Party"> <table name="PARTY" schema="MODEL" /> ... </entity> ... </entity-mappings> As expected, the PARTY table is created into the MODEL schema and the audit table PARTY_AUD is created into the AUDIT schema. But the REVINFO table is created into the MODEL schema. According to the property "org.hibernate.envers.default_schema", it should be created into the AUDIT schema. -- 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, 3 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2484) Introduce NamingStrategy.getDefaultEntityName(String className)

by Emmanuel Bernard (JIRA)

Introduce NamingStrategy.getDefaultEntityName(String className) --------------------------------------------------------------- Key: HHH-2484 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2484 Project: Hibernate3 Type: Improvement Components: core Reporter: Emmanuel Bernard Assigned to: Emmanuel Bernard Priority: Minor Fix For: 3.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, 3 months

2
6
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-661) Improve documentation around query dsl options like ignoreAnalyzer and ignoreFieldBridge

by Hardy Ferentschik (JIRA)

Improve documentation around query dsl options like ignoreAnalyzer and ignoreFieldBridge ---------------------------------------------------------------------------------------- Key: HSEARCH-661 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-661 Project: Hibernate Search Issue Type: Improvement Components: documentation Affects Versions: 3.3.0.Final Reporter: Hardy Ferentschik Fix For: 3.4.0 The _Query Options_ section mentioned that these options exist, but does not explain why they are needed in some cases and what happens per default when _onField(s)()_ is used. See also forum thread - https://forum.hibernate.org/viewtopic.php?f=9&t=1008943 -- 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, 3 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3008) Cascade delete does not work with unidirectional @OneToMany and @JoinTable

by Daniel Dyer (JIRA)

Cascade delete does not work with unidirectional @OneToMany and @JoinTable -------------------------------------------------------------------------- Key: HHH-3008 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3008 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.5 Environment: Standalone entity manager (JavaSE 5.0). H2 database. Reporter: Daniel Dyer A unidirectional one-to-many relationship defined as follows: public class Owner { @OneToMany(cascade = CascadeType.ALL) @JoinTable(name = "owner_element", joinColumns = @JoinColumn(name = "owner_id", nullable = false, updatable = false), inverseJoinColumns = @JoinColumn(name = "element_id", nullable = false, updatable = false)) private List<Element> elements; // ... } Attempting to delete an instance of Owner should also delete all associated instances of Element. Instead I get the following error: SEVERE: Referential integrity constraint violation: FK56BBF9C487E817D: PUBLIC.OWNER_ELEMENT FOREIGN KEY(OWNER_ID) REFERENCES PUBLIC.OWNER(ID) [23003-63] This is because Hibernate attempts to delete the Owner row without first removing the rows from the join table. -- 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, 3 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5914) Remove deprecated Hibernate type constants from org.hibernate.Hibernate and manuals

by Gail Badner (JIRA)

Remove deprecated Hibernate type constants from org.hibernate.Hibernate and manuals ----------------------------------------------------------------------------------- Key: HHH-5914 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5914 Project: Hibernate Core Issue Type: Improvement Components: core, documentation Reporter: Gail Badner Fix For: 4.0.0.Alpha3 Remove deprecated Hibernate type constants from org.hibernate.Hibernate and manuals. Manuals should refer to constants in org.hibernate.type.StandardBasicTypes instead. -- 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, 3 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4722) Proxy initialization should be fail-fast when accidentially initializing from event listeners or interceptor

by Joonas Koivunen (JIRA)

Proxy initialization should be fail-fast when accidentially initializing from event listeners or interceptor ------------------------------------------------------------------------------------------------------------ Key: HHH-4722 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4722 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.2 Environment: Hibernate 3.2.2 Reporter: Joonas Koivunen Proxy initialization done in event listeners (at least post-update) with an entity that has a mapped collection seems to result in {code}org.hibernate.AssertionFailure: collection [role-of-collection] was not processed by flush(){code} at flush time. By googling up problems like the above assertion failure seems that other people than me have spent quite a time searching for the origin of this problem; for me it was using a toString() of an uninitialized proxy. -- 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, 3 months

2
1
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 February 2011