December 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (BVAL-32) Describe what is happening when a composition is not consistent

by Emmanuel Bernard (JIRA)

Describe what is happening when a composition is not consistent --------------------------------------------------------------- Key: BVAL-32 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-32 Project: Bean Validation Issue Type: Improvement Components: spec-general 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.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3528) FETCH JOIN query doesn't work in a StatelessSession

by Oscar Pearce (JIRA)

FETCH JOIN query doesn't work in a StatelessSession --------------------------------------------------- Key: HHH-3528 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3528 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1, 3.2.6 Environment: Hibernate core 3.3.1 and 3.2.6, HSQLDB 1.8.0 and PostgreSQL 8.1 Reporter: Oscar Pearce Attachments: slsession.zip, StatelessSessionImpl.patch A query with an explicit JOIN FETCH, such as the following: from DomainObject obj join fetch obj.a fails when run in a StatelessSession, giving the following exception: org.hibernate.SessionException: proxies cannot be fetched by a stateless session at org.hibernate.impl.StatelessSessionImpl.immediateLoad(StatelessSessionImpl.java:243) at org.hibernate.proxy.AbstractLazyInitializer.initialize(AbstractLazyInitializer.java:95) at org.hibernate.proxy.AbstractLazyInitializer.getImplementation(AbstractLazyInitializer.java:140) at org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:190) The attached zip file contains a small project (buildable with maven) that demonstrates the problem. Applying the patch to StatelessSessionImpl fixes it. The cause of the problem is with the internalLoad method of StatelessSessionImpl. The method currently first tries to generate a proxy and, only if no proxy is available, then it uses the data that it loaded as part of the query. The patch changes it to use any loaded data from the query in preference to creating a proxy. (I suspect that the check for eager should be omitted, and that an exception should be thrown if getEntity fails and no proxy can be created, but I don't know the code well enough to be sure of that.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3053) Left Outer Join on Unmapped Tables

by Ravi Bala (JIRA)

Left Outer Join on Unmapped Tables ---------------------------------- Key: HHH-3053 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3053 Project: Hibernate3 Issue Type: Bug Components: query-hql Affects Versions: 3.2.1 Environment: Hibernate 3, Oracle 10g Reporter: Ravi Bala I am trying to use left outer join on two unmapped tables. How is this possible in HQL? I tried to see if there is any such problem submitted already from the forums, but I could not find one. Please let me know the link if this is already discussed. Here is the problem: Table A Table B I want to use Select a.field1, b.field2 from A a left outer join B b on a.field1 = b.field1 Thanks, Ravi -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

4
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3522) Null value cannot be cache using hibernate

by Lao Shing Kit (JIRA)

Null value cannot be cache using hibernate -------------------------------------------- Key: HHH-3522 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3522 Project: Hibernate Core Issue Type: Bug Components: caching (L2) Environment: Hibernate 3.3.1, Ehcache 1.5, Java1.5 Reporter: Lao Shing Kit I'm using Hibernate with 2nd level cache using Ehcache. We found that if the result returned using session.get() (searching by primary key) is NULL, the value will not be cached in 1st level and 2nd level cache and SQL will be fired to database. There is no problem if the value retuurned is not null for the same entity. I have debug using the hibernate and ehcache source and I'm sure that the cache is enabled and called properly. Actually the null value is expected to be cached also. I have browser all hibernate and ehcache documentation and forum and no related config is available. So, is it a bug? Thanks all for your help! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3455) Component polymorphism (<subclass> within <component>)

by Jasper Blues (JIRA)

Component polymorphism (<subclass> within <component>) ------------------------------------------------------ Key: HHH-3455 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3455 Project: Hibernate3 Issue Type: Improvement Components: core Reporter: Jasper Blues The following feature request occurs on the Hibernate forums from time to time - it would be especially useful in mapping complex legacy schemas: <class name="Critter"> <component name="breathingStrategy" class="BreathingStrategy"> <discriminator column="BREATHING_STRATEGY" type="integer" /> <subclass name="Lungs" discriminator-value="0" > <set name="alveoli"> <key column="CRITTER_ID" /> <one-to-many class="Alveolus" /> </set> </subclass> <subclass name="Gills" discriminator-value="1" > <set name="alveoli"> <key column="CRITTER_ID" /> <one-to-many class="Gill" /> </set> </subclass> </component> </class> Will a patch that implements this feature be accepted? What do you think if there was an option to inherit a discriminator from the owning entity? How about some convention over configuration? By default the discriminator from the owning entity is inherited, unless one is supplied at the component level. Would an equivalent annotation mapping be required? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
4
0 / 0

[Hibernate-JIRA] Created: (BVAL-83) Take TraversableResolver contract into account

by Emmanuel Bernard (JIRA)

Take TraversableResolver contract into account ---------------------------------------------- Key: BVAL-83 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-83 Project: Bean Validation Issue Type: New Feature Components: ri-general Reporter: Emmanuel Bernard Fix For: 1.0 public draft -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (BVAL-38) Add built-in constraints

by Emmanuel Bernard (JIRA)

Add built-in constraints ------------------------ Key: BVAL-38 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-38 Project: Bean Validation Issue Type: New Feature Components: ri-general, spec-general Reporter: Emmanuel Bernard @NotNull @Null @AssertFalse @AssertTrue @Digits(integer, fraction) @Past @Future @Min / @Max @Size (String collection, arrays) Probably need: @Like(caseSensitive, escapeChar) or @Contains(startWith, endWith, caseSentitive) @RegExp seems a complex problem Maybe @Email, @URL as they are standardized in HTML 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.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
6
0 / 0

[Hibernate-JIRA] Created: (BVAL-80) Implement sequences on group interfaces and group inheritance

by Emmanuel Bernard (JIRA)

Implement sequences on group interfaces and group inheritance ------------------------------------------------------------- Key: BVAL-80 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-80 Project: Bean Validation Issue Type: New Feature Components: ri-general Reporter: Emmanuel Bernard Fix For: 1.0 public draft -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2920) Polymorphic association with explicit table_per_class strategy: properties of subclass are not retrieved by queries.

by Andrea Silva (JIRA)

Polymorphic association with explicit table_per_class strategy: properties of subclass are not retrieved by queries. -------------------------------------------------------------------------------------------------------------------- Key: HHH-2920 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2920 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.5 Environment: Java 1.5 - Hypersonic DB - Standalone application Reporter: Andrea Silva Priority: Minor Attachments: src.zip Item class has a one-to-many association to Bid. Bid class has a subclass called CashBid (meaningless design I know, but that's not the point). If I create and save an instance of Item with an associated CashBid, when I query for items the properties defined in CashBid are not retrieved. NB Bid is not mapped as abstract. Here is a code snippet: ... // First Session Session session = sessionFactory.openSession(); Transaction transaction = session.beginTransaction(); Bid bid = new CashBid(new BigDecimal(100.0d), "euro"); Item item = new Item("pc"); Serializable bidId = session.save(bid); item.addBid(bid); session.save(item); transaction.commit(); session.close(); // Second Session session = sessionFactory.openSession(); transaction = session.beginTransaction(); //session.load(CashBid.class, bidId); Query query = session.createQuery("from Item"); List<Item> list = query.list(); for (Item item_ : list) { System.out.println(item_); } transaction.commit(); session.close(); ... The bid in the item retrieved by the query is a CashBid (that's correct) but the properties that are defined in CashBid and not in Bid are null. If I uncomment the line //session.load(CashBid.class, bidId); the problem is not there anymore. If Bid is not mapped as abstract the problem doesn't show. My apologies if I'm just missing something very obvious. Please find the source code and the mappings attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

4
5
0 / 0

[Hibernate-JIRA] Created: (HHH-3371) Criteria Query Issue with Projection and restriction

by Michael Kuhinica (JIRA)

Criteria Query Issue with Projection and restriction ---------------------------------------------------- Key: HHH-3371 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3371 Project: Hibernate3 Issue Type: Bug Components: query-criteria Affects Versions: 3.2.6 Environment: Hibernate version: 3.2.6ga, MySQL 5 Reporter: Michael Kuhinica When I try to add a restriction to a property with a projection, hibernate generate the SQL using the property alias on the where clause instead of the property name. Here is an code example: Criteria c = session.createCriteria(Customer.class).setProjection( Projections.projectionList() .add(Projections.property(Customer.PROP_ID), "id") .add(Projections.property(Customer.PROP_NAME), "name") ) .add(Restrictions.like(Customer.PROP_EMAIL, email)) .add(Restrictions.like(Customer.PROP_NAME, name)); And the generated SQL: select this_.ctm_id as y0_, this_.ctm_name as y1_ from customers this_ where this_.ctm_mail like ? and y1_ like ? Notice that hibernate used the right name for the customer e-mail (that has no projection on it) but it used an alias for the name that have a projection set. See: http://forum.hibernate.org/posting.php?mode=editpost&p=2388756 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues December 2008