October 2010 - hibernate-issues - Jboss List Archives

[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

13 years, 6 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

13 years, 6 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

13 years, 6 months

2
6
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

13 years, 6 months

3
4
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

13 years, 6 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2989) @Loader using named queries returns null

by Jose Noheda (JIRA)

@Loader using named queries returns null ---------------------------------------- Key: HHH-2989 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2989 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.5 Environment: Hibernate 3.2.5, Hibernate Annotations 3.3.0, Hibernate Entity Manager 3.3.1 Reporter: Jose Noheda When using entitymanager.find (class, pk) with a @Loader annotation declared the org.hibernate.persister.entity.NamedQueryLoader load function performs a query.list() call (line 57). This call returns a List of entities and the list is correctly filled with one entry (org.hibernate.impl.SessionImpl line 1121). After returning, the line 62 (of NamedQueryLoader): return session.getPersistenceContext().getEntity( new EntityKey( id, persister, session.getEntityMode() ) ) is unable to find it 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

13 years, 7 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-1976) NamingStrategy.classToTableName receives only class name, not a fully qualified name as stated in javadoc

by Lóránt Pintér (JIRA)

NamingStrategy.classToTableName receives only class name, not a fully qualified name as stated in javadoc --------------------------------------------------------------------------------------------------------- Key: HHH-1976 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1976 Project: Hibernate3 Type: Bug Components: core Versions: 3.1.3, 3.2.0.cr2 Reporter: Lóránt Pintér I have a custom NamingStrategy that overrides classToTableName in EJB3NamingStrategy. Prior to upgrading to Hibernate 3.1.3, my NamingStrategy implementation received the correct classnames as documented in the javadoc at http://www.hibernate.org/hib_docs/v3/api/org/hibernate/cfg/NamingStrategy... Since then, it only receives the name of the class without the package specification. I tried upgrading to 3.2.0.cr2, but it didn't help. -- 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, 7 months

9
15
0 / 0

[Hibernate-JIRA] Created: (HHH-5428) collection tables are improperly non-quoted when the owning table is quoted

by Emmanuel Bernard (JIRA)

collection tables are improperly non-quoted when the owning table is quoted --------------------------------------------------------------------------- Key: HHH-5428 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5428 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.6.0.Beta1, 3.5.4 Reporter: Emmanuel Bernard Fix For: 3.6.0.Beta2 -- 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, 7 months

2
18
0 / 0

[Hibernate-JIRA] Created: (HHH-5352) Misleading replacement of commas with cross joins

by Patras Vlad (JIRA)

Misleading replacement of commas with cross joins ------------------------------------------------- Key: HHH-5352 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5352 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5.3, 3.5.2, 3.5.1, 3.5.0-Final, 3.5.0-CR-2, 3.5.0-CR-1, 3.5.0-Beta-4, 3.5.0-Beta-3, 3.5.0-Beta-2 Environment: Hibernate 3.5.3 Ms SQL Server 2005 Reporter: Patras Vlad There was a new feature implemented in 3.5.0-Beta-2: HHH-1480, as a result, for many dialects, the comma operator "," was replaced with "cross join". As it's already obvious from the feature's description, this changes join precedence. If the query contains outer joins (left or right) this replacement changes the results (because outer join precedence is important). This might not be interpreted as a bug if you know what SQL operator will be generated when you place a comma in HQL, but it's misleading if you don't. A HQL query like: {noformat}select a from A a, B left join B.c c{noformat} is not equivalent with the SQL query: {noformat}select a.* from A.a, B b left join C c on b.cid = c.id{noformat} because the actual SQL query is: {noformat}select a.* from A.a cross join B b left join C c on b.cid = c.id{noformat} The first SQL query would make a left join on B and C and then a cross join with the result and A (and this is what we should expect). The second SQL query makes a cross join on A and B and then a left join with the result and C (this is not expected since we had a comma in HQL). I understand the issues presented in HHH-1480, but they should be expected, i.e. a developer SHOULD expect a faliure from a query like {noformat}select a from A a, B b join a.c C{noformat} because "a" is not visible in the join. Hibernate should not use a cross join behind the scenes to allow such a query at the expense of providing misleading results for others. Maybe turn this into a feature/improvement or add another to allow explicit comma or croos join in HQL, or support parenthesis in HQL. The only workaround I can see for now is to re-order the query like this: {noformat}select a from B left join B.c c, A a{noformat} -- 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, 7 months

3
14
0 / 0

[Hibernate-JIRA] Created: (HHH-4073) discriminator formula creates problem in hibernate envers

by Saravana Kumar (JIRA)

discriminator formula creates problem in hibernate envers --------------------------------------------------------- Key: HHH-4073 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4073 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.3.x Environment: hibernate-3.3.x, envers-1.2.1.ga-hibernate-3.3.jar (Oracle 10g or HSQLDB) Reporter: Saravana Kumar I map my classes using Single Table per class hierarchy as below @Entity @DiscriminatorFormula ("(select t.c_type from t_type t where t.c_id = c_type)") @Audited public class Attribute...{ ... } or <discriminator type="string"> <formula>(select t.c_type from t_type t where t.c_id = c_type)</formula> </discriminator> When I use envers I get the follwoing error Caused by: java.lang.ClassCastException: org.hibernate.mapping.Formula at org.hibernate.envers.configuration.metadata.MetadataTools.addColumns(MetadataTools.java:154) at org.hibernate.envers.configuration.metadata.AuditMetadataGenerator.generateMappingData(AuditMetadataGenerator.java:263) at org.hibernate.envers.configuration.metadata.AuditMetadataGenerator.generateFirstPass(AuditMetadataGenerator.java:345) at org.hibernate.envers.configuration.EntitiesConfigurator.configure(EntitiesConfigurator.java:87) at org.hibernate.envers.configuration.AuditConfiguration.(AuditConfiguration.java:86) at org.hibernate.envers.configuration.AuditConfiguration.getFor(AuditConfiguration.java:99) at org.hibernate.envers.event.AuditEventListener.initialize(AuditEventListener.java:260) at org.hibernate.event.EventListeners$1.processListener(EventListeners.java:198) at org.hibernate.event.EventListeners.processListeners(EventListeners.java:181) at org.hibernate.event.EventListeners.initializeListeners(EventListeners.java:194) When I tried to debug the problem (AuditMetadataGenerator.java:263) has 260: // Checking if there is a discriminator column 261: if (hasDiscriminator) { 262: Element discriminator_element = class_mapping.addElement("discriminator"); 263: MetadataTools.addColumns(discriminator_element, pc.getDiscriminator().getColumnIterator()); 264: discriminator_element.addAttribute("type", pc.getDiscriminator().getType().getName()); 265: } (MetadataTools.java:154) has 152: public static void addColumns(Element any_mapping, Iterator<Column> columns) { 153: while (columns.hasNext()) { 154: Column column = columns.next(); 155: addColumn(any_mapping, column.getName(), column.getLength(), column.getScale(), column.getPrecision(), 156: column.getSqlType()); 157: } 158: } I see that there is nothing to handle Formula :-( Can you investigate? -- 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, 7 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues October 2010