July 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-82) Migrate ant build to maven2

by Hardy Ferentschik (JIRA)

Migrate ant build to maven2 --------------------------- Key: HSEARCH-82 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-82 Project: Hibernate Search Issue Type: Task Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Switch from ant to maven2 as build tool. Initally just try to build HSearch with maven. Once it works we can see if we can extract a common HibernateExt parent pom. -- 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

17 years

4
10
0 / 0

[Hibernate-JIRA] Créée: (HHH-2060) To be able to use <generator> with <composite-id>

by Xavier Brénuchon (JIRA)

To be able to use <generator> with <composite-id> ------------------------------------------------- Key: HHH-2060 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2060 Project: Hibernate3 Type: Improvement Versions: 3.2.0.cr4 Environment: Hibernate 3.x Reporter: Xavier Brénuchon Hello, This is the continuation of HB-389 We develop an application which has very strong need for performance with several tens of million recordings. Partitioning is a need. So for that, I use <composite-id>. But my primary key is not a natural key, but a real technical key : - column of partitioning for optimization of the data base - column of technical id So I need to have a generator, for exemple : <composite-id name="id" class="IdPartition"> <key-property name="org" type="string" column="ORG"/> <key-property name="id" type="long" column="ID"/> <generator class="fr.test.xavier.IdPartitionGenerator"> <param name="table">TAB_SEQ</param> <param name="column">LAST</param> </generator> </composite-id> The good news is that Hibernate can use that (HB-389). In fact, it is enough to modify the DTD to authorize <generator> in <composite-id> and it is all. The current code of Hibernate manages it very well. Is it possible that Hibernate is enriched by this functionality? -- 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

17 years

7
17
0 / 0

[Hibernate-JIRA] Created: (EJB-254) Allow DataSource overriding through createEntityManager(String, Map override)

by Emmanuel Bernard (JIRA)

Allow DataSource overriding through createEntityManager(String, Map override) ----------------------------------------------------------------------------- Key: EJB-254 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-254 Project: Hibernate Entity Manager Type: Improvement Components: EntityManager Reporter: Emmanuel Bernard Assigned to: Emmanuel Bernard Fix For: 3.2.1 -- 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

17 years, 1 month

3
7
0 / 0

[Hibernate-JIRA] Created: (HHH-3204) core-manual-parent pom doesn't build because core-parent doesn't contain the jboss repo

by Geoffrey De Smet (JIRA)

core-manual-parent pom doesn't build because core-parent doesn't contain the jboss repo --------------------------------------------------------------------------------------- Key: HHH-3204 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3204 Project: Hibernate3 Issue Type: Bug Components: build Reporter: Geoffrey De Smet to reproduce: mv ~/.m2/repository ~/.m2/backup_local_repository cd core-parent mvn clean install cd core-manual-parent mvn clean install result ===== Reason: POM 'org.jboss.maven.plugins:maven-jdocbook-plugin' not found in repository: Unable to download the artifact from any repository org.jboss.maven.plugins:maven-jdocbook-plugin:pom:2.1.0 from the specified remote repositories: central (http://repo1.maven.org/maven2) for project org.jboss.maven.plugins:maven-jdocbook-plugin solution ======= Just add this in the core-parent pom: <repositories> <repository> <id>jboss</id> <url>http://repository.jboss.com/maven2/</url> </repository> <repository> <id>jboss-snapshot</id> <url>http://snapshots.jboss.org/maven2</url> <snapshots> <enabled>true</enabled> </snapshots> <releases> <enabled>false</enabled> </releases> </repository> </repositories> <pluginRepositories> <pluginRepository> <id>jboss</id> <url>http://repository.jboss.com/maven2/</url> </pluginRepository> </pluginRepositories> -- 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

17 years, 1 month

2
5
0 / 0

[Hibernate-JIRA] Created: (EJB-294) Hibernate throwing QueryException when using alias for aggregate functions in named queries

by Saravanabavagugan Vengadasundaram (JIRA)

Hibernate throwing QueryException when using alias for aggregate functions in named queries ------------------------------------------------------------------------------------------- Key: EJB-294 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-294 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.2.0.ga Environment: Hibernate 3.2 GA, Reporter: Saravanabavagugan Vengadasundaram Hibernate throwing QueryException when using alias for aggregate functions in named queries. The following query does not work: select sum(emp.salary) as totalSalary from Employee as emp select sum(emp.salary) totalSalary from Employee as emp but this works: select sum(emp.salary) from Employee as emp -- 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

17 years, 1 month

6
9
0 / 0

[Hibernate-JIRA] Created: (HHH-3214) Update unit tests and config files to use non-depracated Oracle dialects

by Gail Badner (JIRA)

Update unit tests and config files to use non-depracated Oracle dialects ------------------------------------------------------------------------ Key: HHH-3214 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3214 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.6 Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.2.x There are still references to OracleDialect and Oracle9Dialect in hibernate.properties and unit tests. These dialects are depracated so references to them in unit tests and config files (e.g, hibernate.properties) should be changed to refer to non-deprecated dialects. -- 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

17 years, 1 month

2
9
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

17 years, 1 month

4
3
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

17 years, 1 month

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

17 years, 1 month

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2792) Session.delete is validate all fields are null

by Daniel Passos (JIRA)

Session.delete is validate all fields are null ---------------------------------------------- Key: HHH-2792 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2792 Project: Hibernate3 Issue Type: Bug Components: core Reporter: Daniel Passos session.delete operation would not have to validate if the fields are null The problem in DefaultDeleteEventListener.deleteEntity -> Nullability.checkNullability -- 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

17 years, 1 month

6
5
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues July 2008