April 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HCANN-19) Issue with @Column( ) annotation

by Prakash G (JIRA)

Issue with @Column( ) annotation -------------------------------- Key: HCANN-19 URL: http://opensource.atlassian.com/projects/hibernate/browse/HCANN-19 Project: Hibernate Commons Annotations Issue Type: Bug Reporter: Prakash G We all know that when we don't map a attribute with column in the DB using @Column() annotation, hibernate by default splits the variable based on the words and constructs the column name to be mapped. Example if I have something like private BigDecimal netLiqPercent; then hibernate constructs the column name as net_liq_percent. But when we use @Column(name ="Account_NetLiq_Percent", nullable=true, updatable=true, insertable=true) private BigDecimal netLiqPercent; Hibernate should not try to resolve / construct column, instead it should use whatever the column name is being specified. However its not so! In the above case hibernate tries to look for column "account_net_liq_percent" and gives unknown column exception. I believe when we explicitly map the column hibernate should use it. but it works if I change column name to all CAPS..! I think this needs to be addressed. -- 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, 3 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5120) LazyGroup Loading Mechanism

by Demidovich Artem (JIRA)

LazyGroup Loading Mechanism --------------------------- Key: HHH-5120 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5120 Project: Hibernate Core Issue Type: Improvement Components: core Environment: Hibernate Reporter: Demidovich Artem Priority: Minor I would like to suggest a new functionality, which could improve Lazy loading. For Example, I have bussines objects and there is an object named Company. Company has many fields, but I can separate Company fields in two or three logical groups and those fields of the object can be groupped in LazyGroups (for example "LazyGroup1", "LazyGroup2"). Now if caller tries to get some field from the LazyGroup1 then Nibernate will load all fields from this group. Just for example Company Type LazyGroup 1. Name (string) 2. Postal Code (string) 3. Address (Address Object) 4. Wokers (Lazy Collection) 5. Contracts (Lazy Collection) (LazyGroup = 'LG1') 6. Clients (Lazy Collection) (LazyGroup = 'LG1') 7. BussinesInfo (string) (LazyGroup = 'LG2') 8. BussinesRegions (Lazy Collection) (LazyGroup = 'LG2') 8. BussinesPartners (Lazy Collection) (LazyGroup = 'LG2') So, if I call BussinesInfo getter then Hibernate should load all fields in 'LG2' LazyGroup (BussinussInfo, BussinessRegions, BussinesPartners). This improvement will descrease amount of sql queries, because hibernate will use one query for loading all fields from the lazy group rather than calling one query per field. -- 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, 3 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5119) LazyInitializationException on OneToMany relationship if relation is not on Primary Key

by Simon Martinelli (JIRA)

LazyInitializationException on OneToMany relationship if relation is not on Primary Key --------------------------------------------------------------------------------------- Key: HHH-5119 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5119 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5.0-Final Environment: Hibernate 3.5.0-Final with Derby DB and Oracle 10g Reporter: Simon Martinelli Attachments: JPA2_M2M.tar.gz I created two entities One and Two. One has a OneToMany relationship to Two. @OneToMany @JoinColumn(insertable = false, updatable = false, name = "SCHLUESSEL", referencedColumnName = "SCHLUESSEL") private List<Two> twos = new ArrayList<Two>(); Important notice: SCHLUESSEL is not the primary key of Two! I have the following test code: List<One> ones = em.createQuery("select o from One o").getResultList(); for (One one : ones) { logger.info(one.getName()); //em.refresh(one); for (Two two : one.getTwos()) { logger.info(two.getText()); } } When I run a test and try to access "twos" I get an excpetion: 2002 [main] ERROR org.hibernate.LazyInitializationException - failed to lazily initialize a collection of role: ch.test.One.twos, no session or session was closed org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: ch.test.One.twos, no session or session was closed at org.hibernate.collection.AbstractPersistentCollection.throwLazyInitializationException(AbstractPersistentCollection.java:380) at org.hibernate.collection.AbstractPersistentCollection.throwLazyInitializationExceptionIfNotConnected(AbstractPersistentCollection.java:372) After uncommenting em.refresh it works. -- 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, 3 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5113) Regression in org.hibernate.criterion.PropertyProjection compared to 3.5.0-CR-2

by thogau (JIRA)

Regression in org.hibernate.criterion.PropertyProjection compared to 3.5.0-CR-2 ------------------------------------------------------------------------------- Key: HHH-5113 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5113 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-Final Environment: mysql 5 Reporter: thogau When applying a projection to a criteria query, the SQL generated is something like : {code}SELECT DISTINCT y0_ AS y0_, y1_ AS y1_ FROM history this_ ORDER BY y1_ ASC{code} while it was correctly generated in 3.5.0-CR-2 as : {code}SELECT DISTINCT this_.id AS y0_, this_.attribute AS y1_ FROM history this_ ORDER BY y1_ ASC{code} I guess there was an autocompletion mistake in line 65 of PropertyProjection.java, the line should be : {code}String[] cols = criteriaQuery.getColumns( criteria, propertyName );{code} cheers, --Thomas -- 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, 3 months

2
5
0 / 0

[Hibernate-JIRA] Updated: (HHH-1496) A new dialect is required for MySQL NDB clustered table types

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1496?page=c... ] Steve Ebersole updated HHH-1496: -------------------------------- Fix Version/s: (was: 3.5.1) 3.5.x > A new dialect is required for MySQL NDB clustered table types > ------------------------------------------------------------- > > Key: HHH-1496 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1496 > Project: Hibernate Core > Issue Type: Improvement > Components: core > Affects Versions: 3.1.2 > Reporter: Darran Lofthouse > Assignee: Juraci Paixao Krohling > Fix For: 3.5.x > > Attachments: HHH-1496.diff > > > A new dialect is required for MySQL NDB clustered table types > http://dev.mysql.com/doc/refman/5.0/en/create-table.html > Either ENGINE=NDB or ENGINE=NDBCLUSTER > Also FYI ENGINE is the prefered way of specifying the type over TYPE so MySQLMyISAMDialect and MySQLInnoDBDialect could also be updated to use ENGINE -- 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, 3 months

1
0
0 / 0

[Hibernate-JIRA] Updated: (HHH-1851) relax special handling of 'id' property

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1851?page=c... ] Steve Ebersole updated HHH-1851: -------------------------------- Fix Version/s: (was: 3.5.1) 3.5.x > relax special handling of 'id' property > --------------------------------------- > > Key: HHH-1851 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1851 > Project: Hibernate Core > Issue Type: Improvement > Components: query-hql > Environment: independent, all versions all databases. > Reporter: Gunther Schadow > Assignee: Steve Ebersole > Fix For: 3.5.x > > Attachments: IdClassAndAnotherPropertyNamedId.zip > > > Hibernate has long treated 'id' in a special manner in HQL and Criteria queries. The drawback to this has always been that it effectively means users cannot define non-identifier properties named id and refer to those properties in HQL/Criteria queries. > Thus, I will change this such that: > (1) 'id' can still be used to refer to the identifier property, whatever the property's actual name, as long as the entity does not define a non-identitifer property named id. > (2) if the entity defines a non-identifier property named 'id', using 'id' in HQL or Criteria queries will refer to this non-identifier property; users would need to refer to the identifier property by its actual name. > FYI, the original reason for this feature was to support entity's which did not define an identifier property at all (users were responsible for managing the ids seperately. That feature was never really recommended and has been deprecated since early in the 3.x development. -- 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, 3 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-4965) Bug in org.hibernate.ejb.QueryImpl

by jean-claude cote (JIRA)

Bug in org.hibernate.ejb.QueryImpl ---------------------------------- Key: HHH-4965 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4965 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.5.0-CR-1 Reporter: jean-claude cote Priority: Minor Emmanuel There seems to be a bug in the QueryImpl class in the method extractParameterInfo() Here's what I've done: I create an equal predicate using a Path to House.address and a Address value. @Entity class House { @Type(type="jc.AddressUserType") @Columns(columns={@Column(name="address")}) Address address; In the extractParameterInfo() method there is a loop that gets the javaType from a namedParameterTypeRedefinition. It gets the javaType (Address.class) then since it is not null tries to find the hibernate Type using the TypeFactory.heuristicType() method. But given a javaType this will only work for strings, int, double etc. What is passed in is an Address not an AddressUserType. The huristicType actually returns an hibernate SerializableType and resets the descriptor which was correct in the first place. I've fix this for myself my just commenting out the call to resetExpectedType but there must be a good reason why this call is made there correct? Thanks Jean-Claude @SuppressWarnings({ "unchecked", "RedundantCast" }) private void extractParameterInfo(Map<String,Class> namedParameterTypeRedefinition) { if ( ! AbstractQueryImpl.class.isInstance( query ) ) { throw new IllegalStateException( "Unknown query type for parameter extraction" ); } HashSet<Parameter<?>> parameters = new HashSet<Parameter<?>>(); AbstractQueryImpl queryImpl = AbstractQueryImpl.class.cast( query ); // extract named params for ( String name : (Set<String>) queryImpl.getParameterMetadata().getNamedParameterNames() ) { final NamedParameterDescriptor descriptor = queryImpl.getParameterMetadata().getNamedParameterDescriptor( name ); Class javaType = namedParameterTypeRedefinition.get( name ); if ( javaType != null ) { descriptor.resetExpectedType( TypeFactory.heuristicType( javaType.getName() ) ); } else if ( descriptor.getExpectedType() != null ) { javaType = descriptor.getExpectedType().getReturnedClass(); } final ParameterImpl parameter = new ParameterImpl( name, javaType ); parameters.add( parameter ); if ( descriptor.isJpaStyle() ) { if ( jpaPositionalIndices == null ) { jpaPositionalIndices = new HashSet<Integer>(); } jpaPositionalIndices.add( Integer.valueOf( name ) ); } } -- 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, 3 months

4
12
0 / 0

[Hibernate-JIRA] Created: (HHH-5108) CriteriaQuery: Support equals(pathToManyToOne, entity) on entities

by Emmanuel Bernard (JIRA)

CriteriaQuery: Support equals(pathToManyToOne, entity) on entities ------------------------------------------------------------------ Key: HHH-5108 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5108 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.5.0-Final Reporter: Emmanuel Bernard I wonder if such a support is expected by the spec and if no, are we willing to support 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

16 years, 3 months

2
6
0 / 0

[Hibernate-JIRA] Created: (HHH-5059) callouts and programlistings with highlighting

by Steve Ebersole (JIRA)

callouts and programlistings with highlighting ---------------------------------------------- Key: HHH-5059 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5059 Project: Hibernate Core Issue Type: Bug Components: documentation Reporter: Steve Ebersole Assignee: Steve Ebersole Priority: Blocker Fix For: 3.5.x Attempting to use callouts with programlistings that apply highlighting break horrifically :( Actually it seems to be ok for pdf; still need to investigate more. However it for certain goes horribly wrong on html formats. We need to fix this and push a 3.5.1 asap to have proper 3.5 documentation available. The problem is that this is an issue with the "JBoss.org jDocBook styles". And the fix is not yet known nor expected to be trivial. So how long so we wait? Because the work around is to remove the highlighting when using callouts; in other words, for all <programlistingco> tags, we need to make sure the nested <programlisting> tags do not specify the role attribute. Then when (if ever) the "JBoss.org jDocBook styles" is fixed we will need to go and add back the highlighting. -- 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, 3 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-5116) REmove copyrighted fonts from annotations

by Emmanuel Bernard (JIRA)

REmove copyrighted fonts from annotations ----------------------------------------- Key: HHH-5116 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5116 Project: Hibernate Core Issue Type: Task Components: annotations Affects Versions: 3.5.0-Final Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard Fix For: 3.5.1 -- 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, 3 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-488) Nested use of @ContainedIn: changes not propagated to Lucene index

by Pieter van den Brink (JIRA)

Nested use of @ContainedIn: changes not propagated to Lucene index ------------------------------------------------------------------ Key: HSEARCH-488 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-488 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.1.1.GA Environment: Hibernate-core 3.3.2.GA PostgreSQL 8.4.2, testcase reproduced in hsqldb 1.8.0.7 Reporter: Pieter van den Brink Attachments: TestNestedContainedIn.zip I'm having trouble getting Hibernate Search to automatically update the Lucene index for entities which are @ContainedIn an entity, which is again @ContainedIn another entity. The class structure in this example is as follows: There are HelpItems and Tags, which are linked many-to-many via another entity HelpItemTag. The HelpItem is the only @Indexed entity, it embeds all tags via @IndexedEmbedded. If an indexed (@Field) property of Tag changes, the change is not propagated to the Lucene index. See the discussion at https://forum.hibernate.org/viewtopic.php?f=9&t=1003637 for a complete description. I have added a standalone testcase that reproduces the issue. As you can see in the the first testcase, the Tag name is indexed properly as part of the HelpItem, but the second testcase fails because the changed Tag name is not update in the Lucene index. -- 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, 3 months

2
6
0 / 0

[Hibernate-JIRA] Created: (HHH-5104) EntityType.isEqual() test x equals x but should test x equals y

by Thierry-Dimitri Roy (JIRA)

EntityType.isEqual() test x equals x but should test x equals y --------------------------------------------------------------- Key: HHH-5104 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5104 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5.0-Final Reporter: Thierry-Dimitri Roy Line 338 change yid = persister.getIdentifier(x, entityMode); to yid = persister.getIdentifier(y, 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

16 years, 3 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-5083) Align javadoc styles better with docbook / website

by Steve Ebersole (JIRA)

Align javadoc styles better with docbook / website -------------------------------------------------- Key: HHH-5083 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5083 Project: Hibernate Core Issue Type: Task Components: documentation Affects Versions: 3.5.0-Final Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.5.x -- 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, 3 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5084) Improve overview for aggregated javadocs

by Steve Ebersole (JIRA)

Improve overview for aggregated javadocs ---------------------------------------- Key: HHH-5084 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5084 Project: Hibernate Core Issue Type: Task Components: documentation Affects Versions: 3.5.0-Final Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.5.x The current overview was very "hibernate-core"-specific. We should mention entitymanager and annotations at least. Additionally, the groups were very "hibernate-core"-specific. We should apply groups for annotations, entity-manager and envers as best as possible. -- 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, 3 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-4077) Misuse of NamingStrategy and logical column names in HbmBinder

by Emmanuel Bernard (JIRA)

Misuse of NamingStrategy and logical column names in HbmBinder -------------------------------------------------------------- Key: HHH-4077 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4077 Project: Hibernate Core Issue Type: Bug Components: metamodel Affects Versions: 3.3.2 Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard 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

16 years, 3 months

3
10
0 / 0

[Hibernate-JIRA] Created: (HHH-5096) FetchingScrollableResultsImpl.last() does not move to the last result if cursor is after the last result

by Gail Badner (JIRA)

FetchingScrollableResultsImpl.last() does not move to the last result if cursor is after the last result --------------------------------------------------------------------------------------------------------- Key: HHH-5096 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5096 Project: Hibernate Core Issue Type: Bug Components: query-hql Affects Versions: 3.5.0-Final, 3.3.2 Reporter: Gail Badner Assignee: Gail Badner Priority: Minor Fix For: 3.3.x, 3.5.x FetchingScrollableResultsImpl.last() does not move to the last result if cursor is after the last result. Instead, it says after the last result. -- 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, 3 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5102) Instances of a subclass can't be loaded

by Saša Obradović (JIRA)

Instances of a subclass can't be loaded --------------------------------------- Key: HHH-5102 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5102 Project: Hibernate Core Issue Type: Bug Components: annotations, core, entity-manager Affects Versions: 3.5.0-Final Environment: Hibernate 3.5.0-Final, Oracle Reporter: Saša Obradović Priority: Blocker Attachments: acount.jpg, columnnotfoundbug.zip, oracle.sql For a simple class hierarchy (strategy: joined, using @MappedSuperclass) an instance can't be loaded from the database using the superclass as type: {{Account account = entityManager.find(Account.class, 404L);}} This works fine in any Hibernate version prior to the latest and is an obvious bug in 3.5.0-Final. {quote} javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: could not load an entity: [hibernatebug.Account#404] at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1179) at org.hibernate.ejb.AbstractEntityManagerImpl.find(AbstractEntityManagerImpl.java:575) at org.hibernate.ejb.AbstractEntityManagerImpl.find(AbstractEntityManagerImpl.java:529) at org.springframework.orm.jpa.ExtendedEntityManagerCreator$ExtendedEntityManagerInvocationHandler.invoke(ExtendedEntityManagerCreator.java:365) at $Proxy90.find(Unknown Source) at org.springframework.orm.jpa.SharedEntityManagerCreator$SharedEntityManagerInvocationHandler.invoke(SharedEntityManagerCreator.java:240) at $Proxy90.find(Unknown Source) at at.ing.diba.service.architektur.BugTest.getSavingsAccount_aroundBody2(BugTest.java:40) at at.ing.diba.service.architektur.BugTest$AjcClosure3.run(BugTest.java:1) at at.ing.diba.manager.ServiceMethodTracingAspect.traceServiceMethod(ServiceMethodTracingAspect.java:40) at at.ing.diba.service.architektur.BugTest.getSavingsAccount(BugTest.java:40) at org.springframework.test.context.testng.AbstractTestNGSpringContextTests.run(AbstractTestNGSpringContextTests.java:158) Caused by: org.hibernate.exception.GenericJDBCException: could not load an entity: [hibernatebug.Account#404] at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:140) at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:128) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66) at org.hibernate.loader.Loader.loadEntity(Loader.java:1937) at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:86) at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:76) at org.hibernate.persister.entity.AbstractEntityPersister.load(AbstractEntityPersister.java:3270) at org.hibernate.event.def.DefaultLoadEventListener.loadFromDatasource(DefaultLoadEventListener.java:496) at org.hibernate.event.def.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:477) at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:227) at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:285) at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:152) at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:1080) at org.hibernate.impl.SessionImpl.get(SessionImpl.java:997) at org.hibernate.impl.SessionImpl.get(SessionImpl.java:990) at org.hibernate.ejb.AbstractEntityManagerImpl.find(AbstractEntityManagerImpl.java:554) ... 47 more Caused by: java.sql.SQLException: Ungültiger Spaltenname at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112) at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146) at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:208) at oracle.jdbc.driver.OracleStatement.getColumnIndex(OracleStatement.java:3296) at oracle.jdbc.driver.OracleResultSetImpl.findColumn(OracleResultSetImpl.java:1914) at oracle.jdbc.driver.OracleResultSet.getBigDecimal(OracleResultSet.java:2042) at org.hibernate.type.BigDecimalType.get(BigDecimalType.java:46) at org.hibernate.type.NullableType.nullSafeGet(NullableType.java:184) at org.hibernate.type.NullableType.nullSafeGet(NullableType.java:173) at org.hibernate.type.AbstractType.hydrate(AbstractType.java:105) at org.hibernate.persister.entity.AbstractEntityPersister.hydrate(AbstractEntityPersister.java:2267) at org.hibernate.loader.Loader.loadFromResultSet(Loader.java:1423) at org.hibernate.loader.Loader.instanceNotYetLoaded(Loader.java:1351) at org.hibernate.loader.Loader.getRow(Loader.java:1251) at org.hibernate.loader.Loader.getRowFromResultSet(Loader.java:619) at org.hibernate.loader.Loader.doQuery(Loader.java:745) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:270) at org.hibernate.loader.Loader.loadEntity(Loader.java:1933) ... 59 more {quote} (''Ungültiger Spaltenname'' means: column not found) The generated SQL-Statements are different: 3.5.0-Final: {quote} /* load hibernatebug.Account */ select account0_.ACC_ID as ACC1_30_0_, account0_.ACC_IBAN as ACC2_30_0_, account0_.ACC_VERSION as ACC3_30_0_, case when account0_1_.SAVACC_ACC_ID is not null then 1 when account0_.ACC_ID is not null then 0 end as clazz_0_ from ACCOUNT account0_ left outer join SAVINGS_ACCOUNT account0_1_ on account0_.ACC_ID=account0_1_.SAVACC_ACC_ID where account0_.ACC_ID=? {quote} 3.3.2.GA: {quote} /* load hibernatebug.Account */ select account0_.ACC_ID as ACC1_36_0_, account0_.ACC_IBAN as ACC2_36_0_, account0_.ACC_VERSION as ACC3_36_0_, account0_1_.SAVACC_WITHDRAWALLIMIT as SAVACC1_44_0_, case when account0_1_.SAVACC_ACC_ID is not null then 1 when account0_.ACC_ID is not null then 0 end as clazz_0_ from ACCOUNT account0_ left outer join SAVINGS_ACCOUNT account0_1_ on account0_.ACC_ID=account0_1_.SAVACC_ACC_ID where account0_.ACC_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

16 years, 3 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-5106) Getting UnsupportedOperationException("not yet implemented for SQL queries") for Named Native queries

by Zuber Saiyed (JIRA)

Getting UnsupportedOperationException("not yet implemented for SQL queries") for Named Native queries ----------------------------------------------------------------------------------------------------- Key: HHH-5106 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5106 Project: Hibernate Core Issue Type: Bug Reporter: Zuber Saiyed I want to bring following to your attention that in org.hibernate.ejb.AbstractEntityManagerImpl method createNamedQuery: org.hibernate.Query namedQuery = getSession().getNamedQuery( name ); // instance of SQLQueryImpl being returned for native query try { // As SQLQueryImpl's getReturnTypes() method throws UnsupportedOperationException, named native queries are not working in Core 3.5-Final if ( namedQuery.getReturnTypes().length != 1 ) { throw new IllegalArgumentException( "Cannot create TypedQuery for query with more than one return" ); } -- 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, 3 months

2
6
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-406) Removing cyclic reference between JMSBackendProcessor and JMSBackendProcessorFactory

by Amin Mohammed-Coleman (JIRA)

Removing cyclic reference between JMSBackendProcessor and JMSBackendProcessorFactory ------------------------------------------------------------------------------------ Key: HSEARCH-406 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-406 Project: Hibernate Search Issue Type: Improvement Components: engine Affects Versions: 3.1.1.GA Environment: Mac OS 10.6 Reporter: Amin Mohammed-Coleman Priority: Minor Attachments: JMS.patch The patch provided removes the cyclic reference between JMSBackendProcessor and JMSBackendProcessorFactory. The patch also includes: 1) Validation in the initialize method of JMSBackendProcessorFactory to check whether connection factory and queue property is included 2) Created a JMSBackendProcessorParameter which encapsulates all the necessary info for JMSBackendProcessor 3) Updated JMSBackendProcessor to include transacted parameter -- 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, 3 months

3
11
0 / 0

[Hibernate-JIRA] Created: (HHH-5103) Specifying the referencedColumnName in a @JoinColumn in backtics like `uid` fails

by Samuel Mendenhall (JIRA)

Specifying the referencedColumnName in a @JoinColumn in backtics like `uid` fails ---------------------------------------------------------------------------------- Key: HHH-5103 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5103 Project: Hibernate Core Issue Type: Bug Components: annotations Affects Versions: 3.2.4.sp1 Environment: EAP 4.3 with Hibernate commons annotations 3.0.0.GA and Hibernate core 3.2.4.sp1.cp09 Reporter: Samuel Mendenhall Priority: Minor Given a column with a defined name in backtics like so @Id @GeneratedValue @Column(name = "`uid`") private long userid; A @JoinTable/@JoinColumn mapping fails if specifically referencing the backtic name, instead one must leave off the backtics so the discovery can happen based on the pk. This fails: @JoinTable(name = "SYS_GROUPS_USERS", joinColumns = @JoinColumn(name = "USERID", referencedColumnName = "`uid`"), inverseJoinColumns = @JoinColumn(name = "GROUPID", referencedColumnName = "GROUPID")) While this works: @ManyToMany(fetch = FetchType.LAZY) @JoinTable(name = "SYS_GROUPS_USERS", joinColumns = @JoinColumn(name = "USERID"), inverseJoinColumns = @JoinColumn(name = "GROUPID")) The exception is Caused by: org.hibernate.AnnotationException: Column name uid of org.domain.seam202.entity.SysUserOrm not found in JoinColumns.referencedColumnName at org.hibernate.cfg.annotations.TableBinder.bindFk(TableBinder.java:321) at org.hibernate.cfg.annotations.CollectionBinder.bindCollectionSecondPass(CollectionBinder.java:1322) at org.hibernate.cfg.annotations.CollectionBinder.bindManyToManySecondPass(CollectionBinder.java:1161) at org.hibernate.cfg.annotations.CollectionBinder.bindStarToManySecondPass(CollectionBinder.java:600) at org.hibernate.cfg.annotations.CollectionBinder$1.secondPass(CollectionBinder.java:541) at org.hibernate.cfg.CollectionSecondPass.doSecondPass(CollectionSecondPass.java:43) at org.hibernate.cfg.Configuration.secondPassCompile(Configuration.java:1136) at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:323) at org.hibernate.cfg.Configuration.buildMappings(Configuration.java:1121) at org.hibernate.ejb.Ejb3Configuration.buildMappings(Ejb3Configuration.java:1225) at org.hibernate.ejb.EventListenerConfigurator.configure(EventListenerConfigurator.java:159) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:854) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:191) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:253) -- 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, 3 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5107) Fetched by fetch-profile results are lost outside of the session

by Elif Kurklu (JIRA)

Fetched by fetch-profile results are lost outside of the session ---------------------------------------------------------------- Key: HHH-5107 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5107 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-Final Environment: [junit] 0 [main] INFO org.hibernate.cfg.Environment - Hibernate 3.5.0-Final [junit] 0 [main] INFO org.hibernate.cfg.Environment - hibernate.properties not found [junit] 16 [main] INFO org.hibernate.cfg.Environment - Bytecode provider name : javassist [junit] 16 [main] INFO org.hibernate.cfg.Environment - using JDK 1.4 java.sql.Timestamp handling [junit] 78 [main] INFO org.hibernate.cfg.Configuration - configuring from url: file:/C:/Elif/Develop/ConFRM-Server/config/hibernate.hsqldb-cfg.xml [junit] 125 [main] INFO org.hibernate.cfg.Configuration - Reading mappings from resource : hibernate-mappings/Authentication.hbm.xml [junit] 203 [main] INFO org.hibernate.cfg.HbmBinder - Mapping class: gov.nasa.arc.confrm.authentication.User -> CONFRM_USER [junit] 219 [main] INFO org.hibernate.cfg.HbmBinder - Mapping collection: gov.nasa.arc.confrm.authentication.User.roles -> CONFRM_USER_ROLES [junit] 219 [main] INFO org.hibernate.cfg.HbmBinder - Mapping class: gov.nasa.arc.confrm.authentication.UserRole -> USER_ROLE [junit] 219 [main] INFO org.hibernate.cfg.Configuration - Reading mappings from resource : hibernate-mappings/Constraint.hbm.xml [junit] 234 [main] INFO org.hibernate.cfg.HbmBinder - Mapping class: gov.nasa.arc.confrm.constraint.ConstraintType -> CONSTRAINT_TYPE [junit] 234 [main] INFO org.hibernate.cfg.HbmBinder - Mapping class: gov.nasa.arc.confrm.constraint.ConstraintStatus -> CONSTRAINT_STATUS [junit] 250 [main] INFO org.hibernate.cfg.HbmBinder - Mapping class: gov.nasa.arc.confrm.constraint.Constraint -> CONSTRAINT [junit] 344 [main] INFO org.hibernate.cfg.HbmBinder - Mapping class: gov.nasa.arc.confrm.constraint.SourceRecord -> SOURCE_RECORD [junit] 344 [main] INFO org.hibernate.cfg.HbmBinder - Mapping class: gov.nasa.arc.confrm.constraint.CommentThread -> COMMENT_THREAD [junit] 344 [main] INFO org.hibernate.cfg.HbmBinder - Mapping class: gov.nasa.arc.confrm.constraint.Comment -> COMMENT [junit] 344 [main] INFO org.hibernate.cfg.Configuration - Configured SessionFactory: null [junit] 344 [main] INFO org.hibernate.cfg.HbmBinder - Mapping collection: gov.nasa.arc.confrm.constraint.Constraint.commentThreads -> COMMENT_THREAD [junit] 344 [main] INFO org.hibernate.cfg.HbmBinder - Mapping collection: gov.nasa.arc.confrm.constraint.CommentThread.comments -> COMMENT [junit] 344 [main] INFO org.hibernate.cfg.HbmBinder - Mapping collection: gov.nasa.arc.confrm.constraint.Comment.responses -> COMMENT [junit] 1266 INFO [main] org.springframework.orm.hibernate3.LocalSessionFactoryBean - Building new Hibernate SessionFactory [junit] 344 [main] INFO org.hibernate.connection.DriverManagerConnectionProvider - Using Hibernate built-in connection pool (not for production use!) [junit] 344 [main] INFO org.hibernate.connection.DriverManagerConnectionProvider - Hibernate connection pool size: 1 [junit] 344 [main] INFO org.hibernate.connection.DriverManagerConnectionProvider - autocommit mode: false [junit] 344 [main] INFO org.hibernate.connection.DriverManagerConnectionProvider - using driver: org.hsqldb.jdbcDriver at URL: jdbc:hsqldb:hsql://localhost/confrm [junit] 344 [main] INFO org.hibernate.connection.DriverManagerConnectionProvider - connection properties: {user=sa, password=****} [junit] 375 [main] INFO org.hibernate.cfg.SettingsFactory - RDBMS: HSQL Database Engine, version: 1.8.0 [junit] 375 [main] INFO org.hibernate.cfg.SettingsFactory - JDBC driver: HSQL Database Engine Driver, version: 1.8.0 [junit] 391 [main] INFO org.hibernate.dialect.Dialect - Using dialect: org.hibernate.dialect.HSQLDialect [junit] 406 [main] INFO org.hibernate.engine.jdbc.JdbcSupportLoader - Disabling contextual LOB creation as JDBC driver reported JDBC version [3] less than 4 [junit] 406 [main] INFO org.hibernate.transaction.TransactionFactoryFactory - Transaction strategy: org.springframework.orm.hibernate3.SpringTransactionFactory [junit] 406 [main] INFO org.hibernate.transaction.TransactionManagerLookupFactory - No TransactionManagerLookup configured (in JTA environment, use of read-write or transactional second-level cache is not recommended) [junit] 406 [main] INFO org.hibernate.cfg.SettingsFactory - Automatic flush during beforeCompletion(): disabled [junit] 406 [main] INFO org.hibernate.cfg.SettingsFactory - Automatic session close at end of transaction: disabled [junit] 406 [main] INFO org.hibernate.cfg.SettingsFactory - JDBC batch size: 15 [junit] 406 [main] INFO org.hibernate.cfg.SettingsFactory - JDBC batch updates for versioned data: disabled [junit] 406 [main] INFO org.hibernate.cfg.SettingsFactory - Scrollable result sets: enabled [junit] 406 [main] INFO org.hibernate.cfg.SettingsFactory - JDBC3 getGeneratedKeys(): disabled [junit] 406 [main] INFO org.hibernate.cfg.SettingsFactory - Connection release mode: auto [junit] 406 [main] INFO org.hibernate.cfg.SettingsFactory - Default batch fetch size: 1 [junit] 406 [main] INFO org.hibernate.cfg.SettingsFactory - Generate SQL with comments: disabled [junit] 406 [main] INFO org.hibernate.cfg.SettingsFactory - Order SQL updates by primary key: disabled [junit] 406 [main] INFO org.hibernate.cfg.SettingsFactory - Order SQL inserts for batching: disabled [junit] 406 [main] INFO org.hibernate.cfg.SettingsFactory - Query translator: org.hibernate.hql.ast.ASTQueryTranslatorFactory [junit] 406 [main] INFO org.hibernate.hql.ast.ASTQueryTranslatorFactory - Using ASTQueryTranslatorFactory [junit] 406 [main] INFO org.hibernate.cfg.SettingsFactory - Query language substitutions: {} [junit] 406 [main] INFO org.hibernate.cfg.SettingsFactory - JPA-QL strict compliance: disabled [junit] 406 [main] INFO org.hibernate.cfg.SettingsFactory - Second-level cache: enabled [junit] 406 [main] INFO org.hibernate.cfg.SettingsFactory - Query cache: disabled [junit] 406 [main] INFO org.hibernate.cfg.SettingsFactory - Cache region factory : org.hibernate.cache.impl.NoCachingRegionFactory [junit] 406 [main] INFO org.hibernate.cfg.SettingsFactory - Optimize cache for minimal puts: disabled [junit] 406 [main] INFO org.hibernate.cfg.SettingsFactory - Structured second-level cache entries: disabled [junit] 406 [main] INFO org.hibernate.cfg.SettingsFactory - Echoing all SQL to stdout [junit] 406 [main] INFO org.hibernate.cfg.SettingsFactory - Statistics: disabled [junit] 406 [main] INFO org.hibernate.cfg.SettingsFactory - Deleted entity synthetic identifier rollback: disabled [junit] 406 [main] INFO org.hibernate.cfg.SettingsFactory - Default entity-mode: pojo [junit] 406 [main] INFO org.hibernate.cfg.SettingsFactory - Named query checking : enabled [junit] 406 [main] INFO org.hibernate.cfg.SettingsFactory - Check Nullability in Core (should be disabled when Bean Validation is on): enabled [junit] 438 [main] INFO org.hibernate.impl.SessionFactoryImpl - building session factory [junit] > orderByFragment(order-by) [junit] > sortSpecification({sort specification}) [junit] > sortKeySpecification(sort key) [junit] > sortKey($PlaceHolder$.addedOn) [junit] < sortKey(null) [junit] < sortKeySpecification(null) [junit] < sortSpecification(null) [junit] < orderByFragment(null) [junit] > orderByFragment(order-by) [junit] > sortSpecification({sort specification}) [junit] > sortKeySpecification(sort key) [junit] > sortKey($PlaceHolder$.addedOn) [junit] < sortKey(null) [junit] < sortKeySpecification(null) [junit] < sortSpecification(null) [junit] < orderByFragment(null) [junit] > orderByFragment(order-by) [junit] > sortSpecification({sort specification}) [junit] > sortKeySpecification(sort key) [junit] > sortKey($PlaceHolder$.addedOn) [junit] < sortKey(null) [junit] < sortKeySpecification(null) [junit] < sortSpecification(null) [junit] < orderByFragment(null) [junit] 625 [main] INFO org.hibernate.impl.SessionFactoryObjectFactory - Not binding factory to JNDI, no JNDI name configured [junit] 2063 INFO [main] org.springframework.jdbc.datasource.DriverManagerDataSource - Loaded JDBC driver: org.hsqldb.jdbcDriver [junit] 2110 INFO [main] org.springframework.security.access.intercept.aopalliance.MethodSecurityInterceptor - Validated configuration attributes [junit] 2141 INFO [main] org.springframework.security.provisioning.JdbcUserDetailsManager - No authentication manager set. Reauthentication of users when changing passwords will not be performed. [junit] 1266 [main] INFO org.hibernate.validator.util.Version - Hibernate Validator 4.0.2.GA Reporter: Elif Kurklu Created a fetch-profile on a lazy collection, and used it in server code. I can see the SQL statement running with proper join to load the collection objects. Yet, when I try to access the collection outside the session, I still get LazyInitializationException. The data is fetched already, why is it dropped in favor of lazy loading? I thought this was a great alternative to using Hibernate.initialize(). I would love it to work that way! code with fetch profile: public T load(PK id, String fetchProfile) { Session s = getSession(); s.enableFetchProfile(fetchProfile); T o = (T) s.load(type, id); return o; } mapping file: <class name="Constraint" table="CONSTRAINT"> <id name="id" type="int" access="field"><generator class="native"/></id> <property name="number" type="string" not-null="true"/> <property name="name" type="string" not-null="true"/> <property name="versionName" type="string" not-null="true"/> <set name="commentThreads" inverse="true" order-by="addedOn" lazy="true" cascade="all,delete-orphan" access="field"> <key column="constraint_id"/> <one-to-many class="CommentThread"/> </set> <fetch-profile name="constraint-fetch"> <fetch association="commentThreads" style="join"/> </fetch-profile> </class> -- 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, 3 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5105) NamingHelper writes credential information to the log

by Yiming Du (JIRA)

NamingHelper writes credential information to the log ----------------------------------------------------- Key: HHH-5105 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5105 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.2.6 Reporter: Yiming Du In certain situations, the class NamingHelper will write credential information to the log. To be more specific, in the method getInitialContext() of the class org.hibernate.util.NamingHelper, there're following 2 lines Hashtable hash = getJndiProperties(props); log.info("JNDI InitialContext properties:" + hash); This will result in the clear text of the credential information in the conditions that the credential properties are set and the log level is lower than INFO. In our case, we have to set the "hibernate.jndi.java.naming.security.principal" and "hibernate.jndi.java.naming.security.credentials" properties in order to register the SessionFactory to the JNDI tree on Websphere if Websphere is security enabled (Another thread https://forum.hibernate.org/viewtopic.php?f=1&t=931740&start=0 gives some description about this situation as well). Although it's harmless to functionalities, it undermines to some degree the overall security. -- 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, 3 months

1
0
0 / 0

[Hibernate-JIRA] Resolved: (HHH-1804) Empty 'FetchingScrollableResultsImpl' throws SQLException

by Gail Badner (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1804?page=c... ] Gail Badner resolved HHH-1804. ------------------------------ Resolution: Fixed Fixed in trunk and Branch_3_3. I believe the attached patch will not work properly for some queries. Instead, I added a check for an empty ResultSet to FetchingScrollableResultsImpl.next(). You can see details at http://opensource.atlassian.com/projects/hibernate/browse/HHH-1804?page=c... when JIRA syncs up the commit. > Empty 'FetchingScrollableResultsImpl' throws SQLException > --------------------------------------------------------- > > Key: HHH-1804 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1804 > Project: Hibernate Core > Issue Type: Bug > Reporter: Maarten Winkels > Assignee: Gail Badner > Attachments: EmptyFetchJoinScrollTest.java, scroll-join-fetch-empty.patch > > > When scrolling a HQL query with join fetch on a collection, that doesn't return any results, the following execption occurs: > org.hibernate.exception.GenericJDBCException: could not perform sequential read of results (forward) > at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:103) > at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:91) > at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) > at org.hibernate.loader.Loader.loadSequentialRowsForward(Loader.java:386) > at org.hibernate.impl.FetchingScrollableResultsImpl.next(FetchingScrollableResultsImpl.java:55) > at org.hibernate.test.joinfetch.EmptyFetchJoinScrollTest.testFetchJoinEmptyScroll(EmptyFetchJoinScrollTest.java:21) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at junit.framework.TestCase.runTest(TestCase.java:154) > at org.hibernate.test.TestCase.runTest(TestCase.java:161) > at junit.framework.TestCase.runBare(TestCase.java:127) > at junit.framework.TestResult$1.protect(TestResult.java:106) > at junit.framework.TestResult.runProtected(TestResult.java:124) > at junit.framework.TestResult.run(TestResult.java:109) > at junit.framework.TestCase.run(TestCase.java:118) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:478) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:344) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) > Caused by: java.sql.SQLException: No data is available > at org.hsqldb.jdbc.Util.sqlException(Unknown Source) > at org.hsqldb.jdbc.Util.sqlException(Unknown Source) > at org.hsqldb.jdbc.jdbcResultSet.checkAvailable(Unknown Source) > at org.hsqldb.jdbc.jdbcResultSet.getColumnInType(Unknown Source) > at org.hsqldb.jdbc.jdbcResultSet.getString(Unknown Source) > at org.hsqldb.jdbc.jdbcResultSet.getString(Unknown Source) > at org.hibernate.type.StringType.get(StringType.java:18) > at org.hibernate.type.NullableType.nullSafeGet(NullableType.java:113) > at org.hibernate.type.NullableType.nullSafeGet(NullableType.java:102) > at org.hibernate.loader.Loader.getKeyFromResultSet(Loader.java:1088) > at org.hibernate.loader.Loader.loadSequentialRowsForward(Loader.java:375) > ... 18 more -- 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, 3 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-491) Make some optional dependencies mandatory

by Emmanuel Bernard (JIRA)

Make some optional dependencies mandatory ----------------------------------------- Key: HSEARCH-491 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-491 Project: Hibernate Search Issue Type: Improvement Components: build, documentation Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard Fix For: 3.2.0.CR1 Need to change the pom, the artifact and the documentation (esp the getting started one). -- 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, 3 months

3
10
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-468) Refactor build to have a module setup

by Hardy Ferentschik (JIRA)

Refactor build to have a module setup ------------------------------------- Key: HSEARCH-468 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-468 Project: Hibernate Search Issue Type: Task Components: build Affects Versions: 3.2.0.Beta1 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 3.2.0.Beta2 Right now I can see the following modules * core * testing * archetype Later on we can add modules for * infinispan and maybe other directory provider It would be nice to simplify the dependencies by getting rid of the profiles w/ and w/o optional dependencies. -- 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, 3 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-320) Hibernate Search conflicts with Spring's class path scanning

by Paul Middelkoop (JIRA)

Hibernate Search conflicts with Spring's class path scanning ------------------------------------------------------------ Key: HSEARCH-320 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-320 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.1.0.GA, 3.1.0.CR1 Reporter: Paul Middelkoop Hibernate Search conflicts with Spring's class path scanning. When Hibernate Search is on the classpath Spring throws an exception while reading annotation metadata. 3.1.0 Beta1 and 3.0.x versions had no problems. Stacktrace: Caused by: java.lang.ArrayIndexOutOfBoundsException: 50432 at org.springframework.asm.ClassReader.readUTF8(Unknown Source) at org.springframework.asm.ClassReader.accept(Unknown Source) at org.springframework.asm.ClassReader.accept(Unknown Source) at org.springframework.core.type.classreading.SimpleMetadataReader.getAnnotationMetadata(SimpleMetadataReader.java:55) at org.springframework.core.type.filter.AnnotationTypeFilter.matchSelf(AnnotationTypeFilter.java:68) at org.springframework.core.type.filter.AbstractTypeHierarchyTraversingFilter.match(AbstractTypeHierarchyTraversingFilter.java:55) at org.springframework.context.annotation.ClassPathScanningCandidateComponentProvider.isCandidateComponent(ClassPathScanningCandidateComponentProvider.java:224) at org.springframework.context.annotation.ClassPathScanningCandidateComponentProvider.findCandidateComponents(ClassPathScanningCandidateComponentProvider.java:182) at org.springframework.context.annotation.ClassPathBeanDefinitionScanner.doScan(ClassPathBeanDefinitionScanner.java:201) at org.springframework.context.annotation.ComponentScanBeanDefinitionParser.parse(ComponentScanBeanDefinitionParser.java:85) at org.springframework.beans.factory.xml.NamespaceHandlerSupport.parse(NamespaceHandlerSupport.java:69) at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1255) at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1245) at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:135) at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:92) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:507) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:398) -- 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, 3 months

5
18
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-277) Adding Lucene Score

by Ulrich Vachon (JIRA)

Adding Lucene Score ------------------- Key: HSEARCH-277 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-277 Project: Hibernate Search Issue Type: Improvement Reporter: Ulrich Vachon Priority: Minor Hello, Is it plans to add implicitly the score to bean via an annotation for example? In my bean, if I have a annoted property or method like : @Score private float score; HS will inject the score result after the query in my bean. Thank you, Ulrich -- 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, 3 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-4864) "Cannot read files twice on NativeScanner" exception when using multiple persistence.xml

by Bouiaw (JIRA)

"Cannot read files twice on NativeScanner" exception when using multiple persistence.xml ---------------------------------------------------------------------------------------- Key: HHH-4864 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4864 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-Beta-3 Reporter: Bouiaw When subclassing DefaultPersistenceUnitManager as described in http://ancientprogramming.blogspot.com/2007/05/multiple-persistencexml-fi... in order to have my entities in different jars, Hibernate 3.5-Beta3 throw the following exception (it worked with previous version of Hibernate) : java.lang.RuntimeException: error trying to scan <jar-file>: file:/Users/bouiaw/resthub/resthub-core/target/classes/ at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:700) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:465) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:165) at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.createNativeEntityManagerFactory(LocalContainerEntityManagerFactoryBean.java:225) at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.afterPropertiesSet(AbstractEntityManagerFactoryBean.java:288) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1457) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1397) ... 51 more Caused by: org.hibernate.AssertionFailure: Cannot read files twice on NativeScanner at org.hibernate.ejb.packaging.NativeScanner.getFilesInJar(NativeScanner.java:168) at org.hibernate.ejb.Ejb3Configuration.addScannedEntries(Ejb3Configuration.java:393) at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:697) ... 57 more -- 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, 3 months

5
7
0 / 0

[Hibernate-JIRA] Deleted: (HHH-5100) test

by John Slota (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5100?page=c... ] John Slota deleted HHH-5100: ---------------------------- > test > ---- > > Key: HHH-5100 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5100 > Project: Hibernate Core > Issue Type: New Feature > Reporter: John Slota > Priority: Trivial > -- 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, 3 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5100) test

by John Slota (JIRA)

test ---- Key: HHH-5100 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5100 Project: Hibernate Core Issue Type: New Feature Reporter: John Slota Priority: Trivial -- 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, 3 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-505) JGroupsMasterTest uses native SQL failing on DB2 and sybase

by Sanne Grinovero (JIRA)

JGroupsMasterTest uses native SQL failing on DB2 and sybase ----------------------------------------------------------- Key: HSEARCH-505 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-505 Project: Hibernate Search Issue Type: Bug Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Trivial Fix For: 3.2.0.CR1 -- 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, 3 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-494) Fix hudson failures

by Sanne Grinovero (JIRA)

Fix hudson failures ------------------- Key: HSEARCH-494 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-494 Project: Hibernate Search Issue Type: Task Reporter: Sanne Grinovero Fix For: 3.2.0.CR1 -- 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, 3 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3543) method org.hibernate.transaction.JDBCTransaction.notifyLocalSynchsBeforeTransactionCompletion "swallows" all exceptions occured inside it

by Roman (JIRA)

method org.hibernate.transaction.JDBCTransaction.notifyLocalSynchsBeforeTransactionCompletion "swallows" all exceptions occured inside it ----------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-3543 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3543 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: MS Windows XP SP2, JDK 1.6.8, Eclipse 3.2.0 Reporter: Roman When using JBoss Envers any exceptions occured during saving data into version tables are swallowed by code block in class org.hibernate.transaction.JDBCTransaction (line 273): try { sync.beforeCompletion(); } catch (Throwable t) { log.error("exception calling user Synchronization", t); } Thereby, any exceptions occured in sync.beforeCompletion() will only be shown in log, but will not have any effect on application functionality So I have such behaviour: 1. Entity changes are saved in database by hibernate 2. Version tables for entities are empty, because, for example, of invalid column names 3. Transaction commits successfully. -- 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, 3 months

5
7
0 / 0

[Hibernate-JIRA] Created: (HHH-2809) dialect changes: limit string

by Anthony Patricio (JIRA)

dialect changes: limit string ----------------------------- Key: HHH-2809 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2809 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.3 Reporter: Anthony Patricio Attachments: IngresDialect.svndiff32 In Ingres we use "SELECT FIRST $n col1,... FROM ..." to limit the resultset. The old dialect replaces the first 6 chars of the select statement with "SELECT FIRST $n". When running our partner application, hibernate has put 2 or 3 blanks at the begining of the query, which causes an error, of course. Patch attached -- 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, 3 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-497) sybase15 Hudson configuration fails because of java.net.ConnectException: Connection refused

by Sanne Grinovero (JIRA)

sybase15 Hudson configuration fails because of java.net.ConnectException: Connection refused -------------------------------------------------------------------------------------------- Key: HSEARCH-497 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-497 Project: Hibernate Search Issue Type: Sub-task Reporter: Sanne Grinovero Assignee: Emmanuel Bernard -- 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, 3 months

4
5
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-496) Some hudson configurations need more time to run the testsuite

by Sanne Grinovero (JIRA)

Some hudson configurations need more time to run the testsuite -------------------------------------------------------------- Key: HSEARCH-496 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-496 Project: Hibernate Search Issue Type: Sub-task Reporter: Sanne Grinovero Assignee: Emmanuel Bernard -- 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, 3 months

4
21
0 / 0

[Hibernate-JIRA] Created: (HHH-3962) Ingres Hibernate dialect for EAP 4.3.0 GA CP04

by Enrico Schenk (JIRA)

Ingres Hibernate dialect for EAP 4.3.0 GA CP04 ---------------------------------------------- Key: HHH-3962 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3962 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.2.4.sp1 Environment: Hibernate Core 3.2.4.SP1 CP07, Ingres 9.2.0 Reporter: Enrico Schenk Priority: Minor Attachments: IngresDialect.java This is the Ingres dialect that was used for the EAP 4.3.0 GA CP04 tests. It's based on the latest dialect from the trunk contains changes for the functions current_time, current_timestamp and current_date. The dialect also overrides the method getForUpdateString() to disable the use of "SELECT...FOR UPDATE" statements. -- 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, 3 months

5
10
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-501) Make use of BeforeTransactionCompletionProcess and AfterTransactionCompletionProcess instead of Synchronization

by Emmanuel Bernard (JIRA)

Make use of BeforeTransactionCompletionProcess and AfterTransactionCompletionProcess instead of Synchronization --------------------------------------------------------------------------------------------------------------- Key: HSEARCH-501 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-501 Project: Hibernate Search Issue Type: Improvement Components: engine Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard Fix For: 3.2.0.CR1 -- 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, 3 months

2
8
0 / 0

[Hibernate-JIRA] Updated: (HHH-1804) Empty 'FetchingScrollableResultsImpl' throws SQLException

by Gail Badner (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1804?page=c... ] Gail Badner updated HHH-1804: ----------------------------- Issue Type: Bug (was: Patch) > Empty 'FetchingScrollableResultsImpl' throws SQLException > --------------------------------------------------------- > > Key: HHH-1804 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1804 > Project: Hibernate Core > Issue Type: Bug > Reporter: Maarten Winkels > Assignee: Gail Badner > Attachments: EmptyFetchJoinScrollTest.java, scroll-join-fetch-empty.patch > > > When scrolling a HQL query with join fetch on a collection, that doesn't return any results, the following execption occurs: > org.hibernate.exception.GenericJDBCException: could not perform sequential read of results (forward) > at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:103) > at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:91) > at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) > at org.hibernate.loader.Loader.loadSequentialRowsForward(Loader.java:386) > at org.hibernate.impl.FetchingScrollableResultsImpl.next(FetchingScrollableResultsImpl.java:55) > at org.hibernate.test.joinfetch.EmptyFetchJoinScrollTest.testFetchJoinEmptyScroll(EmptyFetchJoinScrollTest.java:21) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at junit.framework.TestCase.runTest(TestCase.java:154) > at org.hibernate.test.TestCase.runTest(TestCase.java:161) > at junit.framework.TestCase.runBare(TestCase.java:127) > at junit.framework.TestResult$1.protect(TestResult.java:106) > at junit.framework.TestResult.runProtected(TestResult.java:124) > at junit.framework.TestResult.run(TestResult.java:109) > at junit.framework.TestCase.run(TestCase.java:118) > at junit.framework.TestSuite.runTest(TestSuite.java:208) > at junit.framework.TestSuite.run(TestSuite.java:203) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:478) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:344) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) > Caused by: java.sql.SQLException: No data is available > at org.hsqldb.jdbc.Util.sqlException(Unknown Source) > at org.hsqldb.jdbc.Util.sqlException(Unknown Source) > at org.hsqldb.jdbc.jdbcResultSet.checkAvailable(Unknown Source) > at org.hsqldb.jdbc.jdbcResultSet.getColumnInType(Unknown Source) > at org.hsqldb.jdbc.jdbcResultSet.getString(Unknown Source) > at org.hsqldb.jdbc.jdbcResultSet.getString(Unknown Source) > at org.hibernate.type.StringType.get(StringType.java:18) > at org.hibernate.type.NullableType.nullSafeGet(NullableType.java:113) > at org.hibernate.type.NullableType.nullSafeGet(NullableType.java:102) > at org.hibernate.loader.Loader.getKeyFromResultSet(Loader.java:1088) > at org.hibernate.loader.Loader.loadSequentialRowsForward(Loader.java:375) > ... 18 more -- 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, 3 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-502) update MassIndexer to use new core features

by Sanne Grinovero (JIRA)

update MassIndexer to use new core features ------------------------------------------- Key: HSEARCH-502 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-502 Project: Hibernate Search Issue Type: Improvement Affects Versions: 3.2.0.Beta1 Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Minor Fix For: 3.2.0.CR1 {code}session.setDefaultReadOnly( true );{code} and converting Lock to LockOptions -- 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, 3 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-490) MassIndexer needs to use distinct on primary key selection

by Sanne Grinovero (JIRA)

MassIndexer needs to use distinct on primary key selection ---------------------------------------------------------- Key: HSEARCH-490 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-490 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.2.0.Beta1 Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 3.2.0.Beta2 org.hibernate.search.batchindexing.IdentifierProducer should make sure to select the primary keys using a DISTINCT -- 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, 3 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4938) Multiple errors reported during legacy FooBarTest with Ingres

by Ray Fan (JIRA)

Multiple errors reported during legacy FooBarTest with Ingres ------------------------------------------------------------- Key: HHH-4938 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4938 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-Beta-4 Environment: 3.5.0-Beta-4, Ingres 9.3.1 Reporter: Ray Fan Attachments: IngresAmbiguousColumnTest.java, legacy.zip During test org.hibernate.test.legacy.FooBarTest multiple tests fail with ambiguous column defined in the select list. {noformat} <error message="could not initialize a collection: [org.hibernate.test.legacy.Abstract.abstracts#ff80808126e244920126e246eeb10001]" type="org.hibernate.exception.GenericJDBCException">org.hibernate.exception.GenericJDBCException: could not initialize a collection: [org.hibernate.test.legacy.Abstract.abstracts#ff80808126e244920126e246eeb10001] at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:132) at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:120) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66) at org.hibernate.loader.Loader.loadCollection(Loader.java:2048) at org.hibernate.loader.collection.BatchingCollectionInitializer.initialize(BatchingCollectionInitializer.java:86) at org.hibernate.persister.collection.AbstractCollectionPersister.initialize(AbstractCollectionPersister.java:628) at org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:83) at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1853) at org.hibernate.collection.AbstractPersistentCollection.forceInitialization(AbstractPersistentCollection.java:476) at org.hibernate.engine.StatefulPersistenceContext.initializeNonLazyCollections(StatefulPersistenceContext.java:899) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:276) at org.hibernate.loader.Loader.loadEntity(Loader.java:1907) at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:71) at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:65) at org.hibernate.persister.entity.AbstractEntityPersister.load(AbstractEntityPersister.java:3212) at org.hibernate.event.def.DefaultLoadEventListener.loadFromDatasource(DefaultLoadEventListener.java:496) at org.hibernate.event.def.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:477) at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:227) at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:285) at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:152) at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:1080) at org.hibernate.impl.SessionImpl.get(SessionImpl.java:997) at org.hibernate.event.def.DefaultMergeEventListener.entityIsDetached(DefaultMergeEventListener.java:386) at org.hibernate.event.def.DefaultMergeEventListener.onMerge(DefaultMergeEventListener.java:234) at org.hibernate.event.def.DefaultMergeEventListener.onMerge(DefaultMergeEventListener.java:84) at org.hibernate.impl.SessionImpl.fireSaveOrUpdateCopy(SessionImpl.java:914) at org.hibernate.impl.SessionImpl.saveOrUpdateCopy(SessionImpl.java:878) at org.hibernate.impl.SessionImpl.saveOrUpdateCopy(SessionImpl.java:882) at org.hibernate.test.legacy.FooBarTest.testSaveOrUpdateCopyAny(FooBarTest.java:126) Caused by: com.ingres.gcf.util.SqlEx: line 1, Column 'str' found in more than one FROM list table. at com.ingres.gcf.jdbc.DrvObj.readError(Unknown Source) at com.ingres.gcf.jdbc.DrvObj.readResults(Unknown Source) at com.ingres.gcf.jdbc.DrvPrep.prepare(Unknown Source) at com.ingres.gcf.jdbc.DrvConn.createPrepStmt(Unknown Source) at com.ingres.gcf.jdbc.JdbcPrep.<init>(Unknown Source) at com.ingres.gcf.jdbc.JdbcConn.createPrep(Unknown Source) at com.ingres.gcf.jdbc.JdbcConn.prepareStatement(Unknown Source) at org.hibernate.jdbc.AbstractBatcher.getPreparedStatement(AbstractBatcher.java:534) {noformat} The generate SQL query select list contains multiple columns named 'str'. -- 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, 3 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5089) not-null integrity must be checked for DML statements and not for objects

by Markus Bohr (JIRA)

not-null integrity must be checked for DML statements and not for objects ------------------------------------------------------------------------- Key: HHH-5089 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5089 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: Windows XP Eclipse 3.5.1 Teneo 1.0.3 Reporter: Markus Bohr This issue somehow relates to HHH-4057 but is of much broader scope and pointing out a different aspect. Currently Hibernate checks the not-null constraint integrity persisting any object already on the object level (which is a quite early point in time; for loading objects, this might cause analoguous problems). The not-null XML attribute, however, is part of the <column> tag and therefore is assumed to match the characteristics of a column and not a mapped object property! I am facing severe problems with the current behaviour, as the not-null check is performed even before any nullSafePut() method is executed for a customized Hibernate type, or even before any the any PreInsertEventListener / PreUpdateEventListener has a chance to transform null-values for properties to non-null values for database columns. Effectively, the flexibility to handle different nullability characteristics between columns and their mapped properties is thus reduced to zero. -- 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, 3 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-386) In a Transaction, Delete on unindexed entities referenced by indexed entities with ContainedIn throw LazyInitializationException

by Grégoire Rolland (JIRA)

In a Transaction, Delete on unindexed entities referenced by indexed entities with ContainedIn throw LazyInitializationException -------------------------------------------------------------------------------------------------------------------------------- Key: HSEARCH-386 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-386 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.1.1.GA, 3.1.0.GA Environment: Hibernate 3.3.1.GA, PostgreSQL 8.3 Reporter: Grégoire Rolland Priority: Critical Attachments: hsearch.tar.gz Delete on unindexed entities referenced by indexed entities with ContainedIn annotation failed. On PostCommit Transaction, I get a LazyInitializationException on the collection with the ContainedIn annotation. I upload a test case to reproduce this, run the Boot class. 1/ Entity2 is not lacking @DocumentId, I read the doc again and again (my english is very poor, but ...) : "In fact since the 3.1.0 release of Hibernate Search @DocumentId is optional in the case where an @Id annotation exists." 2/ Entity2 is not lacking @IndexedEmbedded, see the "entity1" association. 3/ From Hibernate Entity Manager Doc : "In an EXTENDED persistence context, all read only operations of the entity manager can be executed outside a transaction (find(), getReference(), refresh(), and read queries). Some modifications operations can be executed outside a transaction, but they are queued until the persistence context join a transaction. This is the case of persist(), merge(), remove(). Some operations cannot be called outside a transaction: flush(), lock(), and update/delete queries.". This is the case of the attached test. I attach a second testcase with all the operation in a transaction, the result is the same. 4/ I check 3.1.1-GA, the problem occurs alway. 5/ All the operation are in a transaction. Please read and run my testcase and if I missuse hibernate say me where. I can't reopen the bug HSEARCH-342, I open a new bug because the resolution of the bug HSEARCH-178 don't resolve this problem. Thank you. -- 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, 3 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-500) Some tests don't close the SessionFactory and SearchFactory

by Sanne Grinovero (JIRA)

Some tests don't close the SessionFactory and SearchFactory ----------------------------------------------------------- Key: HSEARCH-500 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-500 Project: Hibernate Search Issue Type: Bug Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 3.2.0.CR1 -- 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, 3 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5088) Add support in DetachedCriteria for predicates in the join condition (HHH-2308)

by Triqui Galletas (JIRA)

Add support in DetachedCriteria for predicates in the join condition (HHH-2308) ------------------------------------------------------------------------------- Key: HHH-5088 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5088 Project: Hibernate Core Issue Type: Improvement Affects Versions: 3.5.0-Final, 3.5.0-CR-2, 3.5.0-CR-1, 3.5.0-Beta-4, 3.5.0-Beta-3 Reporter: Triqui Galletas [HHH-2308|http://opensource.atlassian.com/projects/hibernate/browse/HHH-2308] allows to add conditions to the join clause, but this is not supported in DetachedCriteria. I would really like to see it fixed. -- 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, 3 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-4912) testManyToManyWithFormula induces error with Ingres dialect

by Ray Fan (JIRA)

testManyToManyWithFormula induces error with Ingres dialect ----------------------------------------------------------- Key: HHH-4912 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4912 Project: Hibernate Core Issue Type: Bug Components: query-hql Affects Versions: 3.5.0-Beta-4 Environment: Hibernate 3.5.0-Beta-4, Ingres 9.3.1 Reporter: Ray Fan Attachments: manytomany-logs.zip During test org.hibernate.test.manytomany.ManyToManyTest an error is encountered when using the Ingres dialect. {noformat} testcase time="0.806" classname="org.hibernate.test.manytomany.ManyToManyTest" name="testManyToManyWithFormula"> <error message="could not execute query" type="org.hibernate.exception.GenericJDBCException">org.hibernate.exception.GenericJDBCException: could not execute query at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:132) at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:120) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66) at org.hibernate.loader.Loader.doList(Loader.java:2257) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2151) at org.hibernate.loader.Loader.list(Loader.java:2146) at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:448) at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:363) at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:196) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1258) at org.hibernate.impl.QueryImpl.list(QueryImpl.java:102) at org.hibernate.impl.AbstractQueryImpl.uniqueResult(AbstractQueryImpl.java:859) at org.hibernate.test.manytomany.ManyToManyTest.testManyToManyWithFormula(ManyToManyTest.java:92) Caused by: com.ingres.gcf.util.SqlEx: line 1, Column 'username' found in more than one FROM list table. at com.ingres.gcf.jdbc.DrvObj.readError(Unknown Source) at com.ingres.gcf.jdbc.DrvObj.readResults(Unknown Source) at com.ingres.gcf.jdbc.DrvPrep.prepare(Unknown Source) at com.ingres.gcf.jdbc.DrvConn.createPrepStmt(Unknown Source) at com.ingres.gcf.jdbc.JdbcPrep.<init>(Unknown Source) at com.ingres.gcf.jdbc.JdbcConn.createPrep(Unknown Source) at com.ingres.gcf.jdbc.JdbcConn.prepareStatement(Unknown Source) at org.hibernate.jdbc.AbstractBatcher.getPreparedStatement(AbstractBatcher.java:534) at org.hibernate.jdbc.AbstractBatcher.getPreparedStatement(AbstractBatcher.java:452) at org.hibernate.jdbc.AbstractBatcher.prepareQueryStatement(AbstractBatcher.java:161) at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1597) at org.hibernate.loader.Loader.doQuery(Loader.java:718) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:271) at org.hibernate.loader.Loader.doList(Loader.java:2254) ... 39 more {noformat} The generated SQL query from HQL: from org.hibernate.test.manytomany.User u join fetch u.groups g join fetch g.users {noformat} select user0_.name as name3854_0_, user0_.org as org3854_0_, group2_.name as name3856_1_, group2_.org as org3856_1_, user4_.name as name3854_2_, user4_.org as org3854_2_, group2_.description as descript3_3856_1_, groups1_.userName as userName0__, groups1_.org as org0__, groups1_.groupName as groupName0__, groups1_.org as formula31_0__, users3_.groupName as groupName1__, users3_.org as org1__, userName as userName1__, users3_.org as formula32_1__ from 'User' user0_ inner join UserGroup groups1_ on user0_.name=groups1_.userName and user0_.org=groups1_.org inner join 'Group' group2_ on groups1_.groupName=group2_.name and groups1_.org=group2_.org inner join UserGroup users3_ on group2_.name=users3_.groupName and group2_.org=users3_.org inner join 'User' user4_ on users3_.userName=user4_.name and users3_.org=user4_.org {noformat} seems to includes userName as userName1__ in the select list without table qualification. Ingres is unable to disambiguate the column from groups1_ or users3_ and raises the error. Attaching test logs. -- 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, 3 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5087) A @ManyToOne field on the same entity class is null when 2nd level cache is enabled

by Joseph Pachod (JIRA)

A @ManyToOne field on the same entity class is null when 2nd level cache is enabled ----------------------------------------------------------------------------------- Key: HHH-5087 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5087 Project: Hibernate Core Issue Type: Bug Components: caching (L2) Affects Versions: 3.5.0-Final, 3.3.0.CR1 Reporter: Joseph Pachod Attachments: demos.tar.gz The issue is based on this discussion https://forum.hibernate.org/viewtopic.php?p=2350265 which shows how to have a List with the index managed by Hibernate. The example given involves two distinct entities classes, for example ParentEntity.class et ChildEntity.class. I tried to use it as well for a List containing the same entity, like that (see attachment for more details): public class RecursiveListItem { (..) public void setParent(final RecursiveListItem parent) { this.parent = parent; } public RecursiveListItem getParent() { return parent; } public static final String RECURSIVELISTITEM_ONETOMANY_INDEX_COLUMN_NAME = "recursivelistitem_position"; public static final String RECURSIVELISTITEM_ONETOMANY_JOIN_COLUMN_NAME = "recursivelistitem_id"; @ManyToOne @JoinColumn(name = RECURSIVELISTITEM_ONETOMANY_JOIN_COLUMN_NAME, insertable = false, updatable = false) private RecursiveListItem parent; @SuppressWarnings("unused") @Column(name = RECURSIVELISTITEM_ONETOMANY_INDEX_COLUMN_NAME, insertable = false, updatable = false) private Integer position; @OneToMany(fetch = FetchType.LAZY) @JoinColumn(name = RecursiveListItem.RECURSIVELISTITEM_ONETOMANY_JOIN_COLUMN_NAME) @org.hibernate.annotations.IndexColumn(name = RecursiveListItem.RECURSIVELISTITEM_ONETOMANY_INDEX_COLUMN_NAME) private List<RecursiveListItem> children = new ArrayList<RecursiveListItem>(); (...) } In my test case, I do : EntityManager entityManager = entityManagerFactory.createEntityManager(); RecursiveListItem parent = new RecursiveListItem(); RecursiveListItem child = new RecursiveListItem(); persist(entityManager, parent); persist(entityManager, child); parent.getChildren().add(child); child.setParent(parent); persist(entityManager, parent); persist(entityManager, child); entityManager.close(); entityManager = entityManagerFactory.createEntityManager(); RecursiveListItem childFound = entityManager.find(RecursiveListItem.class, child.getId()); assertNotNull(childFound); assertNotNull(childFound.getParent()); The last line works when the 2nd level cache and fails otherwise. The issue applies both for 3.5 and 3.3.0.CR1. In the attached file I put two maven enabled eclipse projects, on for 3.5 and one for 3.3.0.CR1. Thanks in advance best regards joseph ps : I'll be on vacation until next Monday (April 12) -- 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, 3 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2295) entity-name attribute's syntax not clearly documented

by Jeremy Michael Crosbie (JIRA)

entity-name attribute's syntax not clearly documented ----------------------------------------------------- Key: HHH-2295 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2295 Project: Hibernate3 Type: Bug Components: documentation Versions: 3.2.1 Environment: Windows XP/JDK 1.5/HypersonicSQL Reporter: Jeremy Michael Crosbie Priority: Minor Attachments: Group.hbm.xml Setting entity-name to a value containing a hyphen, in my case 'lender-group' causes odd behaviors seemingly only when calling get() or load(). Also in my case I am mapping a class to two different tables (attached). The first mapping has an entity name with a hyphen, the other does not. When I call load *after committing a transaction where a new entity is persisted* I get an exception (see below). The exception complains of a column called "LENDER" not existing. But once I change the entity-name to something like 'lendergroup' the problem goes away. Interestingly, the missing column complained about is the text before the hyphen, so if I name the entity 'lndr-group' it complains of a column name 'LNDR' not existing. It almost appears if this format is assuming some sort of discriminator, but the online docs are terse when it comes to describing the entity-name field. Exception: org.hibernate.exception.SQLGrammarException: could not load an entity: [lender-group#G9] 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:1799) at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:47) at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:41) at org.hibernate.persister.entity.AbstractEntityPersister.load(AbstractEntityPersister.java:2730) at org.hibernate.event.def.DefaultLoadEventListener.loadFromDatasource(DefaultLoadEventListener.java:365) at org.hibernate.event.def.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:346) at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:123) at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:177) at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:87) at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:862) at org.hibernate.impl.SessionImpl.get(SessionImpl.java:799) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.hibernate.context.ThreadLocalSessionContext$TransactionProtectionWrapper.invoke(ThreadLocalSessionContext.java:301) at $Proxy0.get(Unknown Source) at com.fares.mtrac.group.GroupDaoImpl.findById(GroupDaoImpl.java:148) at com.fares.mtrac.group.GroupDaoImplTest.testFindByIdStringCompanyType(GroupDaoImplTest.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at junit.framework.TestCase.runTest(TestCase.java:164) at junit.framework.TestCase.runBare(TestCase.java:130) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) Caused by: java.sql.SQLException: Column not found: LENDER in statement [select lender-gro0_.group_cd as group1_48_0_, lender-gro0_.group_nm as group2_48_0_, lender-gro0_.user_nm as user3_48_0_ from lender_group_name lender-gro0_ where lender-gro0_.group_cd=?] at org.hsqldb.jdbc.Util.throwError(Unknown Source) at org.hsqldb.jdbc.jdbcPreparedStatement.<init>(Unknown Source) at org.hsqldb.jdbc.jdbcConnection.prepareStatement(Unknown Source) at org.hibernate.jdbc.AbstractBatcher.getPreparedStatement(AbstractBatcher.java:442) at org.hibernate.jdbc.AbstractBatcher.getPreparedStatement(AbstractBatcher.java:368) at org.hibernate.jdbc.AbstractBatcher.prepareQueryStatement(AbstractBatcher.java:105) at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1561) at org.hibernate.loader.Loader.doQuery(Loader.java:661) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224) at org.hibernate.loader.Loader.loadEntity(Loader.java:1785) ... 36 more -- 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, 3 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-331) Verify sorting behaviour for DoubleBridge

by Sanne Grinovero (JIRA)

Verify sorting behaviour for DoubleBridge ----------------------------------------- Key: HSEARCH-331 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-331 Project: Hibernate Search Issue Type: Task Reporter: Sanne Grinovero -- 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, 3 months

2
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 April 2010