May 2012 - 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, 8 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, 8 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, 8 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-6950) Bogus string replacement in SQLServer2005Dialect.insertRowNumberFunction()

by Roberto Italia (JIRA)

Bogus string replacement in SQLServer2005Dialect.insertRowNumberFunction() -------------------------------------------------------------------------- Key: HHH-6950 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6950 Project: Hibernate Core Issue Type: Bug Components: core, query-sql Affects Versions: 4.0.0.Final Environment: Hibernate 4.0.0, SQLServer 2008R2 Reporter: Roberto Italia The fix for HHH-6849 introduced a problem with column-names containing the character sequence 'from'. For example, assume the string builder contains the following query before the call to SQLServer2005Dialect.insertRowNumberFunction() (formatted for better reading): select persistent0_.rid as rid1688_, persistent0_.deviationfromtarget as deviati16_1688_, persistent0_.sortindex as sortindex1688_ from m_evalstate persistent0_ where persistent0_.customerid=? After the call to SQLServer2005Dialect.insertRowNumberFunction(), the string builder contains: select persistent0_.rid as rid1688_, persistent0_.deviatio, ROW_NUMBER() OVER (ORDER BY CURRENT_TIMESTAMP) as __hibernate_row_nr__nfromtarget as deviati16_1688_, persistent0_.sortindex as sortindex1688_ from m_evalstate persistent0_ where persistent0_.customerid=? But the intention of the fix was: select persistent0_.rid as rid1688_, persistent0_.deviationfromtarget as deviati16_1688_, persistent0_.sortindex as sortindex1688_, ROW_NUMBER() OVER (ORDER BY CURRENT_TIMESTAMP) as __hibernate_row_nr__ from m_evalstate persistent0_ where persistent0_.customerid=? A fix would be the following code instead of the current: final String myFrom = " " + FROM + " "; int selectEndIndex = sql.indexOf( myFrom ); sql.insert( selectEndIndex, ", ROW_NUMBER() OVER (" + orderby + ") as __hibernate_row_nr__" ); -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

4
5
0 / 0

[Hibernate-JIRA] Created: (HHH-7319) ServiceContributingIntegrator do not have access to the configuration and cannot adjust service registration accordingly

by Emmanuel Bernard (JIRA)

ServiceContributingIntegrator do not have access to the configuration and cannot adjust service registration accordingly ------------------------------------------------------------------------------------------------------------------------ Key: HHH-7319 URL: https://hibernate.onjira.com/browse/HHH-7319 Project: Hibernate ORM Issue Type: Improvement Reporter: Emmanuel Bernard In Hibernate OGM, I don't want to set my custom service initiators unless I know it is explicitly being used. I cannot do that today because ServiceContributingIntegrator does not have access to the configuration. I had to write all my service initiators so that they look at the configuration and delegate to the "default" service initiator. That's a lot of redundant code. I wonder if we can do better. See https://github.com/hibernate/hibernate-ogm/blob/master/hibernate-ogm-core... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

2
4
0 / 0

[Hibernate-JIRA] Commented: (HHH-1775) collection batch fetching

by Guenther Demetz (JIRA)

[ https://hibernate.onjira.com/browse/HHH-1775?page=com.atlassian.jira.plug... ] Guenther Demetz commented on HHH-1775: -------------------------------------- https://github.com/hibernate/hibernate-orm/pull/337 > collection batch fetching > ------------------------- > > Key: HHH-1775 > URL: https://hibernate.onjira.com/browse/HHH-1775 > Project: Hibernate ORM > Issue Type: Improvement > Components: core > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Priority: Minor > Fix For: hql+collection > > > I have code local on my box to support "peeking" into the second level cache when determining whether to add a particular entity/collection key to a batch load request. If the given key is contained in the second level cache, then do not batch fetch the entity/collection as it will be initialized from second level cache on access. > However, there are still large inefficiencies when performing this for collections; the biggest of which currently is the fact that we retreive a IdentityMap.entrySet for each and ever call to determine a collectiomn fetch batch. For performance reasons, we should align this with how entity batches are handled where the entity keys considered to be "batch loadable" are tracked seperately on the BatchFetchQueue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 8 months

1
0
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, 8 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, 8 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, 8 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, 8 months

3
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues May 2012