February 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3754) formula using table name with space does not work

by Rupesh Kumar (JIRA)

formula using table name with space does not work ------------------------------------------------- Key: HHH-3754 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3754 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.1 Environment: hibernate 3.3.1, Microsoft SQLServer Reporter: Rupesh Kumar Usually when you have the table name with space in its name, you need to escape it while using it in the hbm file and that works. But if you have a property with formula that uses the same table, calling this code below it throws up error : org.hibernate.exception.SQLGrammarException Query query = session.createQuery("from tablewithspace"); List list = query.list(); tablewithspace.hbm.xml ------------------------------------ <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN" "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd"> <hibernate-mapping> <class name="tablewithspace" entityname="tablewithspace" table="[table with space]"> <id name="id" column="id" length="10" type="int"/> <property name="formulacol" formula="(select count(*) from [table with space])" type="string"/> <property name="name" column="name" length="50" type="string"/> </class> </hibernate-mapping> ----------------------------------- The stackstrace is org.hibernate.exception.SQLGrammarException: could not execute query at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:90) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66) at org.hibernate.loader.Loader.doList(Loader.java:2231) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2125) at org.hibernate.loader.Loader.list(Loader.java:2120) at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:401) at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:361) at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:196) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1148) at org.hibernate.impl.QueryImpl.list(QueryImpl.java:102) Caused by: java.sql.SQLException: [Macromedia][SQLServer JDBC Driver][SQLServer]Invalid object name 'ctablewith0_.table with space'. at macromedia.jdbc.base.BaseExceptions.createException(Unknown Source) at macromedia.jdbc.base.BaseExceptions.getException(Unknown Source) at macromedia.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown Source) at macromedia.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown Source) at macromedia.jdbc.sqlserver.tds.TDSRPCRequest.processReplyToken(Unknown Source) at macromedia.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown Source) at macromedia.jdbc.sqlserver.SQLServerImplStatement.getNextResultType(Unknown Source) at macromedia.jdbc.base.BaseStatement.commonTransitionToState(Unknown Source) at macromedia.jdbc.base.BaseStatement.postImplExecute(Unknown Source) at macromedia.jdbc.base.BasePreparedStatement.postImplExecute(Unknown Source) at macromedia.jdbc.base.BaseStatement.commonExecute(Unknown Source) at macromedia.jdbc.base.BaseStatement.executeQueryInternal(Unknown Source) at macromedia.jdbc.base.BasePreparedStatement.executeQuery(Unknown Source) at macromedia.jdbc.base.BasePreparedStatementPoolable.executeQuery(Unknown Source) at coldfusion.server.j2ee.sql.JRunPreparedStatement.executeQuery(JRunPreparedStatement.java:74) at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:208) at org.hibernate.loader.Loader.getResultSet(Loader.java:1808) at org.hibernate.loader.Loader.doQuery(Loader.java:697) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:259) at org.hibernate.loader.Loader.doList(Loader.java:2228) ... 40 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, 10 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3438) Could not check JTA transaction; nested exception is java.lang.StackOverflowError

by Jara Cesnek (JIRA)

Could not check JTA transaction; nested exception is java.lang.StackOverflowError --------------------------------------------------------------------------------- Key: HHH-3438 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3438 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.3.0.GA Reporter: Jara Cesnek This code cause infinite loop. Moreover still dont work with JOTM. HHH-3358 protected UserTransaction *getUserTransaction*() { log.trace( "Attempting to locate UserTransaction via JNDI [{}]", getUserTransactionName() ); try { UserTransaction ut = ( UserTransaction ) getInitialContext().lookup( getUserTransactionName() ); if ( ut == null ) { throw new TransactionException( "Naming service lookup for UserTransaction returned null [" + getUserTransactionName() +"]" ); } log.trace( "Obtained UserTransaction" ); return ut; } catch ( NamingException ne ) { throw new TransactionException( "Could not find UserTransaction in JNDI [" + *getUserTransaction()* + "]", ne ); } } -- 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, 10 months

4
4
0 / 0

[Hibernate-JIRA] Created: (BVAL-114) Relax property names in ConstraintValidatorContext

by Emmanuel Bernard (JIRA)

Relax property names in ConstraintValidatorContext -------------------------------------------------- Key: BVAL-114 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-114 Project: Bean Validation Issue Type: Improvement Components: spec-general Affects Versions: 1.0 public draft Reporter: Emmanuel Bernard Fix For: 1.0 proposed final draft needed to reference subelements in a object (if the ConstraintValidator reads some subproperties). -- 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, 10 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3770) NPE in o.h.dialect.function.CastFunction

by Ondra Žižka (JIRA)

NPE in o.h.dialect.function.CastFunction ---------------------------------------- Key: HHH-3770 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3770 Project: Hibernate Core Issue Type: Patch Environment: Hibernate Core from trunk Reporter: Ondra Žižka Attachments: CastFunctionNPE.diff CastFunction.render() throws NPE when "CAST( foo AS Type )" contains invalid type, as described at http://forum.hibernate.org/viewtopic.php?t=960362. This is a patch to throw QueryException instead. -- 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3767) Create migration scripts from schemas not using the end-revision column to schemas with it

by Adam Warski (JIRA)

Create migration scripts from schemas not using the end-revision column to schemas with it ------------------------------------------------------------------------------------------ Key: HHH-3767 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3767 Project: Hibernate Core Issue Type: Sub-task Components: envers Reporter: Adam Warski Assignee: Adam Warski The end-revision column can be calculated basing on the content of "revision"+id columns, so a migration script between the two schema variatns would be useful. -- 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3762) LockMode.UPGRADE and TABLE_PER_CLASS and PostgreSQL generates usupported SQL

by Dobes Vandermeer (JIRA)

LockMode.UPGRADE and TABLE_PER_CLASS and PostgreSQL generates usupported SQL ---------------------------------------------------------------------------- Key: HHH-3762 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3762 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: Hibernate 3.3.1.GA, PostgreSQL 8.2, Hibernate-Annotations, Hibernate-EntityManager, Glassfish v2ur2, Windows Vista 64.bit Reporter: Dobes Vandermeer Priority: Minor I created a class called Job and a few subclasses such as SendEmailJob, ProcessSubscriptionsJob, and so on. I set the inheritance type to TABLE_PER_CLASS since the columns in each are quite different. However, the worker that loads and executes the jobs is the same. The worker was trying to use a piece of code like this: @Timeout public void timeout(Timer timer) { session.get(Job.class, (Long)timer.getInfo(), LockMode.UPGRADE); } PostgreSQL returned the following error: org.postgresql.util.PSQLException: ERROR: SELECT FOR UPDATE/SHARE is not allowed with UNION/INTERSECT/EXCEPT The workaround was to lock the object separately, so hibernate only tries to select .. for update from one table: @Timeout public void timeout(Timer timer) { Job job = session.get(Job.class, (Long)timer.getInfo(), LockMode.NONE); session.refresh(job, LockMode.UPGRADE); // Now there's just one table involved } A possible solution to this issue would be for hibernate to do this breakdown automatically when doing a get() on a TABLE_PER_CLASS superclass - i.e. it would ignore LockMode when fetching, but if LockMode is > UPGRADE it would call refresh() with that lock mode on the found object (if any) to lock it. This does introduce an extra SELECT but I can't really think of another solution for this use case. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 10 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3758) Data model object types issue with Id and Generics

by Giovanni Azua (JIRA)

Data model object types issue with Id and Generics -------------------------------------------------- Key: HHH-3758 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3758 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.6 Environment: Hibernate 3.2.6.ga, Windows XP, Maven 2.0.9, JDK 1.6.0_11 Reporter: Giovanni Azua Wanting to have a reusable base for Identifiable data model Object types and at the same time a stronger type checking (e.g. Generic DAO implementations) I introduced the interface and Abstract class below. The problem is that my working models as soon as I extend from AbstractIdentifyable or just implement Identifyable, my test cases break with the following: org.perfectjpattern.jee.api.integration.dao.DaoException: org.hibernate.exception.SQLGrammarException: could not insert: [example.datamodel.Person] I suspect this is related to some kind of Hibernate use of Reflection that can't find in the model supertypes a definition of setId that matches exactly the type it expects e.g. Long but it is a generic parameter. regards, Giovanni public interface Identifyable<Id extends java.io.Serializable> { public Id getId(); public void setId(Id anId); } and base abstract reusable implementation public abstract class AbstractIdentifyable<Id extends java.io.serializable> implements Identifyable<Id> { // ... implements the reusable Identifyable methods } -- 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3757) Performance Problem in IdentityMap

by Henry König (JIRA)

Performance Problem in IdentityMap ---------------------------------- Key: HHH-3757 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3757 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: Hibernate Version 3.3.1.GA, MS SQL Server 2000 - 8.00.2050 Reporter: Henry König There is a large performance problem in functions entrySet() and entryList() of IdentityMap. As opposed to the function entryArray(), which use a dirty flag, both functions create new Sets/Lists, iterate over the stored data and insert new objects if they are called. Therefore the BatchFetchQueue of the BatchingCollectionInitializer (function getCollectionBatch()) is really, really slow. -- 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Created: (BVAL-69) The default MessageResolver now handles Locale

by Emmanuel Bernard (JIRA)

The default MessageResolver now handles Locale ---------------------------------------------- Key: BVAL-69 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-69 Project: Bean Validation Issue Type: New Feature Components: ri-general Reporter: Emmanuel Bernard Fix For: 1.0 public draft This is not the case of the actual implementation. -- 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, 10 months

2
5
0 / 0

[Hibernate-JIRA] Commented: (ANN-161) Add support for custom code-based enums in EnumType - such as mapping ISO codes to gender Enums

by Frederic Leitenberger (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-161?page=co... ] Frederic Leitenberger commented on ANN-161: ------------------------------------------- Hello again, please look at the patch and include it in Hibernate. Or at least say why not ... technically i don't see any objections. Greetings Freddy; > Add support for custom code-based enums in EnumType - such as mapping ISO codes to gender Enums > ----------------------------------------------------------------------------------------------- > > Key: ANN-161 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-161 > Project: Hibernate Annotations > Issue Type: Improvement > Components: binder > Affects Versions: 3.1beta6 > Reporter: Leonardo Quijano > Priority: Minor > Attachments: MappedEnum.java.patch > > > Now, this could be seen as an improvement to EnumType that's specific to a business domain, but I'm thinking it could help in the general case. Right now we can map JDK enums to several database types, such as INT, VARCHAR, etc. Each of these approaches have some drawbacks, depending on the domain: > 1) The int mapping is not very reliable through refactorings. An enum that's mapped to a "0" or "2" integer value in the database could end up mapped as a different value if a future refactoring adds an additional enum with an ordinal of 0. > 2) The varchar mapping could use the enum name instead of its ordinal. But again, if the enum changes, the mapping gets lost and it needs manual changes. It's also heavier on the performance side. > A useful approach for enum mappings is to use common codes to represent them in the database. That depends of course of the domain logic that's being used. A useful example is the Human sex mapping, defined in ISO code 5218: > http://en.wikipedia.org/wiki/ISO_5218 > * 0 = not known, > * 1 = male, > * 2 = female, > * 9 = not specified. > For this to work, the Sex enum could have a property "isoCode" that specifies the mapping between the database integer code and the Java enum. > For other domain examples additional examples could be specified. > The EnumType could include a parameter that indicates the property to be evaluated for code-mapping, performing the translation in this way. Of course, reflection cache / byte-code generation / whatever could be specified to speed up the process. > As always, patches are offered if you think this improvement is viable. -- 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, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues February 2009