January 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-5864) Begin Transaction - During Select

by VISHAL JAIN (JIRA)

Begin Transaction - During Select --------------------------------- Key: HHH-5864 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5864 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.6.0 Environment: Windows - Home Premium Reporter: VISHAL JAIN Priority: Blocker Attachments: hibernate_reference.pdf Assuming that I have to load entities - Hibernate will trigger a select statement on the underlying database. However when I try to do this as per your tutorial code, I always need to begin and commit a transaction. Don't you think this is an overhead on the underlying database and a performance overhead? EJBeans provide much cleaner way to handle these kind of scenarios. What is the support in Hibernate? -- 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
1
0 / 0

[Hibernate-JIRA] Created: (HV-420) Deprecate legacy validator

by Hardy Ferentschik (JIRA)

Deprecate legacy validator -------------------------- Key: HV-420 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-420 Project: Hibernate Validator Issue Type: Task Components: build Affects Versions: 4.2.0.Beta1 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 4.2.0.Beta2 Create a tag and delete legacy validator module -- 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
3
0 / 0

[Hibernate-JIRA] Created: (HV-424) Validators for Joda types should be specified for ReadableInstant/ReadablePartial

by Gunnar Morling (JIRA)

Validators for Joda types should be specified for ReadableInstant/ReadablePartial --------------------------------------------------------------------------------- Key: HV-424 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-424 Project: Hibernate Validator Issue Type: Improvement Components: validators Affects Versions: 4.2.0.Beta1 Reporter: Gunnar Morling Assignee: Kevin Pollet Fix For: 4.2.0.Beta2 Currently the new @Future/@Past validators for the Joda types are defined for AbstractInstant/AbstractPartial. Instead they should be defined for Joda's base interfaces ReadableInstant/ReadablePartial in order to support implementations not derived from the abstract base types. -- 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
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5863) EntityManagerFactory create EntityManger using current session

by Dave (JIRA)

EntityManagerFactory create EntityManger using current session -------------------------------------------------------------- Key: HHH-5863 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5863 Project: Hibernate Core Issue Type: Improvement Environment: ALL, Hibernate 3.6.0.FINAL Reporter: Dave In our web application we have transactions like: Begin transaction call low level API that does the following 1. getEntityManagerFactory 2. EntityManagerFactory.createEntityManager 3. entity access through entityManager do something ... call low level API that does the following 1. getEntityManagerFactory 2. EntityManagerFactory.createEntityManager 3. entity access through entityManager End transaction Within transaction boundary, current session needs to be reused for all the entity access. So an API like the following is needed. EntityManagerFactory.createEntityManager(boolean useCurrentSession) -- 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
0
0 / 0

[Hibernate-JIRA] Created: (HHH-4878) Add documentation about new "image" and "text" properties

by Gail Badner (JIRA)

Add documentation about new "image" and "text" properties --------------------------------------------------------- Key: HHH-4878 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4878 Project: Hibernate Core Issue Type: Improvement Components: documentation Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.5 -- 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
18
0 / 0

[Hibernate-JIRA] Commented: (HHH-1501) insert long string (more than 32700) fails on derby

by Gail Badner (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501?page=c... ] Gail Badner commented on HHH-1501: ---------------------------------- This can be mapped more generically by annotating properties with @Lob. Hibernate will use a "materialized_clob" type (which maps to JDBC CLOB) for the following: @Lob String longString Hibernate will use a "materialized_blob" type (which maps to JDBC BLOB) for the following: @Lob byte[] longByteArray I believe this should work for 3.5.x and 3.6.x. Or maybe I'm missing something? Please let us know if this works for Derby. Thanks, Gail > insert long string (more than 32700) fails on derby > --------------------------------------------------- > > Key: HHH-1501 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1501 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.5.0-Beta-2 > Environment: Derby 10 > Reporter: Sergey Vladimirov > Priority: Trivial > > http://issues.apache.org/jira/browse/DERBY-102 > VARCHAR maximum length 32 672 > LONG VARCHAR maximum length 32 700 > CLOB maximum length 2 147 483 647 > BLOB maximum length 2 147 483 647 > this issue can be reproduced by org.hibernate.test.lob.TextTest (in 3.5 beta1,2) with change org.hibernate.test.lob.LongStringTest.LONG_STRING_SIZE > 32700 -- 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
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5861) PersistenceUnitUtil.getIdentifier() returning zero instead of null

by Archie Cobbs (JIRA)

PersistenceUnitUtil.getIdentifier() returning zero instead of null ------------------------------------------------------------------ Key: HHH-5861 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5861 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.6.0 Reporter: Archie Cobbs Priority: Minor In one project my identifiers are Java {{long}} values and my code invoked {{PersistenceUnitUtil.getIdentifier()}} on an entity object which was either newly created and not yet persisted, or newly created and persisted but not yet actually saved (I'm not sure which case it was). But either way, the method returned the wrong thing, namely zero instead of {{null}}. According to the Persistence API, it should have returned {{null}} instead of zero: {quote} _Return the id of the entity. A generated id is not guaranteed to be available until after the database insert has occurred. Returns null if the entity does not yet have an id._ {quote} -- 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
0
0 / 0

[Hibernate-JIRA] Updated: (HHH-4362) @RowId

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4362?page=c... ] Steve Ebersole updated HHH-4362: -------------------------------- Fix Version/s: (was: 3.6.1) 4.0.0.Alpha2 > @RowId > ------ > > Key: HHH-4362 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4362 > Project: Hibernate Core > Issue Type: Improvement > Components: annotations > Reporter: Steve Ebersole > Priority: Trivial > Fix For: 4.0.0.Alpha2 > > > equivalent of <class rowid=""> -- 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
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5821) JPA EntityType's (or ManagedType's) getSingularAttributes() returns the version attribute with isVersion set to false.

by kabram (JIRA)

JPA EntityType's (or ManagedType's) getSingularAttributes() returns the version attribute with isVersion set to false. ---------------------------------------------------------------------------------------------------------------------- Key: HHH-5821 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5821 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.6.0 Reporter: kabram The version-attribute is stored in the version field of EntityTypeImpl but in the declaredSingularAttributes the SingularAttribute for the same version field has isVersion set to false. -- 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
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5681) Packaged JAR file shouldn't contain files with an absolute path

by Robert Gibson (JIRA)

Packaged JAR file shouldn't contain files with an absolute path --------------------------------------------------------------- Key: HHH-5681 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5681 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.0 Reporter: Robert Gibson hibernate-distribution-3.6.0.Final contains the following entries 0 Thu Oct 07 03:12:02 CEST 2010 / 16460 Wed Oct 13 19:49:50 CEST 2010 /hibernate-distribution-3.6.0.Final.pom Because of this, the JAR file cannot be expanded unless the user has write access to the root directory. Or if this JAR is included in a signed applet or web start application, the application will fail to start. The offending files should be removed. -- 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
9
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 January 2011