November 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-974) Rename ClassNavigator to InstanceInitalizer

by Hardy Ferentschik (JIRA)

Rename ClassNavigator to InstanceInitalizer ------------------------------------------- Key: HSEARCH-974 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-974 Project: Hibernate Search Issue Type: Improvement Components: engine Affects Versions: 4.0.0.CR1 Reporter: Hardy Ferentschik Fix For: 4.0.0.CR2 _ClassNavigator_ implies more of a reflection API. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HV-526) Bug in Hibernate Validator ? Stackoverflow on @Required

by Vincent LE HELLIDU (JIRA)

Bug in Hibernate Validator ? Stackoverflow on @Required ------------------------------------------------------- Key: HV-526 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-526 Project: Hibernate Validator Issue Type: Bug Components: annotation-processor, engine, validators Affects Versions: 4.2.0.Final, 4.1.0.Final Environment: Tests done on Hibernate 3.6.5 final and Hibernate 3.6.7 final with MySQL 5.1 Reporter: Vincent LE HELLIDU Attachments: HibernateTest.zip Hello, I have a stackoverflow error in the following test case. This test case define a bidirectionnal relation OneToMany between A and B where at least one B is Required in the collection A.getB(). The goal of the test case is to delete some B retreived from database. My conclusion: it does not work when retreiving B directly - see deleteFromB() - but it works when getting B from the retreived A - see deleteFromA(). In class MainAB.java, if I use deleteFromA() method, the deletion of "B"s works but deleteFromB() causes a stackoverflow. I think it is a bug on Hibernate or Hibernate Validator but I am not sure, perhaps it is normal with this mapping ? If someone can guide me. Best regards, Vincent ORIGINAL POST : https://forum.hibernate.org/viewtopic.php?f=9&t=1012855 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-960) Index.UN_TOKENIZED overrides other tokenized fields that share the same name

by John-Michael Au (JIRA)

Index.UN_TOKENIZED overrides other tokenized fields that share the same name ---------------------------------------------------------------------------- Key: HSEARCH-960 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-960 Project: Hibernate Search Issue Type: Bug Components: mapping Affects Versions: 3.4.0.Final Environment: 3.4.0 Final Reporter: John-Michael Au Marking one field as un-tokenized causes all other fields with the same names to be un-tokenized. i.e. @Field(name = "simple_search", index = Index.UN_TOKENIZED, store = Store.NO) private String string; @Field(name = "simple_search", index = Index.TOKENIZED, store = Store.NO) private String string2; The resulting behaviour is that "simple_search" will be made up of un-tokenized 'string' and 'string2' values, even though 'string2' was specified to be tokenized. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
17
0 / 0

[Hibernate-JIRA] Created: (HHH-6463) hbm2ddl and Oracle DB: Found: number, expected: boolean

by Thomas (JIRA)

hbm2ddl and Oracle DB: Found: number, expected: boolean ------------------------------------------------------- Key: HHH-6463 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6463 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 4.0.0.Beta1 Reporter: Thomas As described in this forum topic: https://forum.hibernate.org/viewtopic.php?f=1&t=1011905&start=0 Since version 4 Hibernate (hbm2ddl) cannot map a boolean field in a JPA entity to a column with type number(1,0) in Oracle DB. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

6
12
0 / 0

[Hibernate-JIRA] Created: (HHH-6821) Upgrade to jboss-logging-tools 1.0.0.CR5

by Strong Liu (JIRA)

Upgrade to jboss-logging-tools 1.0.0.CR5 ---------------------------------------- Key: HHH-6821 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6821 Project: Hibernate Core Issue Type: Task Reporter: Strong Liu Assignee: Strong Liu Fix For: 4.0.0.next there is a issue within the released jboss-logging-tools 1.0.0.CR4 which causes logging message is not output correctly, which is fixed in thsi CR5 release -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-973) Make sure Hibernate Search build against JDK 7

by Emmanuel Bernard (JIRA)

Make sure Hibernate Search build against JDK 7 ---------------------------------------------- Key: HSEARCH-973 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-973 Project: Hibernate Search Issue Type: Task Reporter: Emmanuel Bernard -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

3
3
0 / 0

[Hibernate-JIRA] Created: (ANN-644) @ManyToMany appears to ALWAYS generate a left outer join SQL

by Barry Davies (JIRA)

@ManyToMany appears to ALWAYS generate a left outer join SQL ------------------------------------------------------------ Key: ANN-644 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-644 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.0.ga Reporter: Barry Davies Priority: Minor Attachments: files.zip A collection mapping created using the @ManyToMany JPA annotation appears to create a left outer join SQL regardless of whether the joinColumn or inverseJoinColumn are marked nullable or not. This might be in error. Emmanuel asked for a JIRA issue to be created, so here we are. I have attached some files that can recreate what I believe to be the issue. The forum topic where this was brought up is: http://forum.hibernate.org/viewtopic.php?t=977936 -- 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

13 years, 2 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3160) Support one-to-many list associations with constraints on both (owner_id, position) and (child_id)

by Gail Badner (JIRA)

Support one-to-many list associations with constraints on both (owner_id, position) and (child_id) -------------------------------------------------------------------------------------------------- Key: HHH-3160 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3160 Project: Hibernate3 Issue Type: Sub-task Reporter: Gail Badner Assignee: Gail Badner The logic used for removing entities from one-to-many list associations can cause ConstraintViolationException will be thrown if there are constraints on both (owner_id, position) and (child_id) in the "collection table". If the association is on a join table, the "collection table" is the join table; otherwise, the "collection table" is the child entity table.. Currently, SchemaExport does not put a constraint on (owner_id, position) when exporting one-to-many list associations on a foreign key. SchemaExport should be updated to also export this constraint. See HHH-1268 for a description of how to reproduce this issue. For one-to-many list associations on a foreign key, the workaround is to either define the constraint on (owner_id, position) in the child entity table as deferred. If this is not on option for a particular Dialect, the constraint on (owner_id, position) will have to be excluded. For a one-to-many list association on a join table, the workaround is to either define the constraint on (child_id) in the join table as deferred. If this is not on option for a particular Dialect, the constraint on (child_id) will have to be excluded. -- 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

13 years, 2 months

4
6
0 / 0

[Hibernate-JIRA] Created: (HHH-6818) update dependencies management

by Strong Liu (JIRA)

update dependencies management ------------------------------ Key: HHH-6818 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6818 Project: Hibernate Core Issue Type: Task Reporter: Strong Liu Assignee: Strong Liu Fix For: 4.0.0.next in favor of transitive dependencies -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-6807) org.hibernate.test.lob.LobMergeTest fail on Sybase ASE

by Michael Ren (JIRA)

org.hibernate.test.lob.LobMergeTest fail on Sybase ASE ------------------------------------------------------ Key: HHH-6807 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6807 Project: Hibernate Core Issue Type: Bug Environment: Hiberante 4.0 CR5, Sybase ASE 15.7 Reporter: Michael Ren Priority: Minor This test needs ASE to support LobValueChangePropogation. Skip it as ASE cannot support it currently. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues November 2011