January 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-142) Modifications to objects which are indexed via @IndexedEmbedded are not triggering index updates

by Hardy Ferentschik (JIRA)

Modifications to objects which are indexed via @IndexedEmbedded are not triggering index updates ------------------------------------------------------------------------------------------------ Key: HSEARCH-142 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-142 Project: Hibernate Search Issue Type: Bug Components: engine Reporter: Hardy Ferentschik This issue was first discussed on the forum: http://forum.hibernate.org/viewtopic.php?t=981979 -- 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

17 years, 5 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HBX-1013) Hibernate giving a field (with maximum 3 characters) with lot of spaces appended to it

by Deepesh Seetharaman (JIRA)

Hibernate giving a field (with maximum 3 characters) with lot of spaces appended to it -------------------------------------------------------------------------------------- Key: HBX-1013 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1013 Project: Hibernate Tools Issue Type: Bug Affects Versions: 3.2.cr1 Environment: Hibernate 3.2.0.cr4, Oracle 9i Reporter: Deepesh Seetharaman Please refer the table structure and the hbm.xml file's content below Problem: Tempo_id is supposed to be of max-lenght 3, but hibernate gives a String with 3 characters and plenty of space appended. eg : "SLW " CREATE TABLE EDECO_TEMPO ( TEMPO_ID CHAR(3 CHAR) NOT NULL, TEMPO_NAME VARCHAR2(40 CHAR) NOT NULL, BPMRANGE VARCHAR2(40 CHAR), TEMPO_DESC VARCHAR2(2000 CHAR) ) <?xml version="1.0"?> <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD//EN" "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd" > <hibernate-mapping package="com.wcm.edeco.assetdetails.vo"> <class name="EdecoTempo" table="EDECO_TEMPO" > <meta attribute="sync-DAO">false</meta> <id name="tempoId" column="TEMPO_ID" type="java.lang.String" length="3" > <generator class="assigned"> </generator> </id> <property name="tempoName" column="TEMPO_NAME" type="java.lang.String" not-null="false" length="40" /> <property name="bpmrange" column="BPMRANGE" type="java.lang.String" not-null="false" length="40" /> <property name="tempoDesc" column="TEMPO_DESC" type="java.lang.String" not-null="false" /> </class> </hibernate-mapping> -- 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

17 years, 5 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2066) HSQL DB + multi-schema --> raised an exception (Problem to get an increment key [select max(id) from table)

by XOrangOutan (JIRA)

HSQL DB + multi-schema --> raised an exception (Problem to get an increment key [select max(id) from table) ----------------------------------------------------------------------------------------------------------- Key: HHH-2066 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2066 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr4 Environment: HSQL DB 1.8.x Reporter: XOrangOutan When trying to save an object that has an "incremental" primary key, Hibernate API tries to know what the max current id is by executing a "SELECT MAX". Though, in this particular sql query, schema name is not taken into account (in hsqldialect). This cause an error that prevents anyone from carrying out unit tests. This bug also exists on 3.x versions -- 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

17 years, 5 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-145) Document a configuration property

by John Griffin (JIRA)

Document a configuration property --------------------------------- Key: HSEARCH-145 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-145 Project: Hibernate Search Issue Type: Improvement Components: documentation Affects Versions: 3.0.0.GA Reporter: John Griffin The configuration property that allows combining different entities into the same directory is not documented. Along with this, the use of @Indexed(name= ) should be documented as an alternative way to implement this. -- 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

17 years, 5 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2781) Changes to fields marked as non-updateable written to L2 cache

by Steve Ebersole (JIRA)

Changes to fields marked as non-updateable written to L2 cache -------------------------------------------------------------- Key: HHH-2781 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2781 Project: Hibernate3 Issue Type: Bug Components: caching (L2) Reporter: Steve Ebersole Assignee: Steve Ebersole When the value a field marked as update="false" is changed, that changed state is written to the L2 cache. This occurs at least on reattachment, but I assume it also occurs for managed entities (need to verify). Viable solutions include: 1) disallow this combination (cached + non-updateable, non-generationed properties) 2) implicitly treat these properties as generated. Workaround is to mark these fields as generated. -- 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

17 years, 5 months

1
7
0 / 0

[Hibernate-JIRA] Created: (HHH-2802) Support HQL style order by (JPA @OrderBy)

by Emmanuel Bernard (JIRA)

Support HQL style order by (JPA @OrderBy) ----------------------------------------- Key: HHH-2802 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2802 Project: Hibernate3 Issue Type: New Feature Components: core Reporter: Emmanuel Bernard Fix For: 3.3 Hibernate Annotations works around the lack of ability to define Order by clause using properties rather than columns by doing the translation at configuration time. Unfortunately, this cannot take alias into account. So moving this logic to the core would make sense -- 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

17 years, 5 months

2
8
0 / 0

[Hibernate-JIRA] Created: (ANN-651) Bad SQL generated when using the @OrderBy annotation

by Eyal Lupu (JIRA)

Bad SQL generated when using the @OrderBy annotation ---------------------------------------------------- Key: ANN-651 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-651 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.0.ga Environment: Hibernate Annotations 3.3.0.GA Hibernate 3.2.5 EntityManager 3.3.1.GA Hibernate Validator 3.0.0.GA Oracle 10g Reporter: Eyal Lupu Attachments: orderBy-bug-test-case.zip When upgrading to the versions above a code which works for months now stopped working, the reason is that Hibernate generates a bad SQL statment. Attached is a test case: Having the following classes Parent / \ Child1 Child2 The parent has a property named 'elementType'. Child1 has a list of Child2 (its sibling) which is ordered using the @OrderBy("elementType") annotation. When fetching a Child1 instance, using the EntityManager.find(...) method, Hibernate generates an invalid SQL: Hibernate: /* load bug.Child1 */ select child1x0_.ID as ID0_1_, child1x0_.ELEMENT_TYPE as ELEMENT3_0_1_, elements1_.PARENT_ID as PARENT4_3_, elements1_.ID as ID3_, elements1_.ID as ID0_0_, elements1_.ELEMENT_TYPE as ELEMENT3_0_0_, elements1_.PARENT_ID as PARENT4_0_0_ from BUG_TST child1x0_ left outer join BUG_TST elements1_ on child1x0_.ID=elements1_.PARENT_ID where child1x0_.ID=? and child1x0_.DTYPE='Child1' order by BUG_TST.ELEMENT_TYPE asc The error is in the order by clause, you can't use the table name if you gave it an alias - you should use the alias. * If I move the 'elementType' property down to Child2 it works! *If I remove the @OrderBy it also works -- It is hard to know if this is an Hibernate core or Hibernate annotation bug. This is the exception: Caused by: org.hibernate.exception.SQLGrammarException: could not load an entity: [bug.Child1#1] at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:67) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.loader.Loader.loadEntity(Loader.java:1874) at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:48) at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:42) at org.hibernate.persister.entity.AbstractEntityPersister.load(AbstractEntityPersister.java:3044) at org.hibernate.event.def.DefaultLoadEventListener.loadFromDatasource(DefaultLoadEventListener.java:395) at org.hibernate.event.def.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:375) at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:139) at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:195) at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:103) at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:878) at org.hibernate.impl.SessionImpl.get(SessionImpl.java:815) at org.hibernate.impl.SessionImpl.get(SessionImpl.java:808) at org.hibernate.ejb.AbstractEntityManagerImpl.find(AbstractEntityManagerImpl.java:175) ... 1 more Caused by: java.sql.SQLException: ORA-00904: "BUG_TST"."ELEMENT_TYPE": invalid identifier at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288) at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:743) at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:216) at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:799) at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1038) at oracle.jdbc.driver.T4CPreparedStatement.executeMaybeDescribe(T4CPreparedStatement.java:839) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1133) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3285) at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3329) at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:186) at org.hibernate.loader.Loader.getResultSet(Loader.java:1787) at org.hibernate.loader.Loader.doQuery(Loader.java:674) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:236) at org.hibernate.loader.Loader.loadEntity(Loader.java:1860) ... 13 more -- Attached is a test case -- 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

17 years, 5 months

3
8
0 / 0

[Hibernate-JIRA] Created: (HHH-2281) CLONE -Calling Session.connection() generates java.lang.IllegalArgumentException: interface org.hibernate.jdbc.ConnectionWrapper is not visible from class loader

by Sergey Polzunov (JIRA)

CLONE -Calling Session.connection() generates java.lang.IllegalArgumentException: interface org.hibernate.jdbc.ConnectionWrapper is not visible from class loader ----------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-2281 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2281 Project: Hibernate3 Type: Bug Versions: 3.2.1 Environment: Hibernate checked out from trunk; revision 10717 Reporter: Sergey Polzunov Calling Session.connection() always generates an exception. Here is the stacktrace I get from the attached test case: Exception in thread "main" java.lang.IllegalArgumentException: interface org.hibernate.jdbc.ConnectionWrapper is not visible from class loader at java.lang.reflect.Proxy.getProxyClass(Proxy.java:353) at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:581) at org.hibernate.jdbc.BorrowedConnectionProxy.generateProxy(BorrowedConnectionProxy.java:56) at org.hibernate.jdbc.ConnectionManager.borrowConnection(ConnectionManager.java:163) at org.hibernate.jdbc.JDBCContext.borrowConnection(JDBCContext.java:111) at org.hibernate.impl.SessionImpl.connection(SessionImpl.java:359) at TestSession.main(TestSession.java:16) Changing the Connection.class.getClassLoader() to BorrowedConnectionProxy.class.getClassLoader() on line 57 in the generateProxy() method solves the problem. I am not very familiar with class loaders so I don't know if this is likeley to cause other problems elsewhere. Removing the ConnectionWrapper.class from the PROXY_INTERFACES array in the org.hibernate.jdbc.BorrowedConnectionProxy also solves the problem, but I guess it was added for a reason. -- 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

17 years, 5 months

11
17
0 / 0

[Hibernate-JIRA] Created: (HHH-2933) DialectFactory dialects should be in a properties file

by Mikael Kopteff (JIRA)

DialectFactory dialects should be in a properties file ------------------------------------------------------ Key: HHH-2933 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2933 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.5 Reporter: Mikael Kopteff Currently the DialectFactory has the static attribute MAPPERS, that hold the dialects. If the dialect is not found, Hibernate will throw an exception. There is already an TODO tag, set for this.So, could this be possibly done, so that the values really are a) in a properties file or b)additions could be made to the map programmaticaly by users. This would be more flexible for advanced users, that work with experimental jdbc drivers(that don't return a standard name for the database). The current trunk version of DialectFactory: // TODO : this is the stuff it'd be nice to move to a properties file or some other easily user-editable place private static final Map MAPPERS = new HashMap(); static { MAPPERS.put( "HSQL Database Engine", new VersionInsensitiveMapper( "org.hibernate.dialect.HSQLDialect" ) ); MAPPERS.put( "H2", new VersionInsensitiveMapper( "org.hibernate.dialect.H2Dialect" ) ); MAPPERS.put( "MySQL", new VersionInsensitiveMapper( "org.hibernate.dialect.MySQLDialect" ) ); etc..... -- 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

17 years, 5 months

3
23
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-77) Expose configuration settings through API

by Christian Bauer (JIRA)

Expose configuration settings through API ----------------------------------------- Key: HSEARCH-77 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-77 Project: Hibernate Search Issue Type: New Feature Components: engine Reporter: Christian Bauer Priority: Minor I'd like to access my configuration settings, probably on a SearchFactory. I want to be able to e.g. get the hibernate.search.worker.batch_size to adjust my loops dynamically. I imagine there are a few other usecases, for example, avoid hardcoding the analyzer for hit highlighting but using the same as the HSearch indexer. -- 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

17 years, 6 months

3
2
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 2008