May 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-760) ReaderProvider to not provide MultiSearchers

by Sanne Grinovero (JIRA)

ReaderProvider to not provide MultiSearchers -------------------------------------------- Key: HSEARCH-760 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-760 Project: Hibernate Search Issue Type: Task Reporter: Sanne Grinovero Fix For: 4.0.0.Alpha1 We still need to provide MultiSearchers, but this should do this at another level: the ReaderProvider interface needs to be coupled to the IndexManager ( see also HSEARCH-758 ) and thus be coupled to a single index. -- 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, 5 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-750) Have an IndexManager concept to manage IndexWriters, Readers and backend.

by Sanne Grinovero (JIRA)

Have an IndexManager concept to manage IndexWriters, Readers and backend. ------------------------------------------------------------------------- Key: HSEARCH-750 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-750 Project: Hibernate Search Issue Type: Improvement Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 4.0 -- 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, 5 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-761) Have a backend instance for each index

by Sanne Grinovero (JIRA)

Have a backend instance for each index -------------------------------------- Key: HSEARCH-761 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-761 Project: Hibernate Search Issue Type: New Feature Reporter: Sanne Grinovero Fix For: 4.0.0.Alpha1 this simplifies backend design, and makes it possible to tune each backend differently, or even use different technologies. -- 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, 5 months

1
4
0 / 0

[Hibernate-JIRA] Created: (HHH-6212) Handle econdary tables

by Hardy Ferentschik (JIRA)

Handle econdary tables ---------------------- Key: HHH-6212 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6212 Project: Hibernate Core Issue Type: Sub-task Reporter: Hardy Ferentschik -- 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, 5 months

3
8
0 / 0

[Hibernate-JIRA] Created: (HHH-6202) Bind inheritance type

by Hardy Ferentschik (JIRA)

Bind inheritance type --------------------- Key: HHH-6202 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6202 Project: Hibernate Core Issue Type: Sub-task Reporter: Hardy Ferentschik -- 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, 5 months

3
7
0 / 0

[Hibernate-JIRA] Created: (ANN-758) map key type no longer inferred correctly, throws exception at runtime

by David Mansfield (JIRA)

map key type no longer inferred correctly, throws exception at runtime ---------------------------------------------------------------------- Key: ANN-758 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-758 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.3.1.GA Environment: hib. 3.2, annotaions 3.3.1GA, em 3.3.1GA, oracle 10r2, tomcat 5.5, linux, spring 2.0 Reporter: David Mansfield Attachments: hib-anno-set-map-key-type.patch after upgrading from annotations 3.3.0GA to 3.3.1GA, my mapped collection (ManyToMany) is broken. i've identified the commit that broke it: http://fisheye.jboss.com/browse/Hibernate/annotations/trunk/src/java/org/... The issue is that unless the type is given now expliticly in the @MapKey's @Type, the code now assumes a 'Serializable' type, and attempts to deserialize an object stream from the database column value. the exact exception is: java.io.StreamCorruptedException: invalid stream header at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:764) at java.io.ObjectInputStream.<init>(ObjectInputStream.java:277) at org.hibernate.util.SerializationHelper$CustomObjectInputStream.<init>(SerializationHelper.java:252) at org.hibernate.util.SerializationHelper.deserialize(SerializationHelper.java:209) at org.hibernate.util.SerializationHelper.deserialize(SerializationHelper.java:240) at org.hibernate.type.SerializableType.fromBytes(SerializableType.java:82) at org.hibernate.type.SerializableType.get(SerializableType.java:39) at org.hibernate.type.NullableType.nullSafeGet(NullableType.java:163) ... The fix is simple: if @Type is NOT given in the @MapKey annotation, keep the old behavior which at least tries to set the type, even if it may not work in all situations. The attached patch fixes the problem for me. In my particular situation, the map key type is a java.lang.Enum. Here's what my annotated property looks like: @ManyToMany @JoinTable( name="chargeback_owner" ,joinColumns=@JoinColumn(name="person_id",referencedColumnName="person_id") ,inverseJoinColumns=@JoinColumn(name="owner_person_id") ) @MapKey(columns=@Column(name="owner_type_cd"),targetElement=ChargebackOwnerType.class) @Enumerated(EnumType.STRING) @Sort(type=SortType.NATURAL) private SortedMap<ChargebackOwnerType,Person> owners = new TreeMap<ChargebackOwnerType, Person>(); -- 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, 5 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2449) Lazy loading for one-to-one asociations

by jose (JIRA)

Lazy loading for one-to-one asociations --------------------------------------- Key: HHH-2449 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2449 Project: Hibernate3 Type: New Feature Components: core Versions: 3.2.2 Environment: Hibernate 3.2.2 Reporter: jose After read "Some explanations on lazy loading" and my tests I found a lossing feature in Hibernate (3.2.2). one-to-one with lazy="proxy"_____________________________________________ Hibernate ALWAYS launch selects to know if one-to-one is null or can be proxied. one-to-one with lazy="no-proxy"__________________________________________ Instrumentation allows to hibernate modify the getter to allows lazy loading on demand: * but allways initialize ALL no-proxy relations (with first getter call) -> must initialize ONLY the requested property * never auto-initialize FETCH joins, ALWAYS doit on demand (if opened session) -> must auto-initialize ONLY the FETCHED property note: Can submit a fix for this? How? NEW FEATURE: one-to-one with lazy="proxy" without multiple SELECTS______ If Hibernate adds join, for all one-to-one relations, to get the foreign-key of other tables, can check it to create a proxy or null. note: that hibernate adds joins for hierarchy, why not for one-to-one relations? This solution avoids: * 'multiple subselects' after first select * 'instrumentation' of bytecode -- 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, 5 months

3
2
0 / 0

[Hibernate-JIRA] Created: (ANN-614) @WhereJoinTable doesn't work with @ManyToOne

by Victor (JIRA)

@WhereJoinTable doesn't work with @ManyToOne -------------------------------------------- Key: ANN-614 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-614 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.0.ga Reporter: Victor @ManyToOne( fetch=FetchType.LAZY ) @JoinTable(name="CATEGORY_PRODUCT", uniqueConstraints = @UniqueConstraint(columnNames = {"PDID", "CATID"}), joinColumns = @JoinColumn(name="PDID"), inverseJoinColumns = @JoinColumn(name="CATID") ) @WhereJoinTable(clause="CATMAIN=1") protected Category getMainCategory() { return mainCategory; } protected void setMainCategories(Category mainCategory) { this.mainCategory = mainCategory; } Best regards, Victor -- 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, 5 months

5
5
0 / 0

[Hibernate-JIRA] Created: (HHH-4648) Mapping exception when one class maps to multiple tables.

by Subhan (JIRA)

Mapping exception when one class maps to multiple tables. --------------------------------------------------------- Key: HHH-4648 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4648 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.5.0-Beta-2 Environment: hibernate-envers-3.5.0-Beta-2 and hibernate-core-3.3.2.GA Reporter: Subhan Priority: Critical The problem arises when there is one class mapped to multiple tables separated by entity name. See the scenarios about it here: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=164631. -- 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, 5 months

4
5
0 / 0

[Hibernate-JIRA] Created: (HHH-5909) SybaseASE15Dialect getMaxAliasLength() cause SQL exception

by Yang Li (JIRA)

SybaseASE15Dialect getMaxAliasLength() cause SQL exception ---------------------------------------------------------- Key: HHH-5909 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5909 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.1, 3.6.0 Environment: Sybase ASE 15.5 with Sybase JDBC 3 (jconn3.jar) Hibernate 3.6.0 final JDK 1.6.0_23 Reporter: Yang Li Priority: Critical After upgrade Hibernate from 3.2.0 to 3.6.0, I got following exception with following SQL (converted from HQL): select defaultwdo1_.displayDescriptionTemplate as displayDescriptionTemplate30_1_ from WJob wjob0_, WDocDist defaultwdo1_ Caused by: com.sybase.jdbc3.jdbc.SybSQLException: The identifier that starts with 'displayDescriptionTemplate30_1' is too long. Maximum length is 30. at com.sybase.jdbc3.tds.Tds.a(Unknown Source) at com.sybase.jdbc3.tds.Tds.nextResult(Unknown Source) at com.sybase.jdbc3.jdbc.ResultGetter.nextResult(Unknown Source) at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source) at com.sybase.jdbc3.jdbc.SybStatement.nextResult(Unknown Source) at com.sybase.jdbc3.jdbc.SybStatement.queryLoop(Unknown Source) at com.sybase.jdbc3.jdbc.SybStatement.executeQuery(Unknown Source) at com.sybase.jdbc3.jdbc.SybPreparedStatement.executeQuery(Unknown Source) at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:208) at org.hibernate.loader.Loader.getResultSet(Loader.java:1953) The same SQL can be executed in native Sybase ISQL environment without any error. The workaround using Sybase11Dilect or modify getMaxAliasLength() inside SybaseASE15Dialect to return a smaller number(e.g. 20) -- 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, 5 months

2
6
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 2011