December 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-952) Ability to configure different IndexDeletionPolicies to handle problems with NFS

by Arnab Ghosh (JIRA)

Ability to configure different IndexDeletionPolicies to handle problems with NFS --------------------------------------------------------------------------------- Key: HSEARCH-952 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-952 Project: Hibernate Search Issue Type: New Feature Components: directory provider Reporter: Arnab Ghosh -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-5) Only index an entity when it's index properties have physically changed

by Emmanuel Bernard (JIRA)

Only index an entity when it's index properties have physically changed ----------------------------------------------------------------------- Key: HSEARCH-5 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-5 Project: Hibernate Search Type: New Feature Components: engine Reporter: Emmanuel Bernard Priority: Minor -- 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

12 years, 7 months

3
11
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-975) JGroups version needed for Infinispan is not fully compatible with the one expected by the JGroups backend

by Sanne Grinovero (JIRA)

JGroups version needed for Infinispan is not fully compatible with the one expected by the JGroups backend ---------------------------------------------------------------------------------------------------------- Key: HSEARCH-975 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-975 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.4.1.Final, 3.4.0.Final Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 3.4.2 This does not affect Hibernate Search > 3.4 Previously we needed to compile using an older version of JGroups to maintain Java5 compatibility in the _hibernate-search_ module; it turns out this version is not API compatible with the one we need for the Infinispan integration bits, making it harder to use both clustering components at the same time. I'm not sure why some users reported it to fail only "occasionally" - I guess they're having both on classpath. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
3
0 / 0

[Hibernate-JIRA] Created: (ANN-809) Composite Key which contains a discriminator causes "Repeated Column" errors

by Pasi Orovuo (JIRA)

Composite Key which contains a discriminator causes "Repeated Column" errors ---------------------------------------------------------------------------- Key: ANN-809 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-809 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.4.0.GA Environment: Hibernate version: 3.3.1 GA Application Server: Glassfish V3 Prelude Database: Oracle 9i Reporter: Pasi Orovuo Attachments: ItemInfo.zip See this forum post for background: http://forum.hibernate.org/viewtopic.php?t=995693 Annotations does not seem to have a possibility to define "insert = false" on a discriminator column, as mentioned in the following bug: http://opensource.atlassian.com/projects/hibernate/browse/HB-1149 Sources of classes that demonstrate the problem in above forum case 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

12 years, 7 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HHH-6849) SQLServer2005Dialect changes the order of selected columns when using pagination

by Hardy Ferentschik (JIRA)

SQLServer2005Dialect changes the order of selected columns when using pagination -------------------------------------------------------------------------------- Key: HHH-6849 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6849 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 4.0.0.CR6 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 4.0.0.next The _SQLServer2005Dialect_ uses _ROW_NUMBER()_ to generate a limit string. However, it prepend the row number column instead of appending it (or not returning it at all). This let for example _PaginationTest#testLimitOffset_ fail. See also HHH-2655. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HV-484) Refactor package organisaton to clearly separate spi, public and private APIs

by Hardy Ferentschik (JIRA)

Refactor package organisaton to clearly separate spi, public and private APIs ----------------------------------------------------------------------------- Key: HV-484 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-484 Project: Hibernate Validator Issue Type: Task Components: engine Affects Versions: 4.1.0.CR1 Reporter: Hardy Ferentschik Fix For: 4.x Aligning with the other Hibernate projects. -- 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

12 years, 7 months

3
13
0 / 0

[Hibernate-JIRA] Created: (HHH-6310) SQLServer2005Dialect produced select statement with a distinct keyword within an aggregate function does not work

by Yoryos Valotassios (JIRA)

SQLServer2005Dialect produced select statement with a distinct keyword within an aggregate function does not work ----------------------------------------------------------------------------------------------------------------- Key: HHH-6310 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6310 Project: Hibernate Core Issue Type: Bug Components: core, query-sql Affects Versions: 3.6.5 Reporter: Yoryos Valotassios As discussed on HHH-5715, the SQLServer2005Dialect does not handle the right the distinct keyword when that is inside an aggregate function. -- 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

12 years, 7 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-6728) SQLServer2005Dialect - Paging doesn't work with UPPERCASE colums in a case sensitive database

by Andrei Zaitsev (JIRA)

SQLServer2005Dialect - Paging doesn't work with UPPERCASE colums in a case sensitive database --------------------------------------------------------------------------------------------- Key: HHH-6728 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6728 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 4.0.0.CR4, 3.6.7 Environment: MS SQL Server 2008 with Latin1_General_CS_AS collation Reporter: Andrei Zaitsev SQLServer2005Dialect changes the original query in getLimitString() to lowercase. That leads to SQLGrammarExcepton with case sensitive collation and not-lowercase table and column names. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

4
5
0 / 0

[Hibernate-JIRA] Created: (HHH-3958) Superfluous generated updates cause Violation of UNIQUE KEY constraint

by Guenther Demetz (JIRA)

Superfluous generated updates cause Violation of UNIQUE KEY constraint ---------------------------------------------------------------------- Key: HHH-3958 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3958 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: 3.3.1 GA, SQLServer 2008 Reporter: Guenther Demetz Priority: Minor Attachments: Testcase.jar When deleting a entire closure of objects associated over @ManyToOne within one single transaction, then on commit the FlushEventListener creates update statements on objects which are going to be deleted anyway. These update statements seems not only be useless, in certain scenarios they lead to Constraint Violation Exceptions, see the example here: @Entity public class A { public A() { } @Id @GeneratedValue private long oid; } @Entity @Table(uniqueConstraints = {@UniqueConstraint(columnNames={"assA_oid"})}) public class B { public B() {}; @Id @GeneratedValue private long oid; @javax.persistence.ManyToOne protected A assA = null; } A a1 = new A(); em.persist(a1); A a2 = new A(); em.persist(a2); B b1 = new B(); b1.assA = a1; // set unique association B b2 = new B(); b2.assA = a2; // set unique association em.persist(b1); em.persist(b2); em.getTransaction().commit(); em.getTransaction().begin(); em.remove(a1); em.remove(a2); em.remove(b1); em.remove(b2); em.getTransaction().commit(); // p6spy report: // update B set assA_oid='',version=0 where oid=1 and version=0 // update B set assA_oid='',version=0 where oid=2 and version=0 --> this raises "Violation of UNIQUE KEY constraint on all DB's which don't allow multiple null values in a unique index See testcase in attachment -- 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

12 years, 7 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HBX-1194) hibernate.hbm2ddl.auto=update works with multiple oracle schemas

by Vyacheslav (JIRA)

hibernate.hbm2ddl.auto=update works with multiple oracle schemas ---------------------------------------------------------------- Key: HBX-1194 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1194 Project: Hibernate Tools Issue Type: Bug Environment: <org.hibernate.core.version>3.6.8.Final</org.hibernate.core.version> <org.hibernate.entitymanager.version>3.6.8.Final</org.hibernate.entitymanager.version> <org.hibernate.validator.version>4.0.2.GA</org.hibernate.validator.version> Reporter: Vyacheslav if privileges are set hbm2ddl schema update searches for created tables in all db schemas which can be accessed, not only in current one. Don't create tables needed in current schema and fails to alter them. http://community.jboss.org/thread/175353?tstart=0 info level log viewing says during schema update that: table found: REALTY.DATA_EXCH_LOG table found: REALTY_NEW.FILES_AUD table found: SYSTEM.PROPERTIES_AUD table found: SYSTEM.REVISIONS Script see different database schemas and creating AUD tables in one schema scanning others: table found: REALTY.REF_RSR_ORDER_TYPES table found: REALTY_NEW.REF_RSR_ORDER_TYPES_AUD After hbm2ddl cannot find tables created in other schemas: Unsuccessful: alter table PROPERTIES_AUD add BASE_TYPE_ID number(10,0) not null Current schema is REALTY_NEW Very strange behaviour. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues December 2011