March 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-5406) Schema export does not consistently follow naming strategy for unique constraints

by Jonathan (JIRA)

Schema export does not consistently follow naming strategy for unique constraints --------------------------------------------------------------------------------- Key: HHH-5406 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5406 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.4 Environment: Hibernate 3.5.4, No database needed Reporter: Jonathan Priority: Minor Attachments: UniqueConstraintTest.java When performing a schema export for entities that include annotated unique constraints, Hibernate does not consistently follow the naming strategy for field names in the unique constraint. It appears that a naming strategy applies only for fields that are mapped to another class. The attached test demonstrates this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
1
0 / 0

[Hibernate-JIRA] Closed: (HHH-906) Criteria API ignores 'where' attribute of class element

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-906?page=co... ] Steve Ebersole closed HHH-906. ------------------------------ Closing stale resolved issues > Criteria API ignores 'where' attribute of class element > ------------------------------------------------------- > > Key: HHH-906 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-906 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.0.5 > Environment: Hibernate 3.0.5, Oracle 9i > Reporter: Patrick Dumontel > Assignee: Gavin King > > assume a where attribute in a class mapping: > <class ... where="column_filter_id = 100"...> > While HQL integrates the where segment to the generated SQL, the Criteria API seems not to be doing this. My code ends up with multiple inserts of the same object instance when Criteria is used vs. HQL. > My apologies if this was reported previously. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-558) HQL doesn't support multi-byte character in class name and property names

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-558?page=co... ] Steve Ebersole closed HHH-558. ------------------------------ Closing stale resolved issues > HQL doesn't support multi-byte character in class name and property names > ------------------------------------------------------------------------- > > Key: HHH-558 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-558 > Project: Hibernate Core > Issue Type: Bug > Affects Versions: 3.0 final, 3.0.1, 3.0.2, 3.0.3, 3.0.4, 3.0.5 > Environment: Hibernate 3.0.X, hsqldb > Reporter: zhangwei > Assignee: Joshua Davis > Fix For: 3.1 beta 1 > > > HQL: > from User user where user.\u4e2d like '%\u4e2d%' > when classname or property name contains multi-byte character, Query.list() will throws an exception which says > org.hibernate.QueryException: unexpected char: 0xF6 [from com.hsd.security.User user where user.中文 like '%中文%'] > at org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:165) > at org.hibernate.hql.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:83) > at org.hibernate.impl.SessionFactoryImpl.getQuery(SessionFactoryImpl.java:427) > at org.hibernate.impl.SessionImpl.getQueries(SessionImpl.java:884) > at org.hibernate.impl.SessionImpl.list(SessionImpl.java:834) > at org.hibernate.impl.QueryImpl.list(QueryImpl.java:74) > at test.TestHibernate.test中文字符串(TestHibernate.java:11) > 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 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 org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:474) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:342) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:194) > Caused by: line 1:44: unexpected char: 0xF6 > at org.hibernate.hql.antlr.HqlBaseLexer.nextToken(HqlBaseLexer.java:281) > at antlr.TokenBuffer.fill(TokenBuffer.java:69) > at antlr.TokenBuffer.LA(TokenBuffer.java:80) > at antlr.LLkParser.LA(LLkParser.java:52) > at org.hibernate.hql.antlr.HqlBaseParser.identPrimary(HqlBaseParser.java:3728) > at org.hibernate.hql.antlr.HqlBaseParser.primaryExpression(HqlBaseParser.java:3311) > at org.hibernate.hql.antlr.HqlBaseParser.atom(HqlBaseParser.java:3031) > at org.hibernate.hql.antlr.HqlBaseParser.unaryExpression(HqlBaseParser.java:2806) > at org.hibernate.hql.antlr.HqlBaseParser.multiplyExpression(HqlBaseParser.java:2687) > at org.hibernate.hql.antlr.HqlBaseParser.additiveExpression(HqlBaseParser.java:2407) > at org.hibernate.hql.antlr.HqlBaseParser.concatenation(HqlBaseParser.java:481) > at org.hibernate.hql.antlr.HqlBaseParser.relationalExpression(HqlBaseParser.java:2195) > at org.hibernate.hql.antlr.HqlBaseParser.equalityExpression(HqlBaseParser.java:2057) > at org.hibernate.hql.antlr.HqlBaseParser.negatedExpression(HqlBaseParser.java:2020) > at org.hibernate.hql.antlr.HqlBaseParser.logicalAndExpression(HqlBaseParser.java:1937) > at org.hibernate.hql.antlr.HqlBaseParser.logicalOrExpression(HqlBaseParser.java:1901) > at org.hibernate.hql.antlr.HqlBaseParser.expression(HqlBaseParser.java:1663) > at org.hibernate.hql.antlr.HqlBaseParser.logicalExpression(HqlBaseParser.java:1834) > at org.hibernate.hql.antlr.HqlBaseParser.whereClause(HqlBaseParser.java:376) > at org.hibernate.hql.antlr.HqlBaseParser.queryRule(HqlBaseParser.java:617) > at org.hibernate.hql.antlr.HqlBaseParser.selectStatement(HqlBaseParser.java:263) > at org.hibernate.hql.antlr.HqlBaseParser.statement(HqlBaseParser.java:150) > at org.hibernate.hql.ast.QueryTranslatorImpl.parse(QueryTranslatorImpl.java:209) > at org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:127) > ... 19 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

15 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-1392) Proxies cannot be serialized after session is closed

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1392?page=c... ] Steve Ebersole closed HHH-1392. ------------------------------- Closing stale resolved issues > Proxies cannot be serialized after session is closed > ---------------------------------------------------- > > Key: HHH-1392 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1392 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.1.1 > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Fix For: 3.1.2 > > > Dues to the changes made for HHH-1290, proxies can no longer be serialized after the Session has been closed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-1254) Serialization of Sessions using JDBCTransactions with auto-flush/auto-close

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1254?page=c... ] Steve Ebersole closed HHH-1254. ------------------------------- Closing stale resolved issues > Serialization of Sessions using JDBCTransactions with auto-flush/auto-close > --------------------------------------------------------------------------- > > Key: HHH-1254 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1254 > Project: Hibernate Core > Issue Type: Bug > Components: core > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Priority: Minor > Fix For: 3.1 > > > When a Session (actually the JDBCContext) gets serialized, it "takes with it" its isTransactionCallbackRegistered variable. The issue is that in the case of JDBCTransaction, this variable is really tied to the JDBCTransaction which does not get serialized along with the JDBCContext (as opposed to JTA-based transactions where this indicates the registration of the txn synch). Thus upon deserialization, any new JDBCTransaction is not able to register as a callback since the JDBCContext thinks there is already one registered. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-1320) configuration and mapping file locations

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1320?page=c... ] Steve Ebersole closed HHH-1320. ------------------------------- Closing stale resolved issues > configuration and mapping file locations > ---------------------------------------- > > Key: HHH-1320 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1320 > Project: Hibernate Core > Issue Type: New Feature > Affects Versions: 3.1 > Environment: 3.0.5 > Reporter: joneric Wennerstrom > Priority: Minor > > I am building a web app which will use hibernate for it's persistence layer. > I would like to place the hibernate.cfg.xml file in the WEB-INF directory, and then place all of my xxxx.hbm.xml mapping files in the /WEB-INF/hibernate/ directory. > I have not been able to do this (at least nothing I tried worked, but perhaps I'm just not doing it right). > So for congiguring hibernate, I would so something like the following: > configuration.configure("WEB-INF/hibernate.cfg.xml"); > So for example, my hibernate.cfg.xml file would have the following mappings: > <mapping resource="WEB-INF/hibernate/user.hbm.xml"/> > <mapping resource="WEB-INF/hibernate/settings.hbm.xml"/> > ... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-1079) Named parameter does not appear in Query using UNION

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1079?page=c... ] Steve Ebersole closed HHH-1079. ------------------------------- Closing stale resolved issues > Named parameter does not appear in Query using UNION > ---------------------------------------------------- > > Key: HHH-1079 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1079 > Project: Hibernate Core > Issue Type: Bug > Affects Versions: 3.1 rc 1 > Environment: Hibernate 3.1rc1 > Hibernate Annotation 3.1 Beta 6 > Firebird 1.5.2 > Reporter: Leandro Sinhorini Alves > Assignee: Steve Ebersole > > My HQL throws "org.hibernate.QueryException: Named parameter does not appear in Query: operacaoRC" > But, how can you see, the parameter operacaoRC is in the second query of union. > select ept.medidaQuantidade, ept.produto.nome, ept.empresa.nome, ept.ccEmprestimoDestino.empresa.nome > from br.com.b2brasil.centralfacil.dw.financeiro.Emprestimo ept > where ept.dataMovimento = :data > and ept.operacao = :operacaoEC > and ept.produto.produtoNivel2.id = :produtoId > union > select ept.medidaQuantidade, ept.produto.nome, ept.ccEmprestimoOrigem.empresa.nome, ept.empresa.nome > from br.com.b2brasil.centralfacil.dw.financeiro.Emprestimo ept > where ept.dataMovimento = :data > and ept.operacao = :operacaoRC > and ept.produto.produtoNivel2.id = :produtoId -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Closed: (HBX-40) hbm2java should exit with error on failure

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-40?page=com... ] Steve Ebersole closed HBX-40. ----------------------------- Closing stale resolved issues > hbm2java should exit with error on failure > ------------------------------------------ > > Key: HBX-40 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-40 > Project: Hibernate Tools > Issue Type: Patch > Components: hbm2java > Affects Versions: 2.1 > Environment: hibernate-extensions-2.1.3 > Reporter: Aaron Read > Assignee: Max Rydahl Andersen > > For Makefiles and shell scripts: > diff -ruNb hibernate-extensions-2.1.3/tools/src/java/net/sf/hibernate/tool/hbm2java/CodeGenerator.java hibernate-extensions-2.1.3-new/tools/src/java/net/sf/hibernate/tool/hbm2java/CodeGenerator.java > --- hibernate-extensions-2.1.3/tools/src/java/net/sf/hibernate/tool/hbm2java/CodeGenerator.java 2004-11-22 14:20:02.000000000 -0800 > +++ hibernate-extensions-2.1.3-new/tools/src/java/net/sf/hibernate/tool/hbm2java/CodeGenerator.java 2004-12-06 09:24:50.000000000 -0800 > @@ -127,6 +127,7 @@ > } > catch (Exception e) { > e.printStackTrace(); > + System.exit(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

15 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-1031) Add "count" operation to Criteria

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1031?page=c... ] Steve Ebersole closed HHH-1031. ------------------------------- Closing stale resolved issues > Add "count" operation to Criteria > --------------------------------- > > Key: HHH-1031 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1031 > Project: Hibernate Core > Issue Type: New Feature > Components: core > Reporter: Brian Remmington > Priority: Minor > > The ability to easily discover the size of a result set from a Criteria would be useful, such as "Criteria.count()". Although there are a few workarounds suggested on the forums, they all seem pretty verbose and some appear to have side-effects. This enhancement request may be related to HHH-635. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Closed: (HHH-1183) Getting sql "plan" for DML operations

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1183?page=c... ] Steve Ebersole closed HHH-1183. ------------------------------- Closing stale resolved issues > Getting sql "plan" for DML operations > ------------------------------------- > > Key: HHH-1183 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1183 > Project: Hibernate Core > Issue Type: Improvement > Components: core > Reporter: Max Rydahl Andersen > Fix For: 3.1 > > > It seems it is not possible to get a "query plan" for DML operations...that would be reaaally nice to have ;) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
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 March 2011