July 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-243) Extrapolate the shard number in properties {shard_nbr}

by Emmanuel Bernard (JIRA)

Extrapolate the shard number in properties {shard_nbr} ------------------------------------------------------ Key: HSEARCH-243 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-243 Project: Hibernate Search Issue Type: Improvement Reporter: Emmanuel Bernard Priority: Minor hibernate.search.Item.indexName = Item{shard_nbr} equivalent to hibernate.search.Item.0.indexName Item0 hibernate.search.Item.1.indexName Item1 -- 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, 8 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HBX-1077) exclude-unlisted-classes in persestence.xml doesn't work for tools

by Antony Stubbs (JIRA)

exclude-unlisted-classes in persestence.xml doesn't work for tools ------------------------------------------------------------------ Key: HBX-1077 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1077 Project: Hibernate Tools Issue Type: Bug Affects Versions: 3.2.2 Environment: n/a Reporter: Antony Stubbs Similar to EJB-212, exclude-unlisted-classes doesnt' seem to work for hibernate tools. I seem to either have to list a .hbm file in the configuration, or include the entity class in the persistence.xml. Although, Eclipse JPA perspective picks up the mapping, when the entity is not listed anywhere and only having exclude-unlisted-classes set to false. When trying to use tools with just exclude-unlisted-classes set, I get "EntityName is not mapped" and no entities appear under the console configuration. -- 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, 8 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-241) initialize methods taking Properties cannot list available properties

by Emmanuel Bernard (JIRA)

initialize methods taking Properties cannot list available properties --------------------------------------------------------------------- Key: HSEARCH-241 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-241 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.1.0.Beta1 Reporter: Emmanuel Bernard Fix For: 3.1.0.Beta2 -- 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, 8 months

2
3
0 / 0

[Hibernate-JIRA] Created: (ANN-759) @NotFound( action = NotFoundAction.IGNORE ) doesn't behave as expected.

by sam doyle (JIRA)

@NotFound( action = NotFoundAction.IGNORE ) doesn't behave as expected. ----------------------------------------------------------------------- Key: ANN-759 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-759 Project: Hibernate Annotations Issue Type: Bug Reporter: sam doyle This scenario causes still results in an ENFE when applied to the method. @OneToOne(cascade = CascadeType.ALL, fetch = FetchType.LAZY, optional = false) @PrimaryKeyJoinColumn @NotFound( action = NotFoundAction.IGNORE ) public X get() Invoking this method can still result in an ENFE being raised?? Is there specific cases I should know about when this works and does not work? It isn't documented. -- 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, 8 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1570) criteria-api: filtering by key-many-to-one causes invalid sql

by Marcio Carvalho (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1570?page=c... ] Marcio Carvalho commented on HHH-1570: -------------------------------------- Any news on this issue? Please, tell me Hasan, what have you left to fix in the AnnotationBinder class from your patch? I've searched at the hibernate core and annotations changelog and haven't found any fixes for this problem. Best regards, Marcio Carvalho. > criteria-api: filtering by key-many-to-one causes invalid sql > ------------------------------------------------------------- > > Key: HHH-1570 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1570 > Project: Hibernate3 > Issue Type: Bug > Components: query-criteria > Affects Versions: 3.1.2 > Reporter: Joris Verschoor > Attachments: hibernate.patch > > > We have a class Price that has a composite-id using a couple of key-properties and some key-many-to-ones) > One of those is "transportation", which has a many-to-one to transportationType > When we query using: criteria.add(Expression.eq("price.transportation.transportationType.id", transId);, we get an invalid SQL statement: The table of transportation was not selected. > I will try to make a testcase today or tomorrow, depending on my schedule.. Things will be more clear by then... > We have created a work-around, by mapping the transportationID twice: once in key-property, and once as a many-to-one. (instead of one key-many-to-one) -- 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, 8 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-244) Abiltiy to ask SearchFactory for the analyzer of a given class

by Hardy Ferentschik (JIRA)

Abiltiy to ask SearchFactory for the analyzer of a given class --------------------------------------------------------------- Key: HSEARCH-244 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-244 Project: Hibernate Search Issue Type: Task Components: engine Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 3.1.0.Beta2 You want to be able to do something like this: Analyzer analyzer = searchFactory.getAnalyzer(Class); -- 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, 8 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2604) Isolator.JdbcDelegate masks the exception if it isn't possible to open a connection.

by Tushar (JIRA)

Isolator.JdbcDelegate masks the exception if it isn't possible to open a connection. ------------------------------------------------------------------------------------ Key: HHH-2604 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2604 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.4 Environment: Hibernate 3.2.2ga Reporter: Tushar Priority: Minor A defect in Isolator.JdbcDelegate makes it throw the wrong exception - a NullPointerException - that masks the true exception. In my case it was an UnsupportedOperationException("The user must supply a JDBC connection"). The trouble is at the start of Isolator.JdbcDelegate.delegateWork(...): {code} 174 public void delegateWork(IsolatedWork work, boolean transacted) throws HibernateException { 175 Connection connection = null; 176 boolean wasAutoCommit = false; 177 try { 178 connection = session.getBatcher().openConnection(); {code} If there is a failure opening a connection on line 178, the finally clause is executed. The finally clause needs the connection, which of course is null :-) -- 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, 8 months

6
10
0 / 0

[Hibernate-JIRA] Updated: (HBX-524) Reverse of one-to-one relationships

by Alexander Buttau (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-524?page=co... ] Alexander Buttau updated HBX-524: --------------------------------- Attachment: patch.txt Hier is a patch-file to teach reverse engineering tool to generate a one-to-one relation > Reverse of one-to-one relationships > ----------------------------------- > > Key: HBX-524 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-524 > Project: Hibernate Tools > Issue Type: Bug > Components: reverse-engineer > Affects Versions: 3.1beta2 > Environment: HIbernate 3.1, Oracle 9i > Reporter: Andrea Cattani > Attachments: patch.txt > > > Hi, > I've posted this issue to the forum and got this response from Max, Hibernate Team: > "the reveng tools does not detect this as a one-to-one. it probably could, so add a request/patch to jira." > The problem I've faced is the following: > I have two tables, let's say > - table A with column ID (PK) and other fields > - table B with column ID (PK) and other fields > table B has a foreign key constraint against table A, from column ID to column ID (one-to-one) > When I reverese the tables with the HibernateTools I have such a resultant mapping for table B: > <class name="B" table="B" schema="SCHEMA"> > <id name="id" type="string"> > <column name="ID" length="12" /> > <generator class="assigned" /> > </id> > <[b]many-to-one name[/b]="a" class="A" update="false" insert="false" fetch="select"> > <column name="ID" length="12" not-null="true" unique="true" /> > </many-to-one> > .... > And this one for table A: > <class name="A" table="A" schema="SCHEMA"> > <id name="id" type="string"> > <column name="ID" length="12" /> > <generator class="assigned"/> > </id> > <set name="b" inverse="true"> > <key> > <column name="ID" length="12" not-null="true" unique="true" /> > </key> > <[b]one-to-many[/b] class="B" /> > </set> > </class> > while I was expecting something like: > [i]<one-to-one name="a" class="A" constrained="true"/>[/i] > in table B, and the same (or nothing) in table A > Thank you > Andi -- 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, 8 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HBX-524) Reverse of one-to-one relationships

by Alexander Buttau (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-524?page=co... ] Alexander Buttau commented on HBX-524: -------------------------------------- Hi Marcio, thanks for your code it works ... ... and to teach Hibernate-Tools to generate a one-to-one mapping you must create a new template "one-to-one.hbm.tpl", which is similat to "many-to-one.hbm.ftl" and looks like this: <one-to-one name="${property.name}" class="${c2j.getJavaTypeName(property, false)}" <#if !property.updateable> update="false" </#if> <#if !property.insertable> insert="false" </#if> <#if !property.basicPropertyAccessor> access="${property.propertyAccessorName}" </#if> <#if property.cascade != "none"> cascade="${property.cascade}" </#if> <#assign fetchmode = c2h.getFetchMode(property)> <#if fetchmode != "default"> fetch="${fetchmode}" </#if> <#if !property.optimisticLocked> optimistic-lock="false" </#if> <#if property.value.hasFormula()> <#assign formula = c2h.getFormulaForProperty(property)> <#if formula> formula="${formula.text}" </#if> </#if> > </one-to-one> > Reverse of one-to-one relationships > ----------------------------------- > > Key: HBX-524 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-524 > Project: Hibernate Tools > Issue Type: Bug > Components: reverse-engineer > Affects Versions: 3.1beta2 > Environment: HIbernate 3.1, Oracle 9i > Reporter: Andrea Cattani > > Hi, > I've posted this issue to the forum and got this response from Max, Hibernate Team: > "the reveng tools does not detect this as a one-to-one. it probably could, so add a request/patch to jira." > The problem I've faced is the following: > I have two tables, let's say > - table A with column ID (PK) and other fields > - table B with column ID (PK) and other fields > table B has a foreign key constraint against table A, from column ID to column ID (one-to-one) > When I reverese the tables with the HibernateTools I have such a resultant mapping for table B: > <class name="B" table="B" schema="SCHEMA"> > <id name="id" type="string"> > <column name="ID" length="12" /> > <generator class="assigned" /> > </id> > <[b]many-to-one name[/b]="a" class="A" update="false" insert="false" fetch="select"> > <column name="ID" length="12" not-null="true" unique="true" /> > </many-to-one> > .... > And this one for table A: > <class name="A" table="A" schema="SCHEMA"> > <id name="id" type="string"> > <column name="ID" length="12" /> > <generator class="assigned"/> > </id> > <set name="b" inverse="true"> > <key> > <column name="ID" length="12" not-null="true" unique="true" /> > </key> > <[b]one-to-many[/b] class="B" /> > </set> > </class> > while I was expecting something like: > [i]<one-to-one name="a" class="A" constrained="true"/>[/i] > in table B, and the same (or nothing) in table A > Thank you > Andi -- 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, 8 months

1
0
0 / 0

[Hibernate-JIRA] Created: (ANN-462) Support @BridgeField annotated annotation

by Emmanuel Bernard (JIRA)

Support @BridgeField annotated annotation ----------------------------------------- Key: ANN-462 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-462 Project: Hibernate Annotations Type: New Feature Components: lucene 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

17 years, 8 months

2
4
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 July 2008