May 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3277) Incorrect delete statement generation

by Moshe Elisha (JIRA)

Incorrect delete statement generation ------------------------------------- Key: HHH-3277 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3277 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.x Environment: Oracle 9.2.0.1.0 Hibernate Annotations 3.3.1.GA Hibernate 3.2.6.GA Hibernate EntityManager 3.3.2.GA Reporter: Moshe Elisha Priority: Minor I am trying to execute a delete statement on a table with a where clause that requires Hibernate to create a join. All the details can viewed here: http://forum.hibernate.org/viewtopic.php?t=986396 -- 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

16 years

2
2
0 / 0

[Hibernate-JIRA] Commented: (HBX-676) Use HQL Lexer in color coding

by Dmitry Geraskov (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-676?page=co... ] Dmitry Geraskov commented on HBX-676: ------------------------------------- Coloring works in HQLEditor now, so the issue can be closed. Or you meant other coloring? > Use HQL Lexer in color coding > ----------------------------- > > Key: HBX-676 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-676 > Project: Hibernate Tools > Issue Type: Improvement > Components: eclipse > Reporter: Max Rydahl Andersen > Fix For: 3.2LATER > > -- 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

16 years

1
0
0 / 0

[Hibernate-JIRA] Commented: (HBX-649) Alphabetize pojos in Hibernate Configuration view in Eclipse

by Dmitry Geraskov (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-649?page=co... ] Dmitry Geraskov commented on HBX-649: ------------------------------------- Not relevant as pojos are sorted by name now. The button can be added only for fields (not shure that we need this). IMHO issue can be closed. > Alphabetize pojos in Hibernate Configuration view in Eclipse > ------------------------------------------------------------ > > Key: HBX-649 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-649 > Project: Hibernate Tools > Issue Type: Improvement > Components: eclipse > Affects Versions: 3.1beta4 > Environment: Windows 2000 > Reporter: Jim Bethancourt > Priority: Trivial > > Would it be possible to alphebetize the pojos in the Hibernate Configuration view via a button (like the one available Eclipse's Outline view)? I think folks would find it handy. > Thanks, > Jim -- 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

16 years

1
0
0 / 0

[Hibernate-JIRA] Created: (HBX-1060) Configuration are not loading due to ClassNotFound exception on entities when using WTP dynamic web project

by Aymeric Levaux (JIRA)

Configuration are not loading due to ClassNotFound exception on entities when using WTP dynamic web project ----------------------------------------------------------------------------------------------------------- Key: HBX-1060 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1060 Project: Hibernate Tools Issue Type: Bug Components: eclipse Environment: Mac OS X 10.5.2, Eclipse 3.3.2, JDK 1.5.0_13 Reporter: Aymeric Levaux Attachments: HibToolTest.tgz Not able to get a working configuration due to ClassNotFoundException on the first entity in the hibernate.cfg.xml. This occur with WTP dynamic web projects. Use the simple project in attachment to reproduce. -- 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

16 years

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3272) using of Integer.valueOf(int), which is not available in JDK 1.4

by Gary Ip (JIRA)

using of Integer.valueOf(int), which is not available in JDK 1.4 ---------------------------------------------------------------- Key: HHH-3272 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3272 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.3.0.CR1 Environment: Windows XP SP2, Tomcat 5.5.26, JDK 1.4.2_17, Spring 2.5.4, Hibernate 3.3.0.CR1 Reporter: Gary Ip In class org.hibernate.jdbc.util.BasicFormatterImpl$FormatProcess line: 271: private void select() { out(); indent++; newline(); parenCounts.addLast( Integer.valueOf( parensSinceSelect ) ); afterByOrFromOrSelects.addLast( Boolean.valueOf( afterByOrSetOrFromOrSelect ) ); parensSinceSelect = 0; afterByOrSetOrFromOrSelect = true; } parensSinceSelect is a int type, while in Integer.valueOf(int) only available since JDK 1.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

16 years

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2953) Mapping DTD does not allow an idbag element inside a component element

by Adolfo Correia (JIRA)

Mapping DTD does not allow an idbag element inside a component element ---------------------------------------------------------------------- Key: HHH-2953 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2953 Project: Hibernate3 Issue Type: Bug Reporter: Adolfo Correia Priority: Minor The mapping DTD file (hibernate-mapping-3.0.dtd) currently forbids an idbag element inside a component element. I have changed the DTD file to allow idbags inside components and the mappings I made seem to work fine with Hibernate. This problem was already reported in the NHibernate Jira (http://jira.nhibernate.org/browse/NH-1044). -- 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

16 years

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2382) DefaultLoadEventListener#onLoad throws exception when DelayedPostInsertIdentifier is set as an entity id

by Eelco Hillenius (JIRA)

DefaultLoadEventListener#onLoad throws exception when DelayedPostInsertIdentifier is set as an entity id -------------------------------------------------------------------------------------------------------- Key: HHH-2382 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2382 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1, 3.2.2, 3.2.0.ga Reporter: Eelco Hillenius DefaultLoadEventListener#onLoad has this code: if ( idClass != null && ! idClass.isInstance( event.getEntityId() ) ) { throw new TypeMismatchException( "Provided id of the wrong type. Expected: " + idClass + ", got " + event.getEntityId().getClass()); } However, EntityIdentityInsertAction has this in it's constructor: delayedEntityKey = isDelayed ? generateDelayedEntityKey() : null; and method: private synchronized EntityKey generateDelayedEntityKey() { if ( !isDelayed ) { throw new AssertionFailure( "cannot request delayed entity-key for non-delayed post-insert-id generation" ); } return new EntityKey( new DelayedPostInsertIdentifier(), getPersister(), getSession().getEntityMode() ); } In case an insert is tried outside of an existing transaction users may run into this problem (like I did). I don't know what the best fix is. The easiest fix would be: Index: /Users/eelcohillenius/Documents/workspace/hibernate3/src/org/hibernate/event/def/DefaultLoadEventListener.java =================================================================== --- /Users/eelcohillenius/Documents/workspace/hibernate3/src/org/hibernate/event/def/DefaultLoadEventListener.java (revision 11098) +++ /Users/eelcohillenius/Documents/workspace/hibernate3/src/org/hibernate/event/def/DefaultLoadEventListener.java (working copy) @@ -5,6 +5,7 @@ import org.apache.commons.logging.Log; import org.apache.commons.logging.LogFactory; +import org.hibernate.EntityMode; import org.hibernate.HibernateException; import org.hibernate.LockMode; import org.hibernate.NonUniqueObjectException; @@ -10,7 +11,7 @@ import org.hibernate.NonUniqueObjectException; import org.hibernate.PersistentObjectException; import org.hibernate.TypeMismatchException; -import org.hibernate.EntityMode; +import org.hibernate.action.DelayedPostInsertIdentifier; import org.hibernate.cache.CacheConcurrencyStrategy; import org.hibernate.cache.CacheKey; import org.hibernate.cache.entry.CacheEntry; @@ -82,7 +83,7 @@ } else { Class idClass = persister.getIdentifierType().getReturnedClass(); - if ( idClass != null && ! idClass.isInstance( event.getEntityId() ) ) { + if ( idClass != null && ! (idClass.isInstance( event.getEntityId() ) || event.getEntityId() instanceof DelayedPostInsertIdentifier )) { throw new TypeMismatchException( "Provided id of the wrong type. Expected: " + idClass + ", got " + event.getEntityId().getClass() ); but that would look like a quick hack to me. -- 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

16 years

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3274) Allow <comment> sub-element to <timestamp>

by Paul Benedict (JIRA)

Allow <comment> sub-element to <timestamp> ------------------------------------------ Key: HHH-3274 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3274 Project: Hibernate3 Issue Type: Improvement Affects Versions: 3.3.0.CR1 Reporter: Paul Benedict There is currently no way to add a column comment to <timestamp>. A simple enhancement would be to add <comment> as an allowed sub-element. Our development team uses this to place the DA logical names into the 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

16 years

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-468) MysqlDialect incorrectly maps java.lang.Boolean to SQL BIT

by Laurent Mallet (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-468?page=co... ] Laurent Mallet commented on HHH-468: ------------------------------------ Hi gavin, My team is working with Seam and jboss 4.2 and discover this bug when we install our application on the pre-production plateform on our entities objects. Our pre-production and production plateforms are in RHEL 5. Our developpement plateform is on RHEL 4. The main difference is also the MySQL version. This bug is really annonying because : - RHEL 5 install version 5 of MySQL (No support on MySQL 4) - MySQL 4 is at end of his lifecycle - in JPA, it's so ugly to change our code from boolean to int - a search in google "MySQL 5 boolean BIT problem" shows so many desesperate people - credibility of jboss : this bug is so annoying that my team doesn't understand that it could be possible; they are afraid that it could have other ugly bugs.. Laurent Mallet CTO of Oxalya > MysqlDialect incorrectly maps java.lang.Boolean to SQL BIT > ---------------------------------------------------------- > > Key: HHH-468 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-468 > Project: Hibernate3 > Issue Type: Bug > Affects Versions: 3.0.3 > Environment: Hibernate 3.0, MySQL. > Reporter: Mark Matthews > Assignee: Scott Marlow > > I didn't track down how java.lang.Boolean gets mapped to Types.BIT in hibernate, but you probably _don't_ want to map to "bit" like you do in MysqlDialect. > "bit", according to SQL99 (it's not in the core standard, and the type was actually dropped for sql2k3) is a bitfield, not a boolean value. You can of course define a bit(1), but it is technically more correct for java.lang.Boolean to map to a SQL BOOLEAN for MySQL since we support a BOOLEAN and a BIT. > It looks like the JDBC-3.0 guys ignored what the standard said, because in reality you'd want BIT to map to something like byte[], or java.util.BitSet if you were tracking how the SQL standard defines BIT. > I'm guessing you probably want to map to "boolean", which the JDBC driver will automagically convert for you, as it silently maps to TINYINT(1) on the server side. -- 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

16 years

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1088) IdentifierProjection does not work with composite keys

by Paul Benedict (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1088?page=c... ] Paul Benedict commented on HHH-1088: ------------------------------------ An awesome patch. I need this for my enterprise. Our DA group uses composite keys heavily for associative entities. > IdentifierProjection does not work with composite keys > ------------------------------------------------------ > > Key: HHH-1088 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1088 > Project: Hibernate3 > Issue Type: Bug > Components: query-criteria > Affects Versions: 3.1 rc2 > Reporter: Max Muermann > Attachments: CompositeIdProjection.java, CriteriaLoader.java > > > When working with Criteria queries, the IdentifierProjection breaks if the entity has a composite key. > In IdentifierProjection.java: > public String toSqlString(Criteria criteria, int position, CriteriaQuery criteriaQuery) > throws HibernateException { > StringBuffer buf = new StringBuffer(); > String[] cols = criteriaQuery.getIdentifierColumns(criteria); > for ( int i=0; i<cols.length; i++ ) { > buf.append( cols[i] ) > .append(" as y") > .append(position + i) > .append('_'); > } > return buf.toString(); > } > This method does not add commas as separators between the column names. Easily fixed by adding > if (i<col.length-1) > buf.append(","); > as the last statement inside the loop. > However, this leads to another problem: > the type returned by IdentifierProjection.geType is the (single) type of the composite id component. The query will however return the property values of the id component without a mapping step. -- 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

16 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues May 2008