June 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3327) Allow DDL comment within timestamp (patch included)

by Paul Benedict (JIRA)

Allow DDL comment within timestamp (patch included) --------------------------------------------------- Key: HHH-3327 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3327 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.6 Reporter: Paul Benedict Attachments: timestamp-comment.patch.txt In my corporate environment, the logical names of tables and columns go into our Hibernate mappings. The logical names are represented in DDL comments via the <comment> sub-elements. Unfortunately, the only columns we currently cannot comment are on <timestamp> (element, not type) columns. The provided patch adds the optional "comment" sub-element to "timestamp" element. I made the following change to Hibernate 3.2.x, ran HBM2DDL, and Hibernate Tools worked as expected. The patch is against the DTD in the svn trunk. <!ELEMENT timestamp (meta*,comment?)> If possible, please consider this for 3.3. Thanks. -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-465) order by nulls first / last

by hamster (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-465?page=co... ] hamster commented on HHH-465: ----------------------------- Just FYI: PostgreSQL supports nulls last/first starting from 8.3 version. http://postgresql.com.cn/docs/8.3/static/queries-order.html (compare with http://postgresql.com.cn/docs/8.2/static/queries-order.html) Cheers, > order by nulls first / last > --------------------------- > > Key: HHH-465 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-465 > Project: Hibernate3 > Issue Type: Improvement > Components: core > Affects Versions: 3.0.3 > Reporter: Anthony Patricio > Priority: Minor > > support of nulls first / last in order clause > "NULLS LAST" is part of the SQL 99 standard. > The syntax is as follows: > ORDER BY [COLUMN NAME] [ASC | DESC] [NULLS FIRST | NULLS LAST] > In different DBs, the sorting of nulls relative to other values is handled differently. > PostgreSQL - Nulls are considered HIGHER than non-nulls. > DB2 - Higher > MSSQL - Lower > MySQL - Lower > Oracle - Higher > The following DBs have supported this functionality: > DB2 V7 > Oracle 9i > PostgreSQL, MySQL, SQLServer do not appear to support this from what I can gather. > see http://forum.hibernate.org/viewtopic.php?t=942176&start=0&postdays=0&post... -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-207) Make DateBridge TwoWay to facilitate projection

by Emmanuel Bernard (JIRA)

Make DateBridge TwoWay to facilitate projection ----------------------------------------------- Key: HSEARCH-207 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-207 Project: Hibernate Search Issue Type: Improvement Components: engine Reporter: Emmanuel Bernard Priority: Minor Fix For: 3.1.0 http://forum.hibernate.org/viewtopic.php?p=2385014#2385014 -- 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, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-196) ObjectNotFoundException not caught in FullTextSession

by Christian Wiedmann (JIRA)

ObjectNotFoundException not caught in FullTextSession ----------------------------------------------------- Key: HSEARCH-196 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-196 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.0.1.GA Environment: Hibernate core 3.2.4.sp1, MySQL 5 Reporter: Christian Wiedmann Priority: Minor I am getting an ObjectNotFoundException from FullTextSession when running a query with items in the index that have been deleted from the database. It seems like the intent is not to let this exception be thrown, but the stack trace shows the exception is not being caught in ObjectLoader.load when it is thrown from session.get(). ref: http://forum.hibernate.org/viewtopic.php?p=2384677 org.hibernate.ObjectNotFoundException: No row with the given identifier exists: [com.lawtrust.server.Document#ca533472193932230119394006b0004f] at org.hibernate.impl.SessionFactoryImpl$1.handleEntityNotFound(SessionFactoryImpl.java:377) at org.hibernate.event.def.DefaultLoadEventListener.returnNarrowedProxy(DefaultLoadEventListener.java:223) at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:187) at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:103) at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:878) at org.hibernate.impl.SessionImpl.get(SessionImpl.java:815) at org.hibernate.impl.SessionImpl.get(SessionImpl.java:808) at org.hibernate.search.engine.ObjectLoader.load(ObjectLoader.java:27) at org.hibernate.search.engine.ProjectionLoader.load(ProjectionLoader.java:54) at org.hibernate.search.query.FullTextQueryImpl.list(FullTextQueryImpl.java:244) at com.lawtrust.server.bl.spring.service.impl.SearchServiceImpl.find(SearchServiceImpl.java:94) -- 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, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-205) Out of Memory on copy of large indexes by JMS

by Sanne Grinovero (JIRA)

Out of Memory on copy of large indexes by JMS --------------------------------------------- Key: HSEARCH-205 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-205 Project: Hibernate Search Issue Type: Bug Components: directory provider Reporter: Sanne Grinovero When using FSMasterDirectoryProvider Hibernate Search uses java.nio.channels.FileChannel to make a copy of the index, but each File needs to reserve an amout of RAM equals to the current block size; it is currently set to "whole file", so for big indexes it could cause Out of Memory errors. The file should be transfered splitting it in minor fixed blocks. http://forum.hibernate.org/viewtopic.php?t=987323 -- 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, 11 months

1
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3312) Cascading is performed even in the absence of "cascade" parameter.

by Gregory Klimov (JIRA)

Cascading is performed even in the absence of "cascade" parameter. ------------------------------------------------------------------ Key: HHH-3312 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3312 Project: Hibernate3 Issue Type: Bug Components: core Reporter: Gregory Klimov Attachments: test.zip Test case in attachment shows that in both cases: unidirectional one-to-many and bidirectional many-to-many cascading operations are done regardless of "cascade" parameter presence. Cascading must not happen if "cascade" parameter is omitted. -- 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, 11 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3324) Support many-to-one multiple -property-ref

by Sonix Legend (JIRA)

Support many-to-one multiple -property-ref ------------------------------------------ Key: HHH-3324 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3324 Project: Hibernate3 Issue Type: Improvement Components: core Environment: Hibernate 3.2.6ga, Oracle 9.2 Reporter: Sonix Legend I have a problem in my current project. For example, I have a table which name is "A". create table A ( ... varchar2(10) a1, varchar2(10) a2, ... ); And another table which name is "B". create table B ( ... varchar2(10) b1 primary key, varchar2(10) b2 primary key, ... ); alter table B add constraint PK_B primary key (b1, b2); Then I generated two hibernate mapping files by hibernate tools. A.hbm.xml ... <class name="A" table="A"> ... <property name="a1" type="string"> <column name="a1" length="10" /> </property> <property name="a2" type="string"> <column name="a2" length="10" /> </property> ... </class> ... B.hbm.xml ... <class name="B" table="B"> ... <composite-id name="id" class="C"> <key-property name="b1" type="string"> <column name="b1" length="10" /> </key-property> <key-property name="b2" type="string"> <column name="b2" length="10" /> </key-property> </composite-id> ... </class> ... Now I wanted A "left outer join" B, so I added a "many-to-one" element into "A.hbm.xml". <many-to-one name="b" class="B"> <column name="a1" /> <column name="a2" /> </many-to-one> And I added a "one-to-many" element into "B.hbm.xml". <set name="a"> <key> <column name="a1" /> <column name="a2" /> </key> <one-to-many class="A" /> </set> I writed a HQL. "select a, b from A as a left outer join a.b as b where a.a1 = 'test1' and a.a2 = 'test2' and (b is null or b.b1 = 'test3')" When the hibernate loads the mapping files, there was not an error. But when the query executes, it report a error "column ambiguous defined". I got the sql that generated from hql by p6spy. select ... a_0.a1, a_0.a2, a_0.a1, a_0.a2, ... b_0.b1, b_0.b2, ... from ... So the error wake me up to the "a1" and "a2" columns had repeated in the "A.hbm.xml" file. The "many-to-one" element only have a "property-ref" attribute. But the "a1" and "a2" fields are used at the "where" condition or other tables associate, and I can't modify the "A" table because other systems uses it. I hope you can resolve the problem with any method. I'm apologize for my English. So sorry. Thanks -- 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, 11 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3323) Error in SchemaUpdate using HSQLDialect with non Integer or Long primary keys

by Jan Justesen (JIRA)

Error in SchemaUpdate using HSQLDialect with non Integer or Long primary keys ----------------------------------------------------------------------------- Key: HHH-3323 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3323 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.6 Environment: Hibernate 3.2.6 and Hibernate Annotations 3.3.1 on HSQL DB Reporter: Jan Justesen >From HSQL manual: "Only one identity column is allowed in each table. Identity columns are autoincrement columns. They must be of INTEGER or BIGINT type" When using HSQLDialect, the following code fails during schema creation: @Entity public class Test { @Id @GeneratedValue(strategy = GenerationType.AUTO) private Short id; } Log output: ERROR org.hibernate.tool.hbm2ddl.SchemaUpdate - Unsuccessful: create table Test (id smallint generated by default as identity (start with 1), primary key (id)) ERROR org.hibernate.tool.hbm2ddl.SchemaUpdate - Wrong data type: ID in statement [create table Test (id smallint generated by default as identity (start with 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, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3326) Temporary tables created in SQLServer use the collation for tempdb, not the application database

by David Good (JIRA)

Temporary tables created in SQLServer use the collation for tempdb, not the application database ------------------------------------------------------------------------------------------------ Key: HHH-3326 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3326 Project: Hibernate3 Issue Type: Patch Affects Versions: 3.2.4.sp1 Environment: SQLServer (All versions) Reporter: David Good Attachments: Dialect.java, SQLServerDialect.java, Table.java The use of temporary tables for updates in SQLServer will fail if tempdb uses a different collation to the application db. Specifically, comparisons between the primary table columns and the temporary table columns fail. It is unclear to me under what circumstances a temporary table is created, so I'm afraid no test case is attached. I do however attach modified versions of the following classes: org.hibernate.mapping.Table org.hibernate.dialect.Dialect org.hibernate.dialect.SQLServerDialect These resolve the issue, but the solution may not be the most optimal possible, as it involves intervention in a specific position (between the datatype declaration and any nullability clause) -- 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, 11 months

1
3
0 / 0

[Hibernate-JIRA] Created: (ANN-731) Fix for ANN-548 breaks @SqlResultSetMapping

by Lars Heyden (JIRA)

Fix for ANN-548 breaks @SqlResultSetMapping ------------------------------------------- Key: ANN-731 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-731 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.1.GA Environment: Hibernate 3.2.6.ga, HEM3.3.2.ga, HAN3.3.1.ga, JSE 1.6, DB2 8.2 Reporter: Lars Heyden The generation of synthetic properties for non-PK-references introduces with ANN-548 makes it impossible to use @SqlResultSetMapping. When doing a native query Hibernate tries to read values for these properties out of columns (column aliases) that do not exist. -- 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, 11 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues June 2008