November 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2401) CLOB truncation on DB2 when using 2 or 3 byte chars (UTF8)

by Simon Jongsma (JIRA)

CLOB truncation on DB2 when using 2 or 3 byte chars (UTF8) ---------------------------------------------------------- Key: HHH-2401 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2401 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.ga Environment: Hibernate 3.2.0 GA + JBoss 4.0.4.GA on Windows XP + DB2 UDB for ISeries V5R3 + IBM JT Open driver 4.9 Reporter: Simon Jongsma Priority: Minor Attachments: ClobTruncated.zip A CLOB column is used in DB2 mapped to a String in Java with the Hibernate "Text" mapping. The column in DB2 has a CCSID 1208 which means "UTF8" (= Unicode). The CLOB truncation occurs when characters are used that are UTF8 coded in more than one byte. In that the string is truncated when persisted in the database. For example the string "Granpré Molière†; 0123456789". This string has three diacritical marks in it. The é and è are coded in two bytes in UTF8 and the † in three bytes. This string will be stored as "Granpré Molière†; 012345". So "6789" is not stored. It appears as though Hibernate does not take into account that a character can be more than 1 byte in UTF8. The number of missing char's at the end is exactly: string.getBytes("UTF-8").length minus string.length() It is not a problem of DB2 or the JT Open driver: Storing and retrieving (from a Java program) the same String directly via Jdbc into the DB2 table and retrieving it, works 100% fine. So this clearly points to a problem somewhere in Hibernate. -- 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, 6 months

3
6
0 / 0

[Hibernate-JIRA] Créée: (HHH-2086) Patch for bug HHH-2076 and to be able to use <formula> in <key> for <one-to-many>

by Xavier Brénuchon (JIRA)

Patch for bug HHH-2076 and to be able to use <formula> in <key> for <one-to-many> --------------------------------------------------------------------------------- Key: HHH-2086 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2086 Project: Hibernate3 Type: Patch Components: core Versions: 3.2.0.cr4 Reporter: Xavier Brénuchon Attachments: formula_one_to_many.patch Hello, There is a patch to correct bug HHH-2076 and make an improvement for HHH-944. In fact, theses 2 cases are linked. They need, amongst other things, a formula in the right part of outer join. This patch is simple but many class concerns (to propagate formula templates). About formula in one-to-many : You must have at least a column (not only formula), because it's not possible to have an Update order without at least a column. If it is the case, hibernate patch will raise an MappingException rightly. This patch add two TestCase : org.hibernate.test.onetoone.bidirectionnalformula. OneToOneBidirectionalFormulaTest org.hibernate.test.onetomany.formula. OneToManyFormulaTest Would it be possible to integrate this patch into Hibernate 3.2 ? -- 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, 6 months

4
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3585) Convert org.hibernate.cache.jbc2 integration to use JBoss Cache 3

by Brian Stansberry (JIRA)

Convert org.hibernate.cache.jbc2 integration to use JBoss Cache 3 ----------------------------------------------------------------- Key: HHH-3585 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3585 Project: Hibernate Core Issue Type: Task Components: caching (L2) Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 3.4 JBoss Cache 3 is the main development branch for JBC. It introduces MVCC locking, which should help the Hibernate 2LC use case. Integration with JBoss Cache 3 and use of MVCC has already been tested against the Hibernate Core 3.3.1.GA tag, on the https://svn.jboss.org/repos/hibernate/core/branches/JBOSS_CACHE_3/ branch. Task here is to port the changes (all in cache-jbosscache2 testsuite) to trunk. -- 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, 6 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-3492) Bug: SingleTableEntityPersister - generateSequentialSelect()

by Michael Kohlhuber (JIRA)

Bug: SingleTableEntityPersister - generateSequentialSelect() ------------------------------------------------------------ Key: HHH-3492 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3492 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: hibernate 3.2.5.ga oracle 9i Reporter: Michael Kohlhuber http://forum.hibernate.org/viewtopic.php?t=990850 -- 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, 6 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HBX-812) Fetching Children of Database _crawls_.

by Syd Poetry (JIRA)

Fetching Children of Database _crawls_. --------------------------------------- Key: HBX-812 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-812 Project: Hibernate Tools Type: Bug Components: reverse-engineer Versions: 3.2beta8 Environment: MySQL 5.0, Eclipse 3.2, JDK 1.5, Beta8 for Hibernate Tools Reporter: Syd Poetry I just updated a bunch of components for Eclipse (mostly related to Visual Editor); added a couple of tables to my database, went to regenerate all the POJO clases .hbm.xml mapping files, and found that anything that queries the database schema runs abysmally slow. Updated the tools from beta6 to beta8 thinking it might be a conflict with one of the updates that was performed, still very slow (5+ minutes to retrieve a list of tables!). Deleted all my hibernate-related XML files thinking it might be a parsing error, went to generate a new console file, and revenge.xml, found out that any listbox that tried to access the schema appeared to be hanging. It finishes after much hard-drive crunching. I have 2.2 GBs free running windows XP, MEM usage is 856 MB out of 1.5 GB physical memory. Just out of curiousity, is *anyone* else having this slow response for schema detection? I'm wondering if I have to update another component like a driver or something like that. -- 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, 6 months

6
13
0 / 0

[Hibernate-JIRA] Created: (HHH-3362) NullPointerException in org.hibernate.dialect.Dialect$2.getReturnType

by Istvan Kovacs (JIRA)

NullPointerException in org.hibernate.dialect.Dialect$2.getReturnType --------------------------------------------------------------------- Key: HHH-3362 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3362 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.6 Environment: Hibernate Core 3.6.2 GA, hsqldb Reporter: Istvan Kovacs Attachments: bug_src.zip java.lang.NullPointerException at org.hibernate.dialect.Dialect$2.getReturnType(Dialect.java:85) at org.hibernate.hql.ast.util.SessionFactoryHelper.findFunctionReturnType(SessionFactoryHelper.java:382) at org.hibernate.hql.ast.tree.AggregateNode.getDataType(AggregateNode.java:21) at org.hibernate.hql.ast.tree.SelectClause.initializeExplicitSelectClause(SelectClause.java:143) at org.hibernate.hql.ast.HqlSqlWalker.useSelectClause(HqlSqlWalker.java:705) at org.hibernate.hql.ast.HqlSqlWalker.processQuery(HqlSqlWalker.java:529) at org.hibernate.hql.antlr.HqlSqlBaseWalker.query(HqlSqlBaseWalker.java:645) at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectStatement(HqlSqlBaseWalker.java:281) at org.hibernate.hql.antlr.HqlSqlBaseWalker.statement(HqlSqlBaseWalker.java:229) at org.hibernate.hql.ast.QueryTranslatorImpl.analyze(QueryTranslatorImpl.java:228) at org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:160) at org.hibernate.hql.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:111) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:77) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:56) at org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:72) at org.hibernate.impl.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:133) at org.hibernate.impl.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:112) at org.hibernate.impl.SessionImpl.createQuery(SessionImpl.java:1623) at org.hibernate.console.HQLQueryPage.setSession(HQLQueryPage.java:106) at org.hibernate.console.ConsoleConfiguration$4.execute(ConsoleConfiguration.java:388) at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:65) at org.hibernate.console.ConsoleConfiguration.executeHQLQuery(ConsoleConfiguration.java:383) [...] 3 classes: Employee: Long ID; String name; Shop shop Shop: Long ID; String name; Set<Employee> employees; Map<Product, Integer> stock Product: Long ID; String name I mapped them to RDBMS using Hibernate. There's a table to hold stock info: SHOP_PRODUCT_STOCK - has fields SHOP_ID, PRODUCT_ID, AMOUNT SQL to query the average stock of each product: select p.name as name, avg(sps.amount) as avg_stock from Shop s, Shop_Product_Stock sps, Product p where sps.product_id=p.product_id and sps.product_id=p.product_id group by p.name order by p.name; Attempt in HQL that the produces exception: select p, avg(s.stock[p]) from Shop s, Product p group by p I've also tried SELECTing and GROUPing BY p.id and p.name. None of the three variants work. -- 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, 6 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HBX-1082) Creating a formula property when reverse engineering

by Anders Reinhardt Hansen (JIRA)

Creating a formula property when reverse engineering ---------------------------------------------------- Key: HBX-1082 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1082 Project: Hibernate Tools Issue Type: Improvement Components: reverse-engineer Affects Versions: 3.2.beta11 Environment: All environments Reporter: Anders Reinhardt Hansen Priority: Minor Having lots of formula properties in mapping files is quite frustrating when reverse engineering database changes. Therefore it would be a big help if there was a way to write formula properties in the Hibernate Reverse Engineering files. A property formula is a property of a mapping file which is calculated by hibernate. I.e. <class name="XXX"> <column name="xxx" type="xxx" formula="(coloumn1+coloumn2)/coloumn3"/> </class> the reveng file could look like this <hibernate-reverse-engineering> ... <formula name="xxx" type="xxx" formula="(coloumn1+coloumn2)/coloumn3"/> </hibernate-reverse-engineering> Maybe the reverse engineering file is not the correct place for this feature. Suggestions are welcome -- 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, 6 months

2
1
0 / 0

[Hibernate-JIRA] Created: (ANN-746) Implemented BigDecimalRange Validator for BigDecimals with precision range and scale

by Priya M (JIRA)

Implemented BigDecimalRange Validator for BigDecimals with precision range and scale ------------------------------------------------------------------------------------ Key: ANN-746 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-746 Project: Hibernate Annotations Issue Type: New Feature Reporter: Priya M Attachments: BigDecimalRange.java, BigDecimalRangeValidator.java Currently, hibernate validator's do not have @Range or @Length for decimal numbers (like float, double and BigDecimal) for validating precision and scale simultaneously. Also, Hibernate doesn't generate correct db column types as Number(x,y) if Java Type is Float or Double. However it works only for BigDecimal. I've added the annotation for BigDecimalRange and BigDecimalRangeValidator for the same Usage @BigDecimalRange(minPrecision=0, maxPrecision=13, scale=2) public BigDecimal getFoo() { return this.foo; } It works for my app. -- 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, 6 months

2
2
0 / 0

[Hibernate-JIRA] Created: (BVAL-12) <T> in ValidatorContext<T> Validator<T> and InvalidConstraint<T> are inadequately considered unique

by Emmanuel Bernard (JIRA)

<T> in ValidatorContext<T> Validator<T> and InvalidConstraint<T> are inadequately considered unique --------------------------------------------------------------------------------------------------- Key: BVAL-12 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-12 Project: Bean Validation Issue Type: Sub-task Components: ri-general Reporter: Emmanuel Bernard Assignee: Hardy Ferentschik In ValidatorImpl.validate() T Generic of ValidatorContext<T> and InvalidConstraint<T> are likely to be different than the Validator<T> A context can be created in a validator (T are equal). but the same context (a clone really) can be passed to a sub validator. Ts are then different. I believe it's the same for InvalidConstraints. An IC created by a subvalidator<U> will craete IC<U>, you will need to convert them in IC<T> when coming to the root validator<T>. So we need something like private <U> List<InvalidConstraintImpl<T>> validate(ValidationContext<U> context, List<String> groups) { } same for similar 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

15 years, 6 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3233) Integer overflow in TableHiLoGenerator

by Hauke Rabe (JIRA)

Integer overflow in TableHiLoGenerator --------------------------------------- Key: HHH-3233 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3233 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.2 Reporter: Hauke Rabe The TableGenerator use for id generation the type INTEGER. The subclass TableHiLoGenerator use these id for multiplication with the maxLo value. But if you mutiply two int and assign the result to a long you can get an integer overflow. The TableGenerator should work with long values, or must be able to configure. -- 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, 6 months

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues November 2008