October 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2066) HSQL DB + multi-schema --> raised an exception (Problem to get an increment key [select max(id) from table)

by XOrangOutan (JIRA)

HSQL DB + multi-schema --> raised an exception (Problem to get an increment key [select max(id) from table) ----------------------------------------------------------------------------------------------------------- Key: HHH-2066 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2066 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr4 Environment: HSQL DB 1.8.x Reporter: XOrangOutan When trying to save an object that has an "incremental" primary key, Hibernate API tries to know what the max current id is by executing a "SELECT MAX". Though, in this particular sql query, schema name is not taken into account (in hsqldialect). This cause an error that prevents anyone from carrying out unit tests. This bug also exists on 3.x versions -- 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

16 years, 11 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-145) Document a configuration property

by John Griffin (JIRA)

Document a configuration property --------------------------------- Key: HSEARCH-145 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-145 Project: Hibernate Search Issue Type: Improvement Components: documentation Affects Versions: 3.0.0.GA Reporter: John Griffin The configuration property that allows combining different entities into the same directory is not documented. Along with this, the use of @Indexed(name= ) should be documented as an alternative way to implement this. -- 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

16 years, 11 months

3
5
0 / 0

[Hibernate-JIRA] Updated: (HHH-1907) offload metadata information from ComponentType to SessionFactory

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1907?page=c... ] Steve Ebersole updated HHH-1907: -------------------------------- Fix Version/s: 3.4 Summary: offload metadata information from ComponentType to SessionFactory (was: make ComponentType operate more like EntityType) Added that HHH-1907 requires HHH-2578 which in the long term is correct to do this cleanly. However, HHH-2578 is far more ambitious than this issue and is therefore bound to the 4.x time-frame. Would really like to instead get this into earlier releases since it is very very useful. > offload metadata information from ComponentType to SessionFactory > ----------------------------------------------------------------- > > Key: HHH-1907 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1907 > Project: Hibernate Core > Issue Type: Improvement > Components: core > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Fix For: 3.4 > > > Specifically, we need to move all the code directly dealing with property-access, instantiation, etc out of here. So where do we move it? Well, EntityType for example moves this stuff off to the persisters; the type then just looks up the persister when needed. Not sure we actually need a persister per-se for handling components; perhaps just ComponentMetamodel is enough... > Why is this important? Well the way ComponentType is currently structured leads to the need for certain configuration properties to be classloader scoped (static on Environment) instead of SessionFactory scoped. This is painful for two in particular: 1) whether to use reflection optimization and 2) bytecode provider. > Also, this change should allow us to cleanup how property accessors are built -- 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

16 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2781) Changes to fields marked as non-updateable written to L2 cache

by Steve Ebersole (JIRA)

Changes to fields marked as non-updateable written to L2 cache -------------------------------------------------------------- Key: HHH-2781 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2781 Project: Hibernate3 Issue Type: Bug Components: caching (L2) Reporter: Steve Ebersole Assignee: Steve Ebersole When the value a field marked as update="false" is changed, that changed state is written to the L2 cache. This occurs at least on reattachment, but I assume it also occurs for managed entities (need to verify). Viable solutions include: 1) disallow this combination (cached + non-updateable, non-generationed properties) 2) implicitly treat these properties as generated. Workaround is to mark these fields as generated. -- 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

16 years, 11 months

1
7
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-225) Avoid using IndexReader.deleteDocument when index is not shared amongst several entity types

by Emmanuel Bernard (JIRA)

Avoid using IndexReader.deleteDocument when index is not shared amongst several entity types -------------------------------------------------------------------------------------------- Key: HSEARCH-225 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-225 Project: Hibernate Search Issue Type: Bug Reporter: Emmanuel Bernard Fix For: 3.1.0.Beta1 When an index is not shared amongst several entities (ie only a given class is stored in the index, we can use IndexWriter.deleteDocuments() using a term pointing to the id. This cannot work for index shared across several entities, even subclasses. We need to build a flag in the metadata and compute it when the SearchFactory is built. Then reuse it during the indexing process to enable the optimization -- 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

16 years, 11 months

3
10
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-252) Document Solr integration

by Emmanuel Bernard (JIRA)

Document Solr integration ------------------------- Key: HSEARCH-252 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-252 Project: Hibernate Search Issue Type: New Feature Components: analyzer 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

16 years, 11 months

2
2
0 / 0

[Hibernate-JIRA] Commented: (HHH-1657) hql update generate wrong sql with joined subclass hierarcy

by dave schorr (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1657?page=c... ] dave schorr commented on HHH-1657: ---------------------------------- Yes, please issue a fix for this bug. I've been pushing internally to continue using hibernate and unresolved bugs like this are making the team reconsider. Thanks. > hql update generate wrong sql with joined subclass hierarcy > ----------------------------------------------------------- > > Key: HHH-1657 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1657 > Project: Hibernate Core > Issue Type: Bug > Components: query-hql > Environment: Hibernate 3.2.0cr1, Hibernate 3.1.3 > Reporter: Alexey Romanchuk > Assignee: Gail Badner > > Let suppose that we have two joined subclass entities: Parent (id PK) and Child (id PK) that mapped with joined subclass method. > When I try to update Child by id with hql: > update Child c set c.field = 'value' where c.id = 1234 > hibernate generates joined tables like > insert into HT_parent select child0_.id as id from child child0_ inner join parent child0_1_ on child0_.id=child0_1_.id wher id in = 1234 > look at last condition. hibernate use id WITH OUT tables alias that cause sql exception: column reference "id" is ambiguous -- 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

16 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2802) Support HQL style order by (JPA @OrderBy)

by Emmanuel Bernard (JIRA)

Support HQL style order by (JPA @OrderBy) ----------------------------------------- Key: HHH-2802 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2802 Project: Hibernate3 Issue Type: New Feature Components: core Reporter: Emmanuel Bernard Fix For: 3.3 Hibernate Annotations works around the lack of ability to define Order by clause using properties rather than columns by doing the translation at configuration time. Unfortunately, this cannot take alias into account. So moving this logic to the core would make sense -- 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

16 years, 11 months

2
8
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-254) Migrate to Solr 1.3

by Emmanuel Bernard (JIRA)

Migrate to Solr 1.3 ------------------- Key: HSEARCH-254 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-254 Project: Hibernate Search Issue Type: Task Components: analyzer Reporter: Emmanuel Bernard Assignee: Hardy Ferentschik Fix For: 3.1.0.Beta2 Attachments: Adapt_to_Solr_1_3.patch Solr 1.3 contains the needed fix for the CCE but has a lot of unintended consequences: - the Tokenizer and filter framework has changed (see attached patch) - Solr 1.3 depends on Lucene 2.4-dev Lucene 2.4 has an incompatible Snowball change that creates CCE if Solr 1.3 and Lucene 2.3 are used together. Hopefully this will be solved in time for 3.1.0.GA (the release of Lucene 2.4), otherwise we will need to provide a SnowballFilterFactory -- 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

16 years, 11 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3540) Dynamic model to fetch data (getting Exception when using Set with fetch="join").

by Prosenjit Chakraborty (JIRA)

Dynamic model to fetch data (getting Exception when using Set with fetch="join"). --------------------------------------------------------------------------------- Key: HHH-3540 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3540 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.1 Environment: hibernate-distribution-3.3.1.GA Reporter: Prosenjit Chakraborty Attachments: entity.hbm.xml I am using dynamic model to fetch data. entity.hbm.xml: ============ <hibernate-mapping default-lazy="false"> <class entity-name="en_table1" table="table1"> <id name="tab_id1" column="tab_id1" type="integer"/> <property name="tab_name1" column="tab_name1" type="string" /> <set name="en_table2s" fetch="join" lazy="false"> <key column="tab_id1"/> <one-to-many class="en_table2"/> </set> </class> <class entity-name="en_table2" table="table2"> <id name="tab_id2" column="tab_id2" type="integer"/> <property name="tab_name2" column="tab_name2" type="string" /> <set name="en_table3s" fetch="join" lazy="false"> <key column="tab_id2"/> <one-to-many class="en_table3"/> </set> </class> <class entity-name="en_table3" table="table3"> <id name="tab_id3" column="tab_id3" type="integer"/> <property name="tab_name3" column="tab_name3" type="string" /> </class> </hibernate-mapping> Data Access Code: ================ Object o=session.get("en_table1",1); Getting error: ================ org.hibernate.LazyInitializationException: illegal access to loading collection at org.hibernate.collection.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:363) at org.hibernate.collection.AbstractPersistentCollection.read(AbstractPersistentCollection.java:108) at org.hibernate.collection.PersistentSet.hashCode(PersistentSet.java:434) at java.util.HashMap$Entry.hashCode(Unknown Source) at java.util.AbstractMap.hashCode(Unknown Source) at java.util.HashMap.put(Unknown Source) at java.util.HashSet.add(Unknown Source)........... ##### The problem arises from the second level Set (here, 'set name="en_table3s"' ). For first level set only('set name="en_table2s"') the problem doesn't arise. Though can be solved by: <set name="en_table3s" fetch="select" lazy="false">. But, I have to use fetch="join". So, what should I do now? Please help. -- 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

16 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues October 2008