June 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2933) DialectFactory dialects should be in a properties file

by Mikael Kopteff (JIRA)

DialectFactory dialects should be in a properties file ------------------------------------------------------ Key: HHH-2933 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2933 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.5 Reporter: Mikael Kopteff Currently the DialectFactory has the static attribute MAPPERS, that hold the dialects. If the dialect is not found, Hibernate will throw an exception. There is already an TODO tag, set for this.So, could this be possibly done, so that the values really are a) in a properties file or b)additions could be made to the map programmaticaly by users. This would be more flexible for advanced users, that work with experimental jdbc drivers(that don't return a standard name for the database). The current trunk version of DialectFactory: // TODO : this is the stuff it'd be nice to move to a properties file or some other easily user-editable place private static final Map MAPPERS = new HashMap(); static { MAPPERS.put( "HSQL Database Engine", new VersionInsensitiveMapper( "org.hibernate.dialect.HSQLDialect" ) ); MAPPERS.put( "H2", new VersionInsensitiveMapper( "org.hibernate.dialect.H2Dialect" ) ); MAPPERS.put( "MySQL", new VersionInsensitiveMapper( "org.hibernate.dialect.MySQLDialect" ) ); etc..... -- 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

17 years, 6 months

3
23
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-77) Expose configuration settings through API

by Christian Bauer (JIRA)

Expose configuration settings through API ----------------------------------------- Key: HSEARCH-77 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-77 Project: Hibernate Search Issue Type: New Feature Components: engine Reporter: Christian Bauer Priority: Minor I'd like to access my configuration settings, probably on a SearchFactory. I want to be able to e.g. get the hibernate.search.worker.batch_size to adjust my loops dynamically. I imagine there are a few other usecases, for example, avoid hardcoding the analyzer for hit highlighting but using the same as the HSearch indexer. -- 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

17 years, 6 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3310) Using Nested DetachedCriteria (Sub-Selects) throwing NullPointerException

by Roshan Dawrani (JIRA)

Using Nested DetachedCriteria (Sub-Selects) throwing NullPointerException ------------------------------------------------------------------------- Key: HHH-3310 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3310 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.5 Environment: Hibernate 3.2.5, Oracle 10g Reporter: Roshan Dawrani Attachments: Nested_Subselects.zip Hi, We have come across an issue with the usage of nested subselects in the sql query with hibernate 3.2.5. We get the following exception when there is more than one level of sub-selects in the query : ---------------------------------------------------------------------------------------------------------------------- java.lang.NullPointerException at org.hibernate.criterion.SubqueryExpression.getTypedValues(SubqueryExpression.java:80) at org.hibernate.loader.criteria.CriteriaQueryTranslator.getQueryParameters(CriteriaQueryTranslator.java:251) at org.hibernate.criterion.SubqueryExpression.toSqlString(SubqueryExpression.java:55) at org.hibernate.loader.criteria.CriteriaQueryTranslator.getWhereCondition(CriteriaQueryTranslator.java:334) at org.hibernate.loader.criteria.CriteriaJoinWalker.<init>(CriteriaJoinWalker.java:71) at org.hibernate.loader.criteria.CriteriaLoader.<init>(CriteriaLoader.java:67) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1550) at org.hibernate.impl.CriteriaImpl.list(CriteriaImpl.java:283) at NestedDetachedCriteriaTest.testNestedDetachedCriteria(Unknown Source) ---------------------------------------------------------------------------------------------------------------------- The actual query that gets fired is like: ---------------------------------------------------------------------------------------------------------------------- select this_.name as y0_ from cat this_ where this_.name = (select this0__.name as y0_ from cat this0__ where this0__.parent_id = (select this0__.parent_id as y0_ from cat this0__ where this0__.name = (select this0__.name as y0_ from cat this0__ where this0__.cat_id = ?))) ---------------------------------------------------------------------------------------------------------------------- We investigated the issue and have fixed it by making some changes in org.hibernate.criterion.SubqueryExpression class. The attached file has the following contents: 1. SubqueryExpression.java - Fix we have made to SubqueryExpression class. 2. NestedDetachedCriteriaTest.zip - A test case to highlight the nested sub-select issue (testNestedDetachedCriteria). Regards, Roshan -- 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

17 years, 6 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-75) Use FieldSelector to filter returned Fields

by Emmanuel Bernard (JIRA)

Use FieldSelector to filter returned Fields ------------------------------------------- Key: HSEARCH-75 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-75 Project: Hibernate Search Issue Type: Improvement Components: engine Reporter: Emmanuel Bernard Priority: Minor Might be useful for projections, but is most likely unnecessary. -- 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

17 years, 6 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-175) USe domain specific annotations to plug custom bridges

by Emmanuel Bernard (JIRA)

USe domain specific annotations to plug custom bridges ------------------------------------------------------ Key: HSEARCH-175 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-175 Project: Hibernate Search Issue Type: New Feature Components: mapping Reporter: Emmanuel Bernard Fix For: 3.1.0 Use annotated annotations to declare bridges. Ie offer the same flexibility used by HSearch in @DateBridge -- 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

17 years, 6 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-219) Manual indexing strategy not implemented

by Fol De Rol (JIRA)

Manual indexing strategy not implemented ---------------------------------------- Key: HSEARCH-219 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-219 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.0.1.GA Reporter: Fol De Rol Priority: Blocker It looks impossible to implement fully manual strategy of indexing because of mandating event listeners to be registered. See org.hibernate.search.util.ContextHelper.java:25: //FIXME this sucks since we mandante the event listener use This causes a side effect to my application that stores an indication that the certain object is indexed in a child collection. So, when I complete manual indexing of an object, I add an element to this collection (actually, the cluster node identifier). This causes the Hibernate Search event listener to be triggered because the dependent collection has been modified which in its turn adds one more indexing job. Finally, I get an endless recursion. -- 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

17 years, 6 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-176) explicitly setting cfg property to lucene default

by Sanne Grinovero (JIRA)

explicitly setting cfg property to lucene default ------------------------------------------------- Key: HSEARCH-176 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-176 Project: Hibernate Search Issue Type: Improvement Components: directory provider, documentation Reporter: Sanne Grinovero Priority: Trivial As highlighted by previous patch for http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-153 , some configuration settings may be inherited, so it becomes difficult to explicitly set "default" settings on some settings as some values are "Integer.MAX_VALUE" or "null" but the cfg parser only accepts int values. Also if the users wants to explicitly set lucene defaults it needs to study the current lucene source code. I'm going to provide a patch to support besides current int values also "default" and "null" Strings, to explicitly configure H.Search to: "default" -> don't mess with the value "null" -> explicitly null the value Also someone may find it useful to represent "MAX_VALUE", what do you think about that, or other configurations that should be recognized? -- 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

17 years, 6 months

2
7
0 / 0

[Hibernate-JIRA] Created: (HHH-3343) Postgres Plus Dialect

by Jim Mlodgenski (JIRA)

Postgres Plus Dialect --------------------- Key: HHH-3343 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3343 Project: Hibernate3 Issue Type: New Feature Components: core Reporter: Jim Mlodgenski Attachments: postgresplus.patch Postgres Plus Advanced Server is an extension to PostgreSQL with added Oracle compatibility. Attached is a patch that implements a Postgres Plus Dialect with the Oracle compatible functions supported in Advanced Server matching the existing registered functions in the Oracle Dialect. -- 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

17 years, 6 months

2
6
0 / 0

[Hibernate-JIRA] Created: (HHH-3283) protect BulkManipulationTest#testInsertWithGeneratedTimestampVersion where Dialect#supportsParametersInInsertSelect == false

by Steve Ebersole (JIRA)

protect BulkManipulationTest#testInsertWithGeneratedTimestampVersion where Dialect#supportsParametersInInsertSelect == false ---------------------------------------------------------------------------------------------------------------------------- Key: HHH-3283 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3283 Project: Hibernate3 Issue Type: Improvement Components: testsuite Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.2.x, 3.3.0.CR2 Because the timestamp there is vm-based, that particular test is hosed if the dialect/jdbc-driver does not support defining parameters in the INSERT ... SELECT statement. -- 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

17 years, 6 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2883) ManyToMany doesn't work with polymorfism

by Dirk (JIRA)

ManyToMany doesn't work with polymorfism ---------------------------------------- Key: HHH-2883 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2883 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.4 Environment: Hibernate 3.2.4, Annotations 3.3.0, Entitymanager 3.3.0 Reporter: Dirk We tried out the SingleTable inheritance with a ManyToMany @Entity @Table(name="SHB_PRINCIPAL") @Inheritance(strategy=InheritanceType.SINGLE_TABLE) @DiscriminatorColumn(name="TYPE",discriminatorType=DiscriminatorType.INTEGER) @Cache(usage=CacheConcurrencyStrategy.TRANSACTIONAL) public class Principal implements Serializable { .... @Entity @DiscriminatorValue(PrincipalType.USER_NR) @Cache(usage=CacheConcurrencyStrategy.NONSTRICT_READ_WRITE) public class ApplicationUser extends Principal { private static final long serialVersionUID = 1L; @ManyToMany(fetch=FetchType.LAZY, cascade={CascadeType.PERSIST, CascadeType.MERGE, CascadeType.REFRESH}, targetEntity=Role.class) @JoinTable(name="SHB_PRINCIPAL_TO_PRINCIPAL", joinColumns=@JoinColumn(name="FROM_PRINCIPAL_ID"), inverseJoinColumns=@JoinColumn(name="TO_PRINCIPAL_ID")) private Set<Role> roles; @ManyToMany(fetch=FetchType.LAZY, cascade={CascadeType.PERSIST, CascadeType.MERGE, CascadeType.REFRESH}, targetEntity=ApplicationGroup.class) @JoinTable(name="SHB_PRINCIPAL_TO_PRINCIPAL", joinColumns=@JoinColumn(name="FROM_PRINCIPAL_ID"), inverseJoinColumns=@JoinColumn(name="TO_PRINCIPAL_ID")) private Set<ApplicationGroup> groups; @Entity @DiscriminatorValue(PrincipalType.GROUP_NR) @Cache(usage=CacheConcurrencyStrategy.NONSTRICT_READ_WRITE) public class ApplicationGroup extends Principal { private static final long serialVersionUID = 1L; @ManyToMany(fetch=FetchType.LAZY, cascade={CascadeType.PERSIST, CascadeType.MERGE, CascadeType.REFRESH}) @JoinTable(name="SHB_PRINCIPAL_TO_PRINCIPAL", joinColumns=@JoinColumn(name="TO_PRINCIPAL_ID"), inverseJoinColumns=@JoinColumn(name="FROM_PRINCIPAL_ID")) private Set<ApplicationUser> users; public ApplicationGroup() { super(); this.type = PrincipalType.GROUP; } public Set<ApplicationUser> getUsers() { return users; } public void setUsers(Set<ApplicationUser> users) { this.users = users; } } But in the groups and the roles of the user, hibernate returns all principals, not only the users or groups. In the query it's clear that the descriminator is NOT used. -- 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

17 years, 6 months

4
5
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 June 2008