Menu
▾
▴
hibernate-issues — Hibernate JIRA Notifications
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(32) |
Jun
(175) |
Jul
(209) |
Aug
(302) |
Sep
(287) |
Oct
(339) |
Nov
(314) |
Dec
(329) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(479) |
Feb
(389) |
Mar
(599) |
Apr
(307) |
May
(390) |
Jun
(300) |
Jul
(410) |
Aug
(458) |
Sep
(299) |
Oct
(315) |
Nov
(363) |
Dec
(529) |
| 2005 |
Jan
(568) |
Feb
(434) |
Mar
(1004) |
Apr
(823) |
May
(767) |
Jun
(763) |
Jul
(854) |
Aug
(862) |
Sep
(560) |
Oct
(853) |
Nov
(763) |
Dec
(731) |
| 2006 |
Jan
(776) |
Feb
(608) |
Mar
(657) |
Apr
(424) |
May
(559) |
Jun
(440) |
Jul
(448) |
Aug
(58) |
Sep
|
Oct
(17) |
Nov
(16) |
Dec
(8) |
| 2007 |
Jan
(1) |
Feb
(8) |
Mar
(2) |
Apr
(5) |
May
(3) |
Jun
(3) |
Jul
(3) |
Aug
(16) |
Sep
(10) |
Oct
(4) |
Nov
(4) |
Dec
(4) |
| 2008 |
Jan
(8) |
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
|
From: Emmanuel B. (JIRA) <no...@at...> - 2006-06-09 01:42:30
|
[ http://opensource.atlassian.com/projects/hibernate/browse/EJB-195?page=all ] Emmanuel Bernard resolved EJB-195: ---------------------------------- Resolution: Fixed > Wrong query should raise an IllegalArgumentException > ---------------------------------------------------- > > Key: EJB-195 > URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-195 > Project: Hibernate Entity Manager > Type: Bug > Versions: 3.2.0.cr1 > Reporter: Emmanuel Bernard > Assignee: Emmanuel Bernard > Fix For: 3.2.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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Emmanuel B. (JIRA) <no...@at...> - 2006-06-09 01:40:37
|
[ http://opensource.atlassian.com/projects/hibernate/browse/EJB-194?page=all ] Emmanuel Bernard resolved EJB-194: ---------------------------------- Resolution: Fixed > Removing a detached instance is not allowed > ------------------------------------------- > > Key: EJB-194 > URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-194 > Project: Hibernate Entity Manager > Type: Bug > Components: EntityManager > Versions: 3.2.0.cr1 > Reporter: Emmanuel Bernard > Assignee: Emmanuel Bernard > Priority: Minor > Fix For: 3.2.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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Emmanuel B. (JIRA) <no...@at...> - 2006-06-09 01:40:32
|
Keep track of a isDetached flag in bytecode enhanced classes
------------------------------------------------------------
Key: HHH-1823
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1823
Project: Hibernate3
Type: New Feature
Components: core
Versions: 3.2.0.cr2
Reporter: Emmanuel Bernard
Priority: Minor
To counter the corner case efficiency of HHH-1822
a flag could be kept in the enhanced 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.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
|
From: Emmanuel B. (JIRA) <no...@at...> - 2006-06-09 01:40:31
|
Write an Java Agent to avoid the build time enhancement operation
-----------------------------------------------------------------
Key: HHH-1824
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1824
Project: Hibernate3
Type: New Feature
Components: build
Reporter: Emmanuel Bernard
Priority: Minor
requires JDK 5
--
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.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
|
From: Emmanuel B. (JIRA) <no...@at...> - 2006-06-09 01:38:32
|
flushing entity linked to transient instance (non cascaded) should always fail
------------------------------------------------------------------------------
Key: HHH-1822
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1822
Project: Hibernate3
Type: Bug
Components: core
Versions: 3.2.0.cr2
Reporter: Emmanuel Bernard
Priority: Critical
Fix For: 3.2.0
A a = new A();
B b = new B();
a.setB(b);
session.persist(a);
session.flush(); //should fail in all cases same for collections
esp when generator is assigned
--
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.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
|
From: Emmanuel B. (JIRA) <no...@at...> - 2006-06-09 01:30:31
|
Wrong query should raise an IllegalArgumentException
----------------------------------------------------
Key: EJB-195
URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-195
Project: Hibernate Entity Manager
Type: Bug
Versions: 3.2.0.cr1
Reporter: Emmanuel Bernard
Assigned to: Emmanuel Bernard
Fix For: 3.2.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.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
|
From: Emmanuel B. (JIRA) <no...@at...> - 2006-06-09 01:30:31
|
referencing a transient instance while flushing an association non cascaded should raise IllegalStateException
--------------------------------------------------------------------------------------------------------------
Key: EJB-196
URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-196
Project: Hibernate Entity Manager
Type: Bug
Components: Documentation
Versions: 3.2.0.cr1
Reporter: Emmanuel Bernard
Assigned to: Emmanuel Bernard
Priority: Minor
Fix For: 3.2.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.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
|
From: Emmanuel B. (JIRA) <no...@at...> - 2006-06-09 01:28:32
|
Removing a detached instance is not allowed
-------------------------------------------
Key: EJB-194
URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-194
Project: Hibernate Entity Manager
Type: Bug
Components: EntityManager
Versions: 3.2.0.cr1
Reporter: Emmanuel Bernard
Assigned to: Emmanuel Bernard
Priority: Minor
Fix For: 3.2.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.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
|
From: Emmanuel B. (JIRA) <no...@at...> - 2006-06-09 00:32:32
|
Create some specialized converter for number
--------------------------------------------
Key: ANN-366
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-366
Project: Hibernate Annotations
Type: New Feature
Components: lucene
Reporter: Emmanuel Bernard
Typically, the numbers are padded to match the alphabetical ordering
007
023
234
This can be done manually through a converter but this would be nice to have it built-in
--
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.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
|
From: Emmanuel B. (JIRA) <no...@at...> - 2006-06-09 00:07:31
|
Be able to define a Date field as Field.keyword(String, Date)
-------------------------------------------------------------
Key: ANN-365
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-365
Project: Hibernate Annotations
Type: New Feature
Components: lucene
Reporter: Emmanuel Bernard
Priority: Minor
probably not very useful but for the API completness...
--
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.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
|
From: Emmanuel B. (JIRA) <no...@at...> - 2006-06-09 00:05:31
|
@Boost or equivalent on entity and on fields
--------------------------------------------
Key: ANN-364
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-364
Project: Hibernate Annotations
Type: New Feature
Components: lucene
Reporter: Emmanuel Bernard
--
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.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
|
From: Emmanuel B. (JIRA) <no...@at...> - 2006-06-09 00:01:40
|
Support for a @Converter
------------------------
Key: ANN-363
URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-363
Project: Hibernate Annotations
Type: New Feature
Components: lucene
Reporter: Emmanuel Bernard
--
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.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
|
From: Max R. A. (JIRA) <no...@at...> - 2006-06-08 14:05:31
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-686?page=all ] Max Rydahl Andersen closed HBX-686: ----------------------------------- Resolution: Fixed sf creation is now postponed until user either click on a sessionfactory (+) or tries to execute a query. > SessionFactory should not be created immediatly when browsing a console config > ------------------------------------------------------------------------------ > > Key: HBX-686 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-686 > Project: Hibernate Tools > Type: Improvement > Versions: 3.1.beta5 > Reporter: Max Rydahl Andersen > Fix For: 3.2beta6 > > > currenlty a sessionfactory is created instantly when clicking on a console config. > This is a heavy operation and we should avoid it if possible. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Max R. A. (JIRA) <no...@at...> - 2006-06-08 14:03:32
|
SessionFactory should not be created immediatly when browsing a console config
------------------------------------------------------------------------------
Key: HBX-686
URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-686
Project: Hibernate Tools
Type: Improvement
Versions: 3.1.beta5
Reporter: Max Rydahl Andersen
Fix For: 3.2beta6
currenlty a sessionfactory is created instantly when clicking on a console config.
This is a heavy operation and we should avoid it if possible.
--
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.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
|
From: Martin S. (JIRA) <no...@at...> - 2006-06-08 13:24:44
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1621?page=comments#action_23301 ] Martin Schulz commented on HHH-1621: ------------------------------------ Scenario (corrected): The parent class A has a discriminator field and some but _not_ all possible discriminator values are mapped to subclasses. A. Schaefer's comment above appears on the surface to be unrelated, unless the method to find thesubclass by discriminator itself is supposed to provide the fallback mechanism, which is of course a valid alternative. > subclass mapping by discriminator - should instantiate parent for unmapped discriminator values > ----------------------------------------------------------------------------------------------- > > Key: HHH-1621 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1621 > Project: Hibernate3 > Type: Improvement > Components: core > Environment: 3.1.2 > Sybase ASE 12.5.3 > Reporter: Martin Schulz > Attachments: HHH-1621 > > > Scenario: The parent class A has a discriminator field and some but all possible scriminator values are mapped to subclasses. > Current behavior: > 1) Default: > The following exception is thrown > org.hibernate.WrongClassException: Object with id: 10000 was not of the specified subclass: A (Discriminator: D) > at org.hibernate.loader.Loader.getInstanceClass(Loader.java:1445) > [ the error itself is also quite misleading, as the row is exactly of / for the specified class A. But there simply was no > subclass found ]. > 2) discriminator with force="true" > The parent class is never instantiated, only the mapped subclasses are instantiated. > Proposed behavior: > The parent class should be instantiated for those rows with unmapped discriminator values. > Characteristics of proposed behavior: > - all rows in resultset would lead to instantiated class in the inheritence tree, > - the behavior would be in line with how joined-subclass behaves > - no caveat documentation required > Implementation: > (Easy) > in Loader.java, lines 1443ff, do not throw WrongClassException, but instead > return persister.getEntityName(); > (Alternate) > change persister.getSubclassForDiscriminatorValue() implementations correspondingly. > Thx for your consideration / vote. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Mohammed S. (JIRA) <no...@at...> - 2006-06-08 12:35:51
|
Sorting based on an optionally associated column
------------------------------------------------
Key: HHH-1821
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1821
Project: Hibernate3
Type: Bug
Components: query-criteria
Versions: 3.1 rc2
Environment: JBoss 4.0.3SP1, Oracle 8.1
Reporter: Mohammed Sadiq
Attachments: CmnCampusSchoolMstT.hbm.xml
Hi,
I have a table containing 3 assocations; out of which one is optional. When I give an order by clause for the optional assocation column (with an alias name in the Criteria) I get only those records for which this column has values, other records with null values are not listed.
As I went through the query generated by Hibernate I am surprised to see that the outer join symbol (+) was not there for this column, but was there when I try to order according to other associated columns.
I have attached my HBM file for your reference.
Any suggestion will be more helpful.
Thanks & Regards
Mohammed Sadiq
--
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.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
|
From: Nigel W. (JIRA) <no...@at...> - 2006-06-08 09:05:33
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1296?page=comments#action_23300 ] Nigel White commented on HHH-1296: ---------------------------------- Yes! I'm getting this too when I remove() an entry from a List with an @IndexColumn. The problem is the way Hibernate creates the link table, and then updates the link table. It puts a "unique" constraint on the child key of the link. That's a problem for a start, it means that a linked-to entity can only be a meber of one List. Try to put it into the List of another parent, and you'll get this error. It's a problem on List.remove() because the way it deals with removes is it cuts down the size of the list by deleting excess link rows from the end. That's fine - a perfectly good start. But then it just goes down the remaining link rows from 0 to n, updating them to point to the new List entries. If List item entry 0 was removed, then when it updates link row 0 to point to what link row 1 pointed to, bzzzzzzt... constraint violation, duplicate key! The schema update should not put the unique constraint on the child key of the link table! > Non lazy loaded List updates done in wrong order, cause exception > ----------------------------------------------------------------- > > Key: HHH-1296 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1296 > Project: Hibernate3 > Type: Bug > Components: core > Versions: 3.0.5 > Environment: Hibernate 3.0.5 - any database (checked postgres 7/8, mysql 4 & 5, db2 v8) > NOT using lazy loading - the tx's are wrapped by session beans, so lazy loading is not allowed. > Reporter: David Birch > Priority: Critical > > > The logic behind list updates is not quite right, nor was it in v2 (only now i have a DBA who won't let up...) > The scenario is: > a bean with list property, and the list has a number of items in it (say 4, index 0-3), an item is then removed (say item at index 2), and the bean is requested to be saved. > From what i can see in the SQL traces, the same statements are issues whe lazy loading is on or off, they are: > [18/12/05 19:48:50:766 EST] 00000036 SystemOut O Hibernate: delete from TGE_CLIENT_POLICY where CLIENT_ID=? and POSITION=? > [18/12/05 19:48:50:766 EST] 00000036 SystemOut O Hibernate: update TGE_CLIENT_POLICY set POLICY_NK=? where CLIENT_ID=? and POSITION=? > So, i can only assume (as when this fails, the row with index 1 above the removed row is nuked!), hibernate removes the item at index 3, and then copies the value of the item at index 3 onto the row for item at index 2. Fair enough but... > When i have lazy loading off, i get DB exceptions like > Duplicate key or integrity constraint violation message from server: "Duplicate entry '1-999999' for key 1" > so, there is some nasty in there, which is not updating the correct row - this has happened since 2.1.8 that i know of :( > i will try & look @ the source, but won't get a chance until after xmas... -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Andreas S. (JIRA) <no...@at...> - 2006-06-08 01:49:20
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1621?page=comments#action_23296 ] Andreas Schaefer commented on HHH-1621: --------------------------------------- I ran into the same issue and could it pin down to the fact that when this conditions: - Discriminiator Column is not specified as a column (I guess that is unmapped) - There is a Column with the same prefix - The maximum length for an alias for the DB in question is short enough that the prefix of the discriminator column and the other column are equal when cut off then I get a select statement with the same alias for the discriminator column and the other column and so you see the other's column value in the parentesis '(Discriminator: D)'. This is caused by the fact that the unique id for a column used to generate the alias is not only set when the column is added through the table but that is not the case when the discriminator column is not mapped. I hacked that by just added a special character when the alias is created for the discrimantor column. -Andy > subclass mapping by discriminator - should instantiate parent for unmapped discriminator values > ----------------------------------------------------------------------------------------------- > > Key: HHH-1621 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1621 > Project: Hibernate3 > Type: Improvement > Components: core > Environment: 3.1.2 > Sybase ASE 12.5.3 > Reporter: Martin Schulz > Attachments: HHH-1621 > > > Scenario: The parent class A has a discriminator field and some but all possible scriminator values are mapped to subclasses. > Current behavior: > 1) Default: > The following exception is thrown > org.hibernate.WrongClassException: Object with id: 10000 was not of the specified subclass: A (Discriminator: D) > at org.hibernate.loader.Loader.getInstanceClass(Loader.java:1445) > [ the error itself is also quite misleading, as the row is exactly of / for the specified class A. But there simply was no > subclass found ]. > 2) discriminator with force="true" > The parent class is never instantiated, only the mapped subclasses are instantiated. > Proposed behavior: > The parent class should be instantiated for those rows with unmapped discriminator values. > Characteristics of proposed behavior: > - all rows in resultset would lead to instantiated class in the inheritence tree, > - the behavior would be in line with how joined-subclass behaves > - no caveat documentation required > Implementation: > (Easy) > in Loader.java, lines 1443ff, do not throw WrongClassException, but instead > return persister.getEntityName(); > (Alternate) > change persister.getSubclassForDiscriminatorValue() implementations correspondingly. > Thx for your consideration / vote. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Max R. A. (JIRA) <no...@at...> - 2006-06-07 20:31:25
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-685?page=all ] Max Rydahl Andersen closed HBX-685: ----------------------------------- Resolution: Rejected ok, thanks for telling me. > Reverse Engineering Strategy cannot find constructor > ---------------------------------------------------- > > Key: HBX-685 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-685 > Project: Hibernate Tools > Type: Bug > Components: reverse-engineer > Versions: 3.1.beta5 > Reporter: Matt Read > Attachments: ExampleStrategy.java, screenshot-1.jpg > > > The custom reverse engineering strategy I was using on 3.1beta4 fails with the following error on beta 5. I've tried pasting the "ExampleStrategy" from the documentation (http://www.hibernate.org/hib_docs/tools/reference/en/html/reverseengineering.html#custom-reveng-strategy) and that fails too. > "Could not create or find com.xxx.ExampleStrategy with one argument delegate constructor" -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Jakub M. (JIRA) <no...@at...> - 2006-06-07 18:00:42
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1820?page=comments#action_23294 ] Jakub Mendys commented on HHH-1820: ----------------------------------- Examle code to reproduce problem: String SQL = "select inst from MedDRATermInstance inst " + " where inst.version = :version and inst.medDRATerm.medDRACode in (:codes) "; Query query = session.createQuery( SQL ); query.setCacheable( true ); query.setInteger( "version", version.getMedDRAVersionId() ); query.setParameterList( "codes", medDRACodes ); List result = query.list(); for (Iterator iter = result.iterator(); iter.hasNext();) { MedDRATermInstance term1 = (MedDRATermInstance) iter.next(); MedDRATermInstance term2 = (MedDRATermInstance) session.get( MedDRATermInstance.class, new Long( term1 .getMedDRATermInstanceId() ) ); assertNotNull( term2.getMedDRATerm().getTermName( Language.DEFAULT ) ); } > Lazy loading problem when property-ref is used for collections > -------------------------------------------------------------- > > Key: HHH-1820 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1820 > Project: Hibernate3 > Type: Bug > Versions: 3.1.3 > Environment: Oracle 8.1.7 > Reporter: Jakub Mendys > > > Consider mapping > <class name="MedDRATerm" table="MBROW_MEDDRA_TERMS" mutable="false" > batch-size="50"> > <cache usage="read-only" region="dictionary" /> > <id name="medDRATermId" type="long" column="TERM_ID"> > <generator class="assigned" /> > </id> > <map name="termNames" table="MBROW_TERM_NAMES" lazy="true" > batch-size="50"> > <cache usage="read-only" region="dictionary" /> > <key column="MEDDRA_CODE" property-ref="medDRACode" /> > <index column="LANGUAGE_ID" > type="com.roche.dss.meddra.dao.type.LanguageType" /> > <element column="NAME" type="string" /> > </map> > <property name="medDRACode" column="MEDDRA_CODE" > type="com.roche.dss.meddra.dao.type.MedDRACodeType" /> > </class> > <class name="MedDRATermInstance" table="MBROW_MEDDRA_TREES" > mutable="false"> > <cache usage="read-only" region="dictionary" /> > <id name="medDRATermInstanceId" type="long" column="NODE_ID"> > <generator class="assigned" /> > </id> > <many-to-one name="medDRATerm" class="MedDRATerm" > column="TERM_ID" fetch="join" not-null="true" insert="false" > update="false" /> > </class> > When you execute a query: > from MedDRATermInstance i where i.version=:versionId and i.medDRATerm in (:terms) > and then using the _same session_ you will iterate over returned collection and will call session.get(id) for returned records it is very likely that for _SOME_ (random??) of objects when you will try to access its properties you will get following exception thrown: > 2006-06-07 19:25:11,942 ERROR org.hibernate.LazyInitializationException - failed to lazily initialize a collection of role: com.roche.dss.meddra.model.MedDRATerm.termNames, no session or session was > losed > org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: com.roche.dss.meddra.model.MedDRATerm.termNames, no session or session was closed > at org.hibernate.collection.AbstractPersistentCollection.throwLazyInitializationException(AbstractPersistentCollection.java:358) > at org.hibernate.collection.AbstractPersistentCollection.throwLazyInitializationExceptionIfNotConnected(AbstractPersistentCollection.java:350) > at org.hibernate.collection.AbstractPersistentCollection.readElementByIndex(AbstractPersistentCollection.java:151) > at org.hibernate.collection.PersistentMap.get(PersistentMap.java:127) > Calling session.clear() before session.get() helps to workaround this but causes all the records to be fethed again from the database. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Jakub M. (JIRA) <no...@at...> - 2006-06-07 17:28:22
|
Lazy loading problem when property-ref is used for collections
--------------------------------------------------------------
Key: HHH-1820
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1820
Project: Hibernate3
Type: Bug
Versions: 3.1.3
Environment: Oracle 8.1.7
Reporter: Jakub Mendys
Consider mapping
<class name="MedDRATerm" table="MBROW_MEDDRA_TERMS" mutable="false"
batch-size="50">
<cache usage="read-only" region="dictionary" />
<id name="medDRATermId" type="long" column="TERM_ID">
<generator class="assigned" />
</id>
<map name="termNames" table="MBROW_TERM_NAMES" lazy="true"
batch-size="50">
<cache usage="read-only" region="dictionary" />
<key column="MEDDRA_CODE" property-ref="medDRACode" />
<index column="LANGUAGE_ID"
type="com.roche.dss.meddra.dao.type.LanguageType" />
<element column="NAME" type="string" />
</map>
<property name="medDRACode" column="MEDDRA_CODE"
type="com.roche.dss.meddra.dao.type.MedDRACodeType" />
</class>
<class name="MedDRATermInstance" table="MBROW_MEDDRA_TREES"
mutable="false">
<cache usage="read-only" region="dictionary" />
<id name="medDRATermInstanceId" type="long" column="NODE_ID">
<generator class="assigned" />
</id>
<many-to-one name="medDRATerm" class="MedDRATerm"
column="TERM_ID" fetch="join" not-null="true" insert="false"
update="false" />
</class>
When you execute a query:
from MedDRATermInstance i where i.version=:versionId and i.medDRATerm in (:terms)
and then using the _same session_ you will iterate over returned collection and will call session.get(id) for returned records it is very likely that for _SOME_ (random??) of objects when you will try to access its properties you will get following exception thrown:
2006-06-07 19:25:11,942 ERROR org.hibernate.LazyInitializationException - failed to lazily initialize a collection of role: com.roche.dss.meddra.model.MedDRATerm.termNames, no session or session was
losed
org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: com.roche.dss.meddra.model.MedDRATerm.termNames, no session or session was closed
at org.hibernate.collection.AbstractPersistentCollection.throwLazyInitializationException(AbstractPersistentCollection.java:358)
at org.hibernate.collection.AbstractPersistentCollection.throwLazyInitializationExceptionIfNotConnected(AbstractPersistentCollection.java:350)
at org.hibernate.collection.AbstractPersistentCollection.readElementByIndex(AbstractPersistentCollection.java:151)
at org.hibernate.collection.PersistentMap.get(PersistentMap.java:127)
Calling session.clear() before session.get() helps to workaround this but causes all the records to be fethed again from the database.
--
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.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
|
From: Jakub M. (JIRA) <no...@at...> - 2006-06-07 17:16:22
|
Invalid SQL generated for mapping with property-ref
---------------------------------------------------
Key: HHH-1819
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1819
Project: Hibernate3
Type: Bug
Components: query-hql
Versions: 3.1.3
Environment: Oracle 8.1.7
Reporter: Jakub Mendys
Priority: Critical
Consider mappings:
<class name="MedDRATerm" table="MBROW_MEDDRA_TERMS" mutable="false"
batch-size="50">
<cache usage="read-only" region="dictionary" />
<id name="medDRATermId" type="long" column="TERM_ID">
<generator class="assigned" />
</id>
<map name="termNames" table="MBROW_TERM_NAMES" lazy="true"
batch-size="50">
<cache usage="read-only" region="dictionary" />
<key column="MEDDRA_CODE" property-ref="medDRACode" />
<index column="LANGUAGE_ID"
type="com.roche.dss.meddra.dao.type.LanguageType" />
<element column="NAME" type="string" />
</map>
<property name="medDRACode" column="MEDDRA_CODE"
type="com.roche.dss.meddra.dao.type.MedDRACodeType" />
</class>
<class name="MedDRATermInstance" table="MBROW_MEDDRA_TREES"
mutable="false">
<cache usage="read-only" region="dictionary" />
<id name="medDRATermInstanceId" type="long" column="NODE_ID">
<generator class="assigned" />
</id>
<many-to-one name="medDRATerm" class="MedDRATerm"
column="TERM_ID" fetch="join" not-null="true" insert="false"
update="false" />
</class>
and a HQL query:
from MedDRATermInstance i where i.medDRATermInstanceId is not null and i.medDRATerm.termNames[1] like 'headache'
Having this Hibernate will generate following SQL:
SELECT ...
FROM orcl_gthes.mbrow_meddra_trees meddraterm0_,
orcl_gthes.mbrow_term_names termnames2_
WHERE meddraterm1_.meddra_code = termnames2_.meddra_code
AND termnames2_.language_id = 1
AND meddraterm0_.term_id = meddraterm1_.term_id
AND (termnames2_.NAME LIKE 'headache')
Please note that WHERE clause refers to alias meddraterm1_ which is not mentioned in FROM section!!!!
--
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.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
|
From: Assaf B. (JIRA) <no...@at...> - 2006-06-07 16:38:34
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1813?page=comments#action_23293 ] Assaf Berg commented on HHH-1813: --------------------------------- Happens using Hibernate 3.2CR2 + ehcache 1.2 as well. > 2nd level cached collections are locked causing a cache miss > ------------------------------------------------------------ > > Key: HHH-1813 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1813 > Project: Hibernate3 > Type: Bug > Versions: 3.1 > Environment: Hibernate 3.1, Oracle 10g, Linux > Reporter: Assaf Berg > Priority: Critical > Attachments: testcase.tar.gz > > > Using the second level cache, collections are fetched from the database due to the cached item being locked. > This happens in the most simple use case: > 1. Insert an entity with a collection > 2. Commit. > 3. Fetch the entity > I've written a simple test case and see the following in the log file: > 11:52:47,159 DEBUG [ReadWriteCache] Invalidating: domain.Cat.kittens#539957 > 11:52:47,177 DEBUG [ReadWriteCache] Inserting: domain.Cat#539957 > 11:52:47,179 DEBUG [ReadWriteCache] Inserted: domain.Cat#539957 > 11:52:47,180 DEBUG [ReadWriteCache] Inserting: domain.Kitten#540214 > 11:52:47,180 DEBUG [ReadWriteCache] Inserted: domain.Kitten#540214 > 11:52:47,181 DEBUG [ReadWriteCache] Releasing: domain.Cat.kittens#539957 > 11:52:49,221 DEBUG [ReadWriteCache] Caching: domain.Cat#539957 > 11:52:49,221 DEBUG [ReadWriteCache] Item was already cached: domain.Cat#539957 > 11:52:49,223 DEBUG [ReadWriteCache] Cache lookup: domain.Cat.kittens#539957 > 11:52:49,223 DEBUG [ReadWriteCache] Cached item was locked: domain.Cat.kittens#539957 > 11:52:49,229 DEBUG [ReadWriteCache] Caching: domain.Kitten#540214 > 11:52:49,229 DEBUG [ReadWriteCache] Item was already cached: domain.Kitten#540214 > 11:52:49,230 DEBUG [ReadWriteCache] Caching: domain.Cat.kittens#539957 > 11:52:49,231 DEBUG [ReadWriteCache] Cached: domain.Cat.kittens#539957 > domain.Cat.kittens [C/H/M/P]: 1/0/1/1 > domain.Cat [C/H/M/P]: 1/0/0/1 > domain.Kitten [C/H/M/P]: 1/0/0/1 > This happens whether the collection is mapped as inverse or not. > I've attached the test case source and hbms (although it might need to be tweaked for the proper DB before running, and I didn't include the dependencies JARs). > Here's a code excerpt of the interesting part (tx is TransactionTemplate using HibnerateTransactionManager and hibernate is HibernateTemplate from the spring framework): > tx.execute(new TransactionCallback() { > public Object doInTransaction(TransactionStatus status) { > // create a Cat with one Kitten > Cat cat = new Cat(); > Kitten kitten = new Kitten(); > cat.addKitten(kitten); > > hibernate.save(cat); > > return null; > } > }); > > Thread.sleep(2000L); > > tx.execute(new TransactionCallback() { > public Object doInTransaction(TransactionStatus status) { > // load all cats > List<Cat> allCats = hibernate.loadAll(Cat.class); > return null; > } > }); > I can supply further information if needed. -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Matt R. (JIRA) <no...@at...> - 2006-06-07 16:13:40
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-685?page=comments#action_23292 ] Matt Read commented on HBX-685: ------------------------------- I just deleted all old JBossIDE plugins and features from my Eclipse plugins and features folders and then re-installed and the problem has gone away. I must have had a mixture of update-site based installations and manual installations that conflicted in some way. Sorry for wasting your time. Matt. > Reverse Engineering Strategy cannot find constructor > ---------------------------------------------------- > > Key: HBX-685 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-685 > Project: Hibernate Tools > Type: Bug > Components: reverse-engineer > Versions: 3.1.beta5 > Reporter: Matt Read > Attachments: ExampleStrategy.java, screenshot-1.jpg > > > The custom reverse engineering strategy I was using on 3.1beta4 fails with the following error on beta 5. I've tried pasting the "ExampleStrategy" from the documentation (http://www.hibernate.org/hib_docs/tools/reference/en/html/reverseengineering.html#custom-reveng-strategy) and that fails too. > "Could not create or find com.xxx.ExampleStrategy with one argument delegate constructor" -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Matt R. (JIRA) <no...@at...> - 2006-06-07 15:23:19
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-685?page=all ] Matt Read updated HBX-685: -------------------------- Attachment: screenshot-1.jpg Sorry, nothing appears in the Error Log view or in the Eclipse .metadata/.log directory. Just this the popup I've attached here. > Reverse Engineering Strategy cannot find constructor > ---------------------------------------------------- > > Key: HBX-685 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-685 > Project: Hibernate Tools > Type: Bug > Components: reverse-engineer > Versions: 3.1.beta5 > Reporter: Matt Read > Attachments: ExampleStrategy.java, screenshot-1.jpg > > > The custom reverse engineering strategy I was using on 3.1beta4 fails with the following error on beta 5. I've tried pasting the "ExampleStrategy" from the documentation (http://www.hibernate.org/hib_docs/tools/reference/en/html/reverseengineering.html#custom-reveng-strategy) and that fails too. > "Could not create or find com.xxx.ExampleStrategy with one argument delegate constructor" -- 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
93 messages has been excluded from this view by a project administrator.
