February 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-4057) Error occurs when the not-null column has a default value in the DB but the field in object has no default value.

by Rupesh Kumar (JIRA)

Error occurs when the not-null column has a default value in the DB but the field in object has no default value. ----------------------------------------------------------------------------------------------------------------- Key: HHH-4057 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4057 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.2 Environment: Hibernate 3.3.2 Reporter: Rupesh Kumar I have a column in the database which is not null and has a default value. In the Java object, I don't have any default value set on the field mapped to this column. When this object is saved, Hibernate throws up an error because it tried to insert a null value in the not-null column. Since DB can generate the value for this column, hibernate should use that. I can not use generated attribute in hibernate mapping file because this column value is not always generated. It is generated only when no value is specified for this column while inserting. Hibernate should inspect the database and find out which columns has default value set on it. If there is anything set on it, insert should ignore the mapped field if the value is not defined for it. -- 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

14 years, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-4954) Support Criteria API restriction index-refering functions for many-to-many, indexed collections

by Marius (JIRA)

Support Criteria API restriction index-refering functions for many-to-many, indexed collections ----------------------------------------------------------------------------------------------- Key: HHH-4954 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4954 Project: Hibernate Core Issue Type: Improvement Components: query-criteria Affects Versions: 3.5.0-CR-2 Reporter: Marius The problem is that the restrictions from Criteria API can't use hql functions. I have a many-to-many relation but I want to left join the other side only with the first index (0). In HQL(starting from 3.5.0-CR-2 for many-to-many relation) to get the first user's address I can write: left join user.addresses address with index(address) = '0' The generated SQL will look like this: select * from USER user left outer join USER_ADDRESS address1_ on user_.ADDRESS_ID=address1_.USER_ID and ( address1_.IDX='0' ) left outer join ADDRESS address2_ on address1_.ADDRESS_ID=address2_.ADDRESS_ID where USER_ADDRESS is the table used for many-to-many relation and IDX is the index column So I want to be able to write in Criteria like this: .createAlias("user.addresses", "address", Criteria.LEFT_JOIN, Restrictions.eq("index(address)", 0)) Or maybe Restrictions.indexEq("address", 0). Index-refering functions to implement: INDEX(), MININDEX(), MAXINDEX() -- 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

14 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (METAGEN-27) Review of documentation

by Hardy Ferentschik (JIRA)

Review of documentation ----------------------- Key: METAGEN-27 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-27 Project: Hibernate StaticMetamodel Generator Issue Type: Bug Components: documentation Affects Versions: 1.0.0-CR-1 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 1.0.0 * The copyright for the documentation should be: "Red Hat, Inc." * Check why the example numbering is not working all the time -- 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

14 years, 11 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4879) Support HQL index() function for many-to-many, indexed collections

by Steve Ebersole (JIRA)

Support HQL index() function for many-to-many, indexed collections ------------------------------------------------------------------ Key: HHH-4879 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4879 Project: Hibernate Core Issue Type: Improvement Components: core, entity-manager, query-hql Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.5.0-Next -- 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

14 years, 11 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-4951) Correct DTD entities for injecting version and date into docs

by Steve Ebersole (JIRA)

Correct DTD entities for injecting version and date into docs ------------------------------------------------------------- Key: HHH-4951 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4951 Project: Hibernate Core Issue Type: Task Components: documentation Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.5.0-CR-2 For core, these got messed up during recent translation importing. For the rest we need to move to the injecting scheme -- 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

14 years, 11 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3720) Method getSession(EntityMode) on child session does not return value provided by root session

by Michael Bezoyan (JIRA)

Method getSession(EntityMode) on child session does not return value provided by root session --------------------------------------------------------------------------------------------- Key: HHH-3720 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3720 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Reporter: Michael Bezoyan Priority: Critical Current code at line 251 in class org.hibernate.impl.SessionImpl public Session getSession(EntityMode entityMode) { if ( this.entityMode == entityMode ) { return this; } if ( rootSession != null ) { rootSession.getSession( entityMode ); } Should be: public Session getSession(EntityMode entityMode) { if ( this.entityMode == entityMode ) { return this; } if ( rootSession != null ) { return rootSession.getSession( entityMode ); } -- 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

14 years, 11 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4949) Document JPA 2 metamodel

by Steve Ebersole (JIRA)

Document JPA 2 metamodel ------------------------ Key: HHH-4949 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4949 Project: Hibernate Core Issue Type: Task Components: documentation, entity-manager, metamodel Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.5.0-CR-2 Provide documentation about the JPA 2 metamodel -- 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

14 years, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-4809) Immutable entities added to a session have Status.MANAGED unless loaded by the Session

by Gail Badner (JIRA)

Immutable entities added to a session have Status.MANAGED unless loaded by the Session -------------------------------------------------------------------------------------- Key: HHH-4809 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4809 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-Beta-3 Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.5.0-Beta-4 An immutable entity will only have Status.READ_ONLY if Hibernate loads the entity itself, e.g., Session.get(), Session.load(), s.merge(), Criteria/Query.list(), Criteria/Query.uniqueResult(). Detached and transient entities that are added to a session via Session.persist(), Session.save(), Session.saveOrUpdate() have Status.Managed. -- 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

14 years, 11 months

2
6
0 / 0

[Hibernate-JIRA] Created: (HHH-4948) Session.flush() does not always cascade save or update to read-only or immutable entities

by Gail Badner (JIRA)

Session.flush() does not always cascade save or update to read-only or immutable entities ------------------------------------------------------------------------------------------ Key: HHH-4948 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4948 Project: Hibernate Core Issue Type: Bug Components: core Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.5.0-CR-2 When the session contains only read-only or immutable entities, Session.flush() does not cascade save or update operations to these entities unless the session contains at least one entity that is mutable and not read-only. Flush should cascade the save-update operation as mapped, but save-update operations should not affect read-only or immutable entities themselves. -- 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

14 years, 11 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3817) JBC second level cache integration can cache collection data

by Brian Stansberry (JIRA)

JBC second level cache integration can cache collection data ------------------------------------------------------------ Key: HHH-3817 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3817 Project: Hibernate Core Issue Type: Bug Components: caching (L2) Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 3.3.x Scenario with two transactions dealing with a single collection: tx1 reads collection, cache miss tx1 goes to database to read collection tx2 reads collection, cache miss tx2 goes to database to read collection tx2 does JBC putForExternalRead to store empty collection tx2 updates collection tx2 removes collection from JBC (since any collection update triggers a org.hibernate.cache.Cache.evict which is implemented as a JBC removeNode) tx1 does JBC putForExternalRead to store empty collection -- STALE DATA With entities, if the db is using REPEATABLE_READ this won't be a problem, as the DB won't allow the tx2 update until tx1 commits. With a collection there is nothing to lock on. It would be a problem for entities with READ_COMMITTED as well. -- 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

14 years, 11 months

2
7
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues February 2010