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: Steve E. (JIRA) <no...@at...> - 2006-06-28 16:46:19
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-422?page=all ] Steve Ebersole updated HHH-422: ------------------------------- Fix Version: 3.2.2 (was: 3.2.0.cr3) > xml entity bindings for subclass entities > ----------------------------------------- > > Key: HHH-422 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-422 > Project: Hibernate3 > Type: Improvement > Components: core > Versions: 3.0.2 > Environment: Hibernate cvs head from main branch .(As of 4/28/05..So 3.0.2?), Oracle 8i. > Reporter: Jesse Kuhnert > Assignee: Steve Ebersole > Fix For: 3.2.2 > Attachments: XMLSubclassTest.zip > > Original Estimate: 1 week > Remaining: 1 week > > I'm sure someone else is already in the process of agnonizing over how to handle the entity name resolution issues that are currently floating around in the codebase, but for the sake of not knowing who's doing what and what-not (heh), I thought I would share my couple quick notes learned from trying to make this work today. > I was having problems getting an import of xml data into hibernate with derived subclasses of one base class. (Not abstract, derived using the discriminator value column and table per subclass method). Was getting lots of errors trying to map my subclass nodes into the main xml document, even if I named the child nodes the same as the parent. The only eventual temporary solution I could find was by adding the subclass "node name" values into the two Map instances I could find that needed these references. [Mappings class and EntityPersister, ughh I've forgotten the other ones name now. ] > The one main culprit already had an obvious method comment with a TODO tag so I'm sure someone is already working on a much better longterm solution than mine.. The only thing I didn't complete was having the ability for the subclass instances to have their own node names. Ie if I had an instance of the base class mapped as a many-to-XX collection in someone's class, I had to specify a node name of "something" to get it to be recognized. I didn't get far enough in my day to get this part as well, but I think it would just require being able to reference the current child somehow. Some sort of XSLT expression like "name()" or "self" perhaps? > After that everything worked beautifully of course :) Will be very excited to see this feature come to full bloom, as I plan on using it to synchronize some data points with customer databases sometime this summer? (Am I being too hopeful? I'd love to help, but I'm sure there are plenty of good people doing things already..And I'm I'm fu#$!@ with my own deadlines anyways...) -- 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: Steve E. (JIRA) <no...@at...> - 2006-06-28 16:46:18
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-796?page=all ] Steve Ebersole updated HHH-796: ------------------------------- Fix Version: 3.2.2 (was: 3.2.0.cr3) > Hibernate fails to determine identifier of association inside composite-element in EntityMode.DOM4J when declared with embed-xml="false" > ---------------------------------------------------------------------------------------------------------------------------------------- > > Key: HHH-796 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-796 > Project: Hibernate3 > Type: Bug > Versions: 3.0.5 > Environment: Hibernate 3.0.5; Windows; MySQL 4.1 > Reporter: Vladimir Demochko > Fix For: 3.2.2 > Attachments: TestBug.zip > > > Having the following mapping declaration: > <class name="Parent"> > <id name="id"/> > <property name="label"/> > <bag name="associations" table="ASSOCIATION" cascade="all"> > <key column="PARENT_ID"/> > <composite-element class="Association" node="associations"> > <parent name="parent"/> > <many-to-one name="child" class="Child" column="CHILD_ID" node="child" embed-xml="false"/> > <property name="info" column="INFO" type="string"/> > </composite-element> > </bag> > </class> > <class name="Child"> > <id name="id"/> > <property name="info"/> > </class> > Hibernate fails with NullPointerException while constructing Parent/assosiations/child element (in fact while getting an identifier of a Child object) in EntityMode.DOM4J: > java.lang.NullPointerException > at org.hibernate.type.EntityType.getIdentifierType(EntityType.java:227) > at org.hibernate.type.EntityType.setToXMLNode(EntityType.java:417) > at org.hibernate.property.Dom4jAccessor$ElementSetter.set(Dom4jAccessor.java:307) > at org.hibernate.tuple.AbstractComponentTuplizer.setPropertyValues(AbstractComponentTuplizer.java:80) > at org.hibernate.type.ComponentType.setPropertyValues(ComponentType.java:262) > at org.hibernate.type.ComponentType.resolve(ComponentType.java:446) > at org.hibernate.type.ComponentType.nullSafeGet(ComponentType.java:182) > at org.hibernate.persister.collection.AbstractCollectionPersister.readElement(AbstractCollectionPersister.java:612) > at org.hibernate.collection.PersistentElementHolder.readFrom(PersistentElementHolder.java:97) > at org.hibernate.loader.Loader.readCollectionElement(Loader.java:645) > at org.hibernate.loader.Loader.readCollectionElements(Loader.java:355) > at org.hibernate.loader.Loader.getRowFromResultSet(Loader.java:306) > at org.hibernate.loader.Loader.doQuery(Loader.java:395) > at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:210) > at org.hibernate.loader.Loader.loadCollection(Loader.java:1401) > at org.hibernate.loader.collection.CollectionLoader.initialize(CollectionLoader.java:107) > at org.hibernate.persister.collection.AbstractCollectionPersister.initialize(AbstractCollectionPersister.java:483) > at org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:60) > at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1422) > at org.hibernate.type.CollectionType.getCollection(CollectionType.java:474) > at org.hibernate.type.CollectionType.resolveKey(CollectionType.java:332) > at org.hibernate.type.CollectionType.resolve(CollectionType.java:326) > at org.hibernate.engine.TwoPhaseLoad.initializeEntity(TwoPhaseLoad.java:105) > at org.hibernate.loader.Loader.initializeEntitiesAndCollections(Loader.java:510) > at org.hibernate.loader.Loader.doQuery(Loader.java:419) > at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:210) > at org.hibernate.loader.Loader.loadEntity(Loader.java:1312) > at org.hibernate.loader.entity.EntityLoader.load(EntityLoader.java:116) > at org.hibernate.loader.entity.EntityLoader.load(EntityLoader.java:101) > at org.hibernate.persister.entity.BasicEntityPersister.load(BasicEntityPersister.java:2461) > at org.hibernate.event.def.DefaultLoadEventListener.loadFromDatasource(DefaultLoadEventListener.java:350) > at org.hibernate.event.def.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:331) > at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:113) > at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:151) > at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:79) > at org.hibernate.impl.SessionImpl.get(SessionImpl.java:617) > at org.hibernate.impl.SessionImpl.get(SessionImpl.java:610) > at TestBug.main(TestBug.java:21) -- 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: Steve E. (JIRA) <no...@at...> - 2006-06-28 16:46:17
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1039?page=all ] Steve Ebersole updated HHH-1039: -------------------------------- Fix Version: 3.2.2 (was: 3.2.0.cr3) > WrongClassException when scrolling through EntityMode.DOM4J and loading identical objects from different fields > --------------------------------------------------------------------------------------------------------------- > > Key: HHH-1039 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1039 > Project: Hibernate3 > Type: Bug > Versions: 3.0.5 > Environment: Windows XP, JDK 1.4.2_8, Hibernate 3.0.5, Oracle 9.2. Replicated on Windows XP, JDK 1.5.0_2, Hibernate 3.0.5, MySQL > Reporter: Roland Groen > Fix For: 3.2.2 > Attachments: HbmXmlTest.java, Test.hbm.xml > > > When working with XML representations of entities, an unexpected org.hibernate.WrongClassException is thrown when working with identical embedded objects (embed-xml="true") which have different field names. > org.hibernate.WrongClassException seems to be thrown when: > 1) Running in EntityMode.DOM4J > 2) Scrolling through a result set using session.scroll() > 3) Embedding objects that are: > a) Referred by least by one of the objects on which the query is selecting primarily (parent object) and, > b) that field is in FetchMode.JOIN. > c) Referred by one object which is embedded (embed-xml="true") and uses a different field name to refer to the object than the parent object. > I would like to apologise for the large test case. The bug is quite hard to reproduce, I tried to minimise the test, but this seems the smallest and most simple case I can find. > The stack trace is: > Caused by: org.hibernate.WrongClassException: Object with id: 1 was not of the specified subclass: Customer (loaded object was of wrong class) > at org.hibernate.loader.Loader.instanceAlreadyLoaded(Loader.java:890) > at org.hibernate.loader.Loader.getRow(Loader.java:846) > at org.hibernate.loader.Loader.getRowFromResultSet(Loader.java:305) > at org.hibernate.loader.Loader.loadSingleRow(Loader.java:238) > at org.hibernate.impl.ScrollableResultsImpl.prepareCurrentRow(ScrollableResultsImpl.java:477) > at org.hibernate.impl.ScrollableResultsImpl.next(ScrollableResultsImpl.java:106) > at HbxXmlTest.main(HbxXmlTest.java:90) > The included files are: > Test.hbm.xml : the hbm file to create the classes > HbmXmlTest.java : the the java source to reproduce the issue. > Greetings, > Roland. -- 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: Steve E. (JIRA) <no...@at...> - 2006-06-28 16:44:20
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1050?page=all ] Steve Ebersole updated HHH-1050: -------------------------------- Fix Version: 3.2.1 (was: 3.2.0.cr3) > HQL Unions > ---------- > > Key: HHH-1050 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1050 > Project: Hibernate3 > Type: New Feature > Components: query-hql > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Fix For: 3.2.1 > > > Add the ability to define unions in HQL. Support will be initially limited to only: > 1) scalar queries : select id from Animal union select id from Car > 2) the same entity : from Animal where ... union from Animal where ... > Support both UNION and UNION ALL -- 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: Steve E. (JIRA) <no...@at...> - 2006-06-28 16:44:18
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1499?page=all ] Steve Ebersole updated HHH-1499: -------------------------------- Fix Version: 3.2.1 (was: 3.2.0.cr3) > use subselect fetching for collection join fetches with DISTINCT or firstResult/maxRows > --------------------------------------------------------------------------------------- > > Key: HHH-1499 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1499 > Project: Hibernate3 > Type: Improvement > Components: query-hql > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Fix For: 3.2.1 > > > As a follow on to HHH-1411and HHH-1412... > Both of those above were actually resolved by handling the DISTINCT-ion and/or firstResult/maxRows *in memory*. A better solution is to not honor the join fetch in these cases, perform the requested operation, and then get the requested join fectehd collections through subselect fetches. > As is, this would work as long as the collections have subselect fetching enabled in metadata, but would actually use immediate fetching (n+1) for any collections not defining subselect fetching in metadata. This is due to the way PersistenceContext.initializeNonLazyCollections() currently works. -- 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: Steve E. (JIRA) <no...@at...> - 2006-06-28 16:44:17
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1718?page=all ] Steve Ebersole updated HHH-1718: -------------------------------- Fix Version: 3.2.1 (was: 3.2.0.cr3) > Have multiple bag fetches revert to subselect fetching for all but one of the bags > ---------------------------------------------------------------------------------- > > Key: HHH-1718 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1718 > Project: Hibernate3 > Type: Improvement > Components: query-hql, query-criteria, core > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Fix For: 3.2.1 > > > Follow on to HHH-1413. Multiple bag fetches were simply disallowed as the resolution to that particular case in the interest of working around that issue. > The correct longer term solution is to not fetch all the bags at once, ideally reverting to subselect fetching for all but one of the bags. -- 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: Steve E. (JIRA) <no...@at...> - 2006-06-28 16:44:17
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1775?page=all ] Steve Ebersole updated HHH-1775: -------------------------------- Fix Version: 3.2.1 (was: 3.2.0.cr3) > collection batch fetching > ------------------------- > > Key: HHH-1775 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1775 > Project: Hibernate3 > Type: Improvement > Components: core > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Priority: Minor > Fix For: 3.2.1 > > > I have code local on my box to support "peeking" into the second level cache when determining whether to add a particular entity/collection key to a batch load request. If the given key is contained in the second level cache, then do not batch fetch the entity/collection as it will be initialized from second level cache on access. > However, there are still large inefficiencies when performing this for collections; the biggest of which currently is the fact that we retreive a IdentityMap.entrySet for each and ever call to determine a collectiomn fetch batch. For performance reasons, we should align this with how entity batches are handled where the entity keys considered to be "batch loadable" are tracked seperately on the BatchFetchQueue. -- 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: Steve E. (JIRA) <no...@at...> - 2006-06-28 16:44:17
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1267?page=all ] Steve Ebersole updated HHH-1267: -------------------------------- Fix Version: 3.2.1 (was: 3.2.0.cr3) > HQL: order-by clause column list > -------------------------------- > > Key: HHH-1267 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1267 > Project: Hibernate3 > Type: Improvement > Components: query-hql > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Priority: Minor > Fix For: 3.2.1 > > > HQL currently always results in using qualified column names in the order-by clause. Some databases (ok DB2) actually do not support this in all cases. And really according to the SQL spec, it is not the specified thing to do. Essentially the SQL spec says that if select-clause column aliases are used, those column aliases (or the column indexes) should be used in the order-by clause. > This should be the non-default behavior as it'll be more intensive of the query parser to achieve 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.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Steve E. (JIRA) <no...@at...> - 2006-06-28 16:44:16
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-294?page=all ] Steve Ebersole updated HHH-294: ------------------------------- Fix Version: 3.2.1 (was: 3.2.0.cr3) > implicit join in both subselect and outer query : single join > ------------------------------------------------------------- > > Key: HHH-294 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-294 > Project: Hibernate3 > Type: Improvement > Components: query-hql > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Priority: Minor > Fix For: 3.2.1 > > > See HHH-280 for the details. > Basically, that was fixed by reverting to the old parser output of generating duplicate joins. This should be fixed to use the same join both times for effeciency. > There were a number of ways we might acheive this: > 1) Somehow suspend processing of subqueries until their containing query is completely processed. The trick here is that the join definition from the outer query would already have been resolved when processing the inner query resumes at which point we could simply reuse the join def from the outer query (this is the same thing as putting the implicit join in the outer query *before* the subquery, which works). This approach (while simple in its concept) seems very difficult to acheive with the ANTLR parser. > 2) Perform some post processing sort of like we do with the "join post processing". Yuck! > 3) When attempting to resolve the DotNode (representing the implicit join) take a peek at "child from clauses" to see if any of them defined the same "implicit join path"; if so "promote" that join fragment from the child FromClause to the current FromClause. > I will attempt #3. -- 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: Steve E. (JIRA) <no...@at...> - 2006-06-28 16:42:18
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1850?page=all ] Steve Ebersole updated HHH-1850: -------------------------------- Fix Version: 3.2.0.ga (was: 3.2.0.cr3) > Add of query.setIsolationLevel() methods > ---------------------------------------- > > Key: HHH-1850 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1850 > Project: Hibernate3 > Type: New Feature > Components: core > Reporter: Emmanuel Bernard > Fix For: 3.2.0.ga > > > A reminder for the discussion Steve and Gavin had. Since the result was lost, we probably need to have it again :-) -- 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: <no...@at...> - 2006-06-28 16:35:18
|
Group by does not expand columns
--------------------------------
Key: HHH-1865
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH=
-1865
Project: Hibernate3
Type: Bug
Components: query-hql =20
Environment: Windows XP
JDeveloper 10.1.2.1
Reporter: Nestor Bosc=C3=A1n
Priority: Minor
Hi=20
I need to use Hibernate 3.1.3 to create a query that returns an object and =
a aggregate value like this:=20
select max (t.test_date), t from TestTo t.=20
Because I have an aggregate function I have to define the GROUP BY clause:=
=20
select max (t.test_date), t from TestTo t group by t=20
But I get an error:=20
ORA-00979: not a GROUP BY expression=20
The generated SQL is:=20
select max(testto0_.test_date) as col_0_0_,=20
testto0_.test_value as col_1_0_,=20
testto0_.test_value as test1_0_,=20
testto0_.test_date as test2_0_=20
from TEST testto0_=20
group by testto0_.test_value=20
It seems that Hibernate is expanding all columns of the TestTo class in the=
SELECT statement but not in the GROUP BY statement.=20
The TestTo class:=20
public class TestTo=20
{=20
private int value;=20
private Date date;=20
public TestTo()=20
{=20
}=20
public int getValue()=20
{=20
return value;=20
}=20
public void setValue(int value)=20
{=20
this.value =3D value;=20
}=20
public Date getDate()=20
{=20
return date;=20
}=20
public void setDate(Date date)=20
{=20
this.date =3D date;=20
}=20
}=20
The Mapping File:=20
<hibernate-mapping>=20
<class name=3D"mypackage.TestTo" table=3D"TEST">=20
<id name=3D"value" column=3D"test_value">=20
<generator class=3D"sequence">=20
<param name=3D"sequence">seq_test</param>=20
</generator>=20
</id>=20
<property name=3D"date" column=3D"test_date"/>=20
</class>=20
</hibernate-mapping>
--=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=
.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
|
From: <no...@at...> - 2006-06-28 14:48:21
|
[ http://opensource.atlassian.com/projects/hibernate/browse/EJB-201?pag= e=3Dcomments#action_23457 ]=20 Ren=C3=A9 Treffer commented on EJB-201: ---------------------------------- Ok, this seems to be a WebApp problem, you won't find the normal META-INF/p= ersistence.xml by your ClassLoader. I've found comments of other user havin= g the same problem with Toplink and Tomcat. WEB-INF/classes/META-INF is the correct location for web applications, perh= aps hibernate could give a hint about that? > Ejb3Configuration should output a warning if no persistence.xml is found > ------------------------------------------------------------------------ > > Key: EJB-201 > URL: http://opensource.atlassian.com/projects/hibernate/browse/E= JB-201 > Project: Hibernate Entity Manager > Type: Improvement > Components: EntityManager > Versions: 3.2.0.cr1 > Environment: Any Environment with missing persistence.xml or bad ClassLo= aders > Reporter: Ren=C3=A9 Treffer > > Original Estimate: 30 minutes > Remaining: 30 minutes > > If persistence.xml can't be found javax.ejb.Persistence return's "No Pers= istence found for EntityManager <name>". > However it might help a lot of people if Ejb3Configuration could output a= warning in > public EntityManagerFactory createEntityManagerFactory(String emName, Map= integration) { > The warning might be something like "No META-INF/persistence.xml found". = In my case it looks like a Jetty6 ClassLoader problem, a simple warning mig= ht have saved me hours of bugtracking. > A sample Trace: > 93676 [btpool0-20] INFO org.hibernate.ejb.Version - Hibernate EntityMan= ager 3.2.0.CR1 > 93712 [btpool0-20] INFO org.hibernate.cfg.annotations.Version - Hiberna= te Annotations 3.2.0.CR1 > 93729 [btpool0-20] INFO org.hibernate.cfg.Environment - Hibernate 3.2 c= r2 > 93736 [btpool0-20] INFO org.hibernate.cfg.Environment - hibernate.prope= rties not found > 93739 [btpool0-20] INFO org.hibernate.cfg.Environment - Bytecode provid= er name : cglib > 93752 [btpool0-20] INFO org.hibernate.cfg.Environment - using JDK 1.4 j= ava.sql.Timestamp handling > 93923 [btpool0-20] DEBUG org.hibernate.ejb.Ejb3Configuration - Trying to= find persistence unit: losem > <<< Here should be a "WARN org.hibernate.ejb.Ejb3Configuration - No META-= INF/persistence.xml found" > followed by=20 > java.lang.ExceptionInInitializerError > ...... > Caused by: javax.persistence.PersistenceException: No Persistence provide= r for EntityManager named losem > at javax.persistence.Persistence.createEntityManagerFactory(Persi= stence.java:41) > at javax.persistence.Persistence.createEntityManagerFactory(Persi= stence.java:27) > at de.rtjava.los.pmanager.PersistenceManager.<clinit>(Persistence= Manager.java:58) > ... 29 more > Good luck and a big thank-you fr Hibernate! --=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= .jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
From: Dave R. (JIRA) <no...@at...> - 2006-06-28 13:59:25
|
New dialect for Solid database for Hibernate 3.1.3 and Solid 4.5 onwards
------------------------------------------------------------------------
Key: HHH-1864
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1864
Project: Hibernate3
Type: New Feature
Components: core
Environment: New dialect for Solid database for Hibernate 3.1.3 and Solid 4.5 onwards
Reporter: Dave Richardson
Attachments: SolidDialect.java
I have written a Dialect class for the Solid database (www.solidtech.com) release 4.5 onwards.
The SolidDialect is designed to be used with Solid release 4.5 or later.
It does however work with Solid release 4.2 if the new features in Solid 4.5
are not used. These are:
- referential actions CASCADE, SET NULL, SET DEFAULT, RESTRICT and NO ACTION.
- syntax for windowing over the result set: SELECT ... LIMIT ... OFFSET ...
- new functions SOUNDEX() and DIFFERENCE() for approximate string comparisons.
- automatic removing of constraints, with: DROP TABLE ... CASCADE CONSTRAINTS.
I ran the Hibernate test suites with the SolidDialect using Hibernate 3.1.3.
As a baseline I also ran the test suite against HSQLDB giving the following results:
Tests: 806, unsuccessful: 12, success rate: 98.51%
I had initially expected 100%, but the following comment from Gavin King in the
Hibernate Forum explains the main reason:
"There are some expected failures in the HB3 test suite.
Basically, some obscure stuff that we broke going from HB2->HB3 and plan to fix "someday"."
The results with the SolidDialect are:
Tests: 806, unsuccessful: 36, success rate: 95.53%
This compares reasonably well with HSQLDB.
Note: some of the Hibernate tests rely on the availability of temporary tables.
This is supported by Solid but requires an appropriate license (with support for so-called M-tables).
I have sent the dialect and the results of the Hibernate test suite together with a detailed analysis of the results to Solid.
They are currently analysing this information. If necessary I can provide a contact person at Solid.
I hope the dialect can be included in an official distribution as soon as possible.
Test Results Analysis
=====================
I analyzed the results and assigned the reason for failure to the following categories:
- Feature not currently supported by the Solid database.
- Error or non-standard behaviour in the Solid database engine and/or JDBC driver.
- Error or missing support in the SolidDialect for Hibernate
- Problem with the test case itself
- Error in Hibernate itself.
This led to the following:
#ERRORS CATEGORY
11 Feature not supported by Solid
17 Probable Solid error or non-standard behaviour
0 Problem with SolidDialect
6 Problem with Hibernate test case
2 Hibernate bug
36 Total errors
I patched three test cases and corrected one bug in Hibernate to acheive these results:
hql.ASTParserLoadingTest:
- changed query "from Animal where bodyWeight > 1e-38"
to "from Animal where bodyWeight > 1e-12" since Solid supports a maximum
precision of 16 and the precision is not the focus of the test.
legacy.MasterDetailTest:
- There are numerous dialect checks in this test. Many tests are omitted
depending on the dialect. For MySQL the transaction isolation level
is explicitly set for this test case.
The test was patched to do this for Solid too.
readonly.ReadOnlyTest:
The test case initialises an attribute using:
dp.setX( new BigDecimal( 0.1d ).setScale(19, BigDecimal.ROUND_DOWN) );
Solid supports a maximum precision of 16.
The test case was patched to use 12 instead of 19.
Then only testReadOnlyOnProxiesFailureExpected failed later as it does with
HSQLDB with the following diagnostic:
org.hibernate.TransientObjectException: Instance was not associated with the session
at org.hibernate.engine.StatefulPersistenceContext.setReadOnly(
StatefulPersistenceContext.java:1095)
at org.hibernate.impl.SessionImpl.setReadOnly(SessionImpl.java:1795)
at org.hibernate.test.readonly.ReadOnlyTest.
testReadOnlyOnProxiesFailureExpected(ReadOnlyTest.java:50)
Research showed that this is a known bug (HHH-1352).
I suppose I should submit separate patches for these modified test cases?
The Hibernate bug corrected is in the statistics gathering class StatisticsImpl
which under certain circumstances causes the test case stats.StatsTestestQueryStatGathering
to fail with the following diagnostic:
junit.framework.ComparisonFailure:
expected:<from Continent> but was:<null>
at org.hibernate.test.stats.StatsTest.testQueryStatGathering(StatsTest.java:136)
I'll submit a separate patch for this.
Here are now some details about the errors:
Category: Feature not supported by Solid
----------------------------------------
Of the 11 errors due to unsupported features, 6 are caused by functions in
ORDER BY clauses and 3 by missing support for ResultSet.getBlob().
A further error is caused by the test case joinedsubclass.JoinedSubclassTest
which leads to the following SQL fragment:
where (this_.address, this_.zip, this_.country) in ((?, ?, ?), (?, ?, ?))
This is apparently not currently supported by Solid.
Note: this test is skipped for HSQLDB, PostgreSQL, MySQL and DB2.
The last error due to an unsupported feature occurs in the test case
legacy.FooBarTest.testCollectionsInSelect
The test issues the following HQL query:
select count(*) from Bar as bar, bar.component.glarch.proxyArray as g
where g.id in indices(bar.baz.fooArray)
This leads to the following SQL fragment:
...and ((proxyarray2_.tha_key in(select fooarray4_.i from fooArray fooarray4_ where ...))
Solid reports an exception (comparison between incompatible types).
proxyarray2_.tha_key is of type VARCHAR(32) and fooarray4_.i is of type INTEGER.
Some databases apparently support this comparison.
Note: this test is skipped for HSQLDB, MySQL, DB2 and Oracle.
Category: Problem with Hibernate test case
------------------------------------------
Of the 6 errors 5 occur in the test hql.HQLTest producing the following diagnostics:
Old query translator did not throw an exception, the new one did
SQL is not the same as the old SQL
New query translator did *NOT* throw an exception, the old one did
This was not analyzed any further since the errors also occur with HSQLDB.
The other error was in proxy.ProxyTest.testFullyLoadedPCSerialization
which produced the following diagnostic:
junit.framework.AssertionFailedError:
unexpected DP delete count expected:<50> but was:<51>
at org.hibernate.test.proxy.ProxyTest.testFullyLoadedPCSerialization(ProxyTest.java:291)
This test also fails with HSQLDB with the same diagnostic.
Possibly a problem with the test itself.
Category: Hibernate bug
-----------------------
readonly.ReadOnlyTest.testReadOnlyOnProxiesFailureExpected fails as follows:
org.hibernate.TransientObjectException:
Instance was not associated with the session
at org.hibernate.engine.StatefulPersistenceContext.setReadOnly(StatefulPersistenceContext.java:1095) at org.hibernate.impl.SessionImpl.setReadOnly(SessionImpl.java:1795)
at org.hibernate.test.readonly.ReadOnlyTest.testReadOnlyOnProxiesFailureExpected(ReadOnlyTest.java:50)
Research showed that this is a known bug (HHH-1352).
legacy.SQLLoaderTest.testReturnPropertyComponentRename fails as follows:
java.sql.SQLException: [Solid JDBC 04.50.0058] Column not found
This test uses a native SQL query defined in the Hibernate mapping file:
select id, nickName as n2, name, subName as otherSubName, subName1 from Componentizable
The error is in Hibernate trying to access the result set using subName as the
column name instead of the defined alias otherSubName.
Research showed that this is a known bug (HHH-1515).
I hope the dialect meets with your approval and look forward to it
being included in the official distribution!
--
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: Steve E. (JIRA) <no...@at...> - 2006-06-28 13:26:17
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1552?page=all ] Steve Ebersole resolved HHH-1552: --------------------------------- Resolution: Fixed done > Error when using ?1 and parameterList > ------------------------------------- > > Key: HHH-1552 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1552 > Project: Hibernate3 > Type: Bug > Components: query-hql > Versions: 3.2.0.alpha1 > Reporter: Emmanuel Bernard > Assignee: Steve Ebersole > Priority: Blocker > Fix For: 3.2.0 > > > select item from Item item where item.name in ( :n ) > query.setParameterList("n", list); works > select item from Item item where item.name in ( ?1 ) > query.setParameterList("1", list); > raise an exception > java.lang.NullPointerException > at org.hibernate.hql.ast.ParameterTranslationsImpl.getNamedParameterSqlLocations(ParameterTranslationsImpl.java:59) > at org.hibernate.loader.hql.QueryLoader.getNamedParameterLocs(QueryLoader.java:458) > at org.hibernate.loader.hql.QueryLoader.bindNamedParameters(QueryLoader.java:481) > at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1577) > at org.hibernate.loader.Loader.doQuery(Loader.java:661) > at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224) > at org.hibernate.loader.Loader.doList(Loader.java:2145) > at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2029) > at org.hibernate.loader.Loader.list(Loader.java:2024) > at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:375) > at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:333) > at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:172) > at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1105) > at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79) > Note that select item from Item item where item.name = ?1 > works like a charm -- 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: <no...@at...> - 2006-06-28 12:15:16
|
Ejb3Configuration should output a warning if no persistence.xml is found
------------------------------------------------------------------------
Key: EJB-201
URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB=
-201
Project: Hibernate Entity Manager
Type: Improvement
Components: EntityManager =20
Versions: 3.2.0.cr1 =20
Environment: Any Environment with missing persistence.xml or bad ClassLoad=
ers
Reporter: Ren=C3=A9 Treffer
If persistence.xml can't be found javax.ejb.Persistence return's "No Persis=
tence found for EntityManager <name>".
However it might help a lot of people if Ejb3Configuration could output a w=
arning in
public EntityManagerFactory createEntityManagerFactory(String emName, Map i=
ntegration) {
The warning might be something like "No META-INF/persistence.xml found". In=
my case it looks like a Jetty6 ClassLoader problem, a simple warning might=
have saved me hours of bugtracking.
A sample Trace:
93676 [btpool0-20] INFO org.hibernate.ejb.Version - Hibernate EntityManag=
er 3.2.0.CR1
93712 [btpool0-20] INFO org.hibernate.cfg.annotations.Version - Hibernate=
Annotations 3.2.0.CR1
93729 [btpool0-20] INFO org.hibernate.cfg.Environment - Hibernate 3.2 cr2
93736 [btpool0-20] INFO org.hibernate.cfg.Environment - hibernate.propert=
ies not found
93739 [btpool0-20] INFO org.hibernate.cfg.Environment - Bytecode provider=
name : cglib
93752 [btpool0-20] INFO org.hibernate.cfg.Environment - using JDK 1.4 jav=
a.sql.Timestamp handling
93923 [btpool0-20] DEBUG org.hibernate.ejb.Ejb3Configuration - Trying to f=
ind persistence unit: losem
<<< Here should be a "WARN org.hibernate.ejb.Ejb3Configuration - No META-IN=
F/persistence.xml found"
followed by=20
java.lang.ExceptionInInitializerError
......
Caused by: javax.persistence.PersistenceException: No Persistence provider =
for EntityManager named losem
at javax.persistence.Persistence.createEntityManagerFactory(Persist=
ence.java:41)
at javax.persistence.Persistence.createEntityManagerFactory(Persist=
ence.java:27)
at de.rtjava.los.pmanager.PersistenceManager.<clinit>(PersistenceMa=
nager.java:58)
... 29 more
Good luck and a big thank-you fr Hibernate!
--=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=
.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
|
|
From: Emmanuel B. (JIRA) <no...@at...> - 2006-06-28 12:05:19
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1863?page=all ] Emmanuel Bernard resolved HHH-1863: ----------------------------------- Resolution: Rejected usage questions should be posted on the user forum http://forum.hibernate.org Thanks > Sequences generated in PostgreSQL not respect curent table schema name. > ----------------------------------------------------------------------- > > Key: HHH-1863 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1863 > Project: Hibernate3 > Type: Bug > Versions: 3.2.0.cr2 > Reporter: Grigoras Cristinel > Priority: Minor > > > Hi, > I have a table where de ID is generate using sequence. > The table is inside schema "newschema". > The sequence is generate inside public schema. How can i create sequence inside curent table schema. > Cristi -- 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: Mattias J. (JIRA) <no...@at...> - 2006-06-28 11:10:17
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1853?page=comments#action_23454 ] Mattias Jiderhamn commented on HHH-1853: ---------------------------------------- Click the link to the forum, and post your question there. JIRA is for bug/issue tracking, not support. > CREATE SCHEMA inside database-object need to execute before tables are created > ------------------------------------------------------------------------------ > > Key: HHH-1853 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1853 > Project: Hibernate3 > Type: Improvement > Versions: 3.1.3 > Environment: hsqldb 1.8.0 > Reporter: Mattias Jiderhamn > Priority: Minor > > > In order to have Hibernate create database schemas for hsqldb, you have to insert a <database-object> in your mapping file (http://forums.hibernate.org/viewtopic.php?p=2305138). Problem is, all the database-object statements are executed after the tables are created, so tables in non-default schemas will not be created. To get around this, you have to first use Configuration.generateSchemaCreationScript() to get the schemas, and then Configuration.generateSchemaUpdateScript() to get the tables inside the schemas. > (This is a bit problematic when using Springs LocalSessionFactoryBean) -- 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: Grigoras C. (JIRA) <no...@at...> - 2006-06-28 11:04:18
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1853?page=comments#action_23453 ] Grigoras Cristinel commented on HHH-1853: ----------------------------------------- Hi, PostgresSQL will not create the schema. How can i fix that ? Cristi > CREATE SCHEMA inside database-object need to execute before tables are created > ------------------------------------------------------------------------------ > > Key: HHH-1853 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1853 > Project: Hibernate3 > Type: Improvement > Versions: 3.1.3 > Environment: hsqldb 1.8.0 > Reporter: Mattias Jiderhamn > Priority: Minor > > > In order to have Hibernate create database schemas for hsqldb, you have to insert a <database-object> in your mapping file (http://forums.hibernate.org/viewtopic.php?p=2305138). Problem is, all the database-object statements are executed after the tables are created, so tables in non-default schemas will not be created. To get around this, you have to first use Configuration.generateSchemaCreationScript() to get the schemas, and then Configuration.generateSchemaUpdateScript() to get the tables inside the schemas. > (This is a bit problematic when using Springs LocalSessionFactoryBean) -- 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: Grigoras C. (JIRA) <no...@at...> - 2006-06-28 11:02:18
|
Sequences generated in PostgreSQL not respect curent table schema name.
-----------------------------------------------------------------------
Key: HHH-1863
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1863
Project: Hibernate3
Type: Bug
Versions: 3.2.0.cr2
Reporter: Grigoras Cristinel
Priority: Minor
Hi,
I have a table where de ID is generate using sequence.
The table is inside schema "newschema".
The sequence is generate inside public schema. How can i create sequence inside curent table schema.
Cristi
--
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-28 10:04:17
|
[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-362?page=all ] Emmanuel Bernard resolved ANN-362: ---------------------------------- Fix Version: 3.2.0 Resolution: Fixed fixed (part of hibernate core) > Specification of table @Table name with quotes using backticks fails with @OneToMany mapping > -------------------------------------------------------------------------------------------- > > Key: ANN-362 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-362 > Project: Hibernate Annotations > Type: Bug > Versions: 3.2.0.cr1 > Environment: Tomcat 5.5 > JDK 1.5.0_05-b05 (Win32) > PostgreSQL 8.1 > Reporter: Niko Horn > Priority: Blocker > Fix For: 3.2.0 > > > Scenario: > Simple one-to-many mapping (1 User has n Roles) > User-Class: > @Entity() > @Table(name = "`Users`") > public class User > [...] > @OneToMany > @JoinTable > ( > name = "UserRoles", > joinColumns = { @JoinColumn( name="userId") }, > inverseJoinColumns = @JoinColumn( name="roleId") > ) > private Set<Role> roles; > [...] > Role-Class: > @Entity > @Table(name = "`Roles`") > public class Role > [...] > If the User-Table name is given with backticks (for neccessary quotes in PostgreSQL if capitals are used), Tomcat starts with exception > org.hibernate.MappingException: Unable to find physical table: Users > The problem is in Class org.cfg.hibernate.mappings in the Method getLogicalTableName(). The generated key variable > String key = buildTableNameKey( schema, catalog, physicalName ); > does not contain the neccessary backticks to determine the value from the tableNameBinding HashMap. > A fast fix would be nice :-) -- 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-28 09:54:21
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1862?page=all ] Emmanuel Bernard resolved HHH-1862: ----------------------------------- Resolution: Rejected Since you cannot change an object type in java (ie morphing a object x into an object y, this does not make sense to hibernate either > one type of subclass object can be persist in the database with the same id for another type of object which is extended by the same class as first one. > -------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: HHH-1862 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1862 > Project: Hibernate3 > Type: New Feature > Components: core > Versions: 3.0.5 > Reporter: Anil Garg > > > e.g. > lets say there are two subclasses x and y which are extended by the class u. > one object of x is persisted into the database with id say 1. > in the later there should be option in hibernate by which i can convert x object into y object i mean to say the y object can be saved in the database with same id as x. -- 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-28 09:44:18
|
[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-360?page=all ] Emmanuel Bernard resolved ANN-360: ---------------------------------- Resolution: Rejected This is actually a misuse of mappedBy should be @OneToMany(mappedBy="chargeType") private List<Charge> charges; @OneToMany(mappedBy="product") private List<Charge> charges; > Many-To-Many relationship with attributes on relationship > --------------------------------------------------------- > > Key: ANN-360 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-360 > Project: Hibernate Annotations > Type: Bug > Components: binder > Versions: 3.2.0.cr1 > Environment: Hibernate 3.2.0cr2, HibernateAnnotations 3.2.0cr1, HQL > Reporter: Peter Muir > Priority: Critical > Attachments: manytomanywithattributes.zip > > > Use a composite foreign key on an entity (A) to model an many to many entity(B)-entity(C) relationship with attributes on the relationship. > This is supported using hibernate mapping files. > See http://forum.hibernate.org/viewtopic.php?t=958753 for more discussion. -- 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: Anil G. (JIRA) <no...@at...> - 2006-06-28 09:27:20
|
one type of subclass object can be persist in the database with the same id for another type of object which is extended by the same class as first one.
--------------------------------------------------------------------------------------------------------------------------------------------------------
Key: HHH-1862
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1862
Project: Hibernate3
Type: New Feature
Components: core
Versions: 3.0.5
Reporter: Anil Garg
e.g.
lets say there are two subclasses x and y which are extended by the class u.
one object of x is persisted into the database with id say 1.
in the later there should be option in hibernate by which i can convert x object into y object i mean to say the y object can be saved in the database with same id as x.
--
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: Steve E. (JIRA) <no...@at...> - 2006-06-28 05:44:58
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1539?page=all ] Steve Ebersole updated HHH-1539: -------------------------------- Fix Version: (was: 3.2.0) > JDK 1.4 dependencies in ResultSetWrapper, SerializableBlob and SerializableClob > ------------------------------------------------------------------------------- > > Key: HHH-1539 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1539 > Project: Hibernate3 > Type: Bug > Components: core > Reporter: Emmanuel Bernard > Priority: Minor > Attachments: Hibernate3.1.2 Compilation Errors.xls > > > All these classes are simple wrappers. > We should write a proxy or AOPize that to not depend on JDK 1.4 APIs. -- 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: Steve E. (JIRA) <no...@at...> - 2006-06-28 05:43:00
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1543?page=all ] Steve Ebersole closed HHH-1543: ------------------------------- Fix Version: (was: 3.2.0) Resolution: Won't Fix fetching is a hint, not a guarentee > query cache and fetches > ----------------------- > > Key: HHH-1543 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1543 > Project: Hibernate3 > Type: Bug > Components: core > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Priority: Minor > > > Whenever query results are served from the query cache, fetched associations are not initialized (regardless of whether join fetching is specified in the query or the metadata). > For example, consider: > from Customer c > join fetch c.orders > When the info is pulled from the query cache, the Customer entity is rebuilt based on the Customer-id cached in the query cache. However, the Customer.orders role is never forced to initialize. It is left to initialize itself on first access. The same is true even if the fetching is enabled in the metadata. > Same for entity fetches. > Same for cached criteria query results -- 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.
