hibernate-issues — Hibernate JIRA Notifications

[Hibernate-issues] [Hibernate-JIRA] Commented: (HHH-1813) 2nd level cached collections are locked causing a cache miss

[Assaf B. (JIRA) <no...@at...>]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1813?page=comments#action_23267 ] 

Assaf Berg commented on HHH-1813:
---------------------------------

By the way, if I load the same entity 5 times in a row I will get 5 misses on its collection. Using nonstrict-read-write strategy I get 1 miss and 4 hits, which is better but I expect the first load to hit as well because I've just inserted this entity.

> 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

[Hibernate-issues] [Hibernate-JIRA] Created: (HHH-1815) Add support for batch operations in StatelessSession

[Eric W. (JIRA) <no...@at...>]

Add support for batch operations in StatelessSession
----------------------------------------------------

         Key: HHH-1815
         URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1815
     Project: Hibernate3
        Type: Improvement

  Components: core  
 Environment: all
    Reporter: Eric Williams
    Priority: Minor


The principal use cases for StatelessSession seems to be in batch-oriented processing. However, there is no support for batch inserts or updates of persistent entities in the StatelessSession interface. This severely handicaps its usefulness for batch data loading.

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

[Hibernate-issues] [Hibernate-JIRA] Commented: (HBX-620) Bad hbm2hbmxml reverse-engineer

[Mike D. (JIRA) <no...@at...>]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HBX-620?page=comments#action_23268 ] 

Mike Desjardins commented on HBX-620:
-------------------------------------

FYI, here's a related case in the forums...

http://forum.hibernate.org/viewtopic.php?p=2308784#2308784



> Bad hbm2hbmxml reverse-engineer
> -------------------------------
>
>          Key: HBX-620
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-620
>      Project: Hibernate Tools
>         Type: Bug

>   Components: reverse-engineer
>  Environment: Hibernate tools 3.1.0 beta4, MySQL 4.1.12
>     Reporter: Matteo
>  Attachments: ArticoliOfferti.hbm.xml, OfferteFornitori.hbm.xml, ddl.sql
>
>
> Reverse engineering from the ddl attached produced two mappings also attached.
> When trying to generate the code with hbm2java it fails with the following exception:
> org.hibernate.MappingException: Foreign key (FK405FC7E1E8A9975D:articoli_offerti [fk_offerte_fornitori_for])) must have same number of columns as the referenced primary key (offerte_fornitori [fk_fornitori,fk_rdo])

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

[Hibernate-issues] [Hibernate-JIRA] Closed: (HBX-683) Bag associations not translated correctly with hbm2hbmxml

[Max R. A. (JIRA) <no...@at...>]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HBX-683?page=all ]
     
Max Rydahl Andersen closed HBX-683:
-----------------------------------

    Fix Version: 3.2beta6
     Resolution: Fixed

thanks. i've applied something similar (basically just what <set> already contained)

should probably try and create some reusable blocks for the assocations handling.

> Bag associations not translated correctly with hbm2hbmxml
> ---------------------------------------------------------
>
>          Key: HBX-683
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-683
>      Project: Hibernate Tools
>         Type: Bug

>     Versions: 3.1.beta5
>  Environment: hibernatetools 3.1 beta 5 with Hibernate 3.1 CR1
>     Reporter: Ali Ibrahim
>      Fix For: 3.2beta6
>  Attachments: bag.hbm.ftl
>
> Original Estimate: 1 day
>         Remaining: 1 day
>
> A bag association in a configuration is not translated correctly when generating hbm XML files via hbm2hbmxml. The current code translates the bag association without taking into account the type of element in the collection, whether it is one-to-many or many-to-many, etc. Instead it puts a placeholder of:
> <element type="string" column="dummy"/>
> A simple fix would be to replicate most of the functionality in template for set associations. I am not sure if there is extra logic that is specific for bag associations. I have attached a simple template augmentation which allowed for one-to-many relationships to be translated correctly (for my simple case at least). This fix was enough for my purposes of using linguine maps to create a diagram from the model.

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

[Hibernate-issues] [Hibernate-JIRA] Created: (ANN-361) @Column(name="xxxx") does not work when composit key is used

[Thomas R. (JIRA) <no...@at...>]

@Column(name="xxxx") does not work when composit key is used
------------------------------------------------------------

         Key: ANN-361
         URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-361
     Project: Hibernate Annotations
        Type: Bug

    Versions: 3.2.0.cr1    
    Reporter: Thomas Risberg


When using a composit key and specifying name of id column - the specified name is ignored and a column with the name of the field is generated.

This:

-------------
import java.io.Serializable;

public class ProductItemPK implements Serializable {
    private Long  productId;
    private Long  itemId;
}
-------------
import javax.persistence.*;

@Entity
@IdClass(value=ProductItemPK.class)
public class ProductItem {
    @Id
    @Column(name="product_id")
    private Long productId;

    @Id
    @Column(name="item_id")
    private Long itemId;

    private String name;
}
-------------

results in:

    create table ProductItem (
        productId number(19,0) not null,
        itemId number(19,0) not null,
        name varchar2(255 char),
        primary key (productId, itemId)
    )


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

[Hibernate-issues] [Hibernate-JIRA] Closed: (HBX-679) composite-element code completion in hbm.xml

[Max R. A. (JIRA) <no...@at...>]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HBX-679?page=all ]
     
Max Rydahl Andersen closed HBX-679:
-----------------------------------

    Fix Version: 3.2beta6
     Resolution: Fixed

I have fixed the code compelte issue.

Please report the other issue in a seperate issue. Thanks.

> composite-element code completion in hbm.xml
> --------------------------------------------
>
>          Key: HBX-679
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-679
>      Project: Hibernate Tools
>         Type: Bug

>   Components: eclipse
>     Versions: 3.1.beta5
>  Environment: Eclipse 3.1.2
>     Reporter: Eugene
>      Fix For: 3.2beta6
>  Attachments: composite_class issue.jpg, issues.zip, new db issue.jpg
>
>
> There are two issues.
> 1) I have the 
> <composite-element class="Ch06Filenames"> 
>           <property name="|"/> 
> </composite-element> 
> When i press Ctrl-Space, codecompletion listbox shows the properties of the Ch06ItemImage entity class, but i really expected to see the properties of the Ch06Filenames component Class.
> See the composite_class issue.JPG screenshot in the issues.zip
> 2) I have inserted the new table in the DataBase (HSQLDB). Then i try to view the list of tables in the codecompletion listbox:
> <idbag name="filenamesIdbag" table="|">
> but i dont see the new table at all! Then i tried to refresh  Hibernate configuration (clicked right button on it and pressed Refresh) and repeated the codecompletion operation but nevertheless the table is not present in the list!
> See the db issue.JPG screenshot in the issues.zip
> ______________________
> I have the following mapping:
> <hibernate-mapping schema="Ch06ItemImage" package="org.hibernate.ce.auction.model.ch06"> 
>   <class name="Ch06ItemImage" table="CH06ITEM" optimistic-lock="none"> 
>     <id name="id" access="field" type="long" unsaved-value="null" column="id">
>       <generator class="native"/>
>     </id>
>     <version name="version" column="VERSION" access="field" generated="always" unsaved-value="null"/>
>     <property name="created" column="CREATED" type="calendar" update="false" not-null="true" access="field"/>
>     <property name="name" type="string" column="name"/>
>     <set name="filenames" table="CH06ITEM_SET_IMAGE" inverse="true" cascade="save-update"> 
>       <key column="ITEM_ID"/>
>       <one-to-many class="Ch06ItemImageSet"/>
>     </set>
>     <idbag name="filenamesIdbag" table="CH06ITEM_BAG_IMAGE">
>     	<collection-id column="ITEM_IMAGE_ID" type="long">
>     		<generator class="native"/>
>     	</collection-id>
>     	<key column="ITEM_ID"/>
>     	<composite-element class="Ch06Filenames">
>     		<property name="name" column=""/>
>     	</composite-element>
>     </idbag>
>   </class>
> </hibernate-mapping>

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

[Hibernate-issues] [Hibernate-JIRA] Updated: (HBX-679) composite-element code completion in hbm.xml

[Max R. A. (JIRA) <no...@at...>]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HBX-679?page=all ]

Max Rydahl Andersen updated HBX-679:
------------------------------------

    Summary: composite-element code completion in hbm.xml  (was: codecompletion)

updated to reflect  issue.

> composite-element code completion in hbm.xml
> --------------------------------------------
>
>          Key: HBX-679
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-679
>      Project: Hibernate Tools
>         Type: Bug

>   Components: eclipse
>     Versions: 3.1.beta5
>  Environment: Eclipse 3.1.2
>     Reporter: Eugene
>      Fix For: 3.2beta6
>  Attachments: composite_class issue.jpg, issues.zip, new db issue.jpg
>
>
> There are two issues.
> 1) I have the 
> <composite-element class="Ch06Filenames"> 
>           <property name="|"/> 
> </composite-element> 
> When i press Ctrl-Space, codecompletion listbox shows the properties of the Ch06ItemImage entity class, but i really expected to see the properties of the Ch06Filenames component Class.
> See the composite_class issue.JPG screenshot in the issues.zip
> 2) I have inserted the new table in the DataBase (HSQLDB). Then i try to view the list of tables in the codecompletion listbox:
> <idbag name="filenamesIdbag" table="|">
> but i dont see the new table at all! Then i tried to refresh  Hibernate configuration (clicked right button on it and pressed Refresh) and repeated the codecompletion operation but nevertheless the table is not present in the list!
> See the db issue.JPG screenshot in the issues.zip
> ______________________
> I have the following mapping:
> <hibernate-mapping schema="Ch06ItemImage" package="org.hibernate.ce.auction.model.ch06"> 
>   <class name="Ch06ItemImage" table="CH06ITEM" optimistic-lock="none"> 
>     <id name="id" access="field" type="long" unsaved-value="null" column="id">
>       <generator class="native"/>
>     </id>
>     <version name="version" column="VERSION" access="field" generated="always" unsaved-value="null"/>
>     <property name="created" column="CREATED" type="calendar" update="false" not-null="true" access="field"/>
>     <property name="name" type="string" column="name"/>
>     <set name="filenames" table="CH06ITEM_SET_IMAGE" inverse="true" cascade="save-update"> 
>       <key column="ITEM_ID"/>
>       <one-to-many class="Ch06ItemImageSet"/>
>     </set>
>     <idbag name="filenamesIdbag" table="CH06ITEM_BAG_IMAGE">
>     	<collection-id column="ITEM_IMAGE_ID" type="long">
>     		<generator class="native"/>
>     	</collection-id>
>     	<key column="ITEM_ID"/>
>     	<composite-element class="Ch06Filenames">
>     		<property name="name" column=""/>
>     	</composite-element>
>     </idbag>
>   </class>
> </hibernate-mapping>

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

[Hibernate-issues] [Hibernate-JIRA] Resolved: (EJB-191) Incoherent usage of getResultList(), executeUpdate() or getSingleResult() regarding the DML/Select style should raise an IllegalStateException

[Emmanuel B. (JIRA) <no...@at...>]

     [ http://opensource.atlassian.com/projects/hibernate/browse/EJB-191?page=all ]
     
Emmanuel Bernard resolved EJB-191:
----------------------------------

    Resolution: Fixed

> Incoherent usage of getResultList(), executeUpdate() or getSingleResult() regarding the DML/Select style should raise an IllegalStateException
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
>          Key: EJB-191
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-191
>      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

[Hibernate-issues] [Hibernate-JIRA] Resolved: (HB-1559) portability of boolean properties in HQL WHERE clause

[Christian B. (JIRA) <no...@at...>]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HB-1559?page=all ]
     
Christian Bauer resolved HB-1559:
---------------------------------

    Resolution: Rejected

Blah, the only required datatype for a relational database is boolean, a truth-valued type. Just because Oracle isn't a relational database doesn't mean we should break all queries for booleans...


> portability of boolean properties in HQL WHERE clause
> -----------------------------------------------------
>
>          Key: HB-1559
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HB-1559
>      Project: Hibernate2
>         Type: Improvement

>     Versions: 2.1.8
>  Environment: postgresql vs. Oracle 
>     Reporter: Bill Schneider

>
>
> "from Foo foo where foo.booleanProperty"  
> works in PostgreSQL because it has a native boolean column type, but breaks in Oracle.
> The Hibernate docs say to use substitutions in Hibernate configuration, and "= true" literal:
> <property name="hibernate.query.substitutions">true 1, false 0</property>
> ...
> from eg.Cat cat where cat.alive = true
> Suggested improvement: the former "where foo.booleanProperty" should be considered invalid HQL and break during HQL parsing on *all* platforms, rather than literally translating to SQL and breaking selectively on DBs without native booleans.
> Always require explicit " = true".
> And incorporate literal substitution (true=1 false=0) into the Dialect.

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

[Hibernate-issues] [Hibernate-JIRA] Created: (HBX-681) Multiple Table selection from the "Tables & Columns" Tab does not function correctly.

[Todd N. (JIRA) <no...@at...>]

Multiple Table selection from the "Tables & Columns" Tab does not function correctly.
-------------------------------------------------------------------------------------

         Key: HBX-681
         URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-681
     Project: Hibernate Tools
        Type: Bug

  Components: reverse-engineer  
    Versions: 3.1.beta5    
 Environment: Windows XP JDK 1.4 Eclipse 3.1.1
    Reporter: Todd Nine


When selecting multiple tables with the Hibernate reverse engineering editor, only the last selected table is added to the XML file.  Here is a simple test case.

Schema: test_schema
Tables: TableA, TableB, TableC

1.	Click the "Add..." Button
2.	Select TableA, TableB, and TableC
3.	Click Finish

Only TableC will be added to the XML file


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

[Hibernate-issues] [Hibernate-JIRA] Created: (HBX-680) Enable Caching/Saving database meta data

[Todd N. (JIRA) <no...@at...>]

Enable Caching/Saving database meta data
----------------------------------------

         Key: HBX-680
         URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-680
     Project: Hibernate Tools
        Type: Improvement

  Components: reverse-engineer  
    Versions: 3.1.beta5    
 Environment: Windows XP JDK 1.4, Teradata 7
    Reporter: Todd Nine


I'm currently connecting to Tera Data and reverse engineering using the Hibernate IDE.  While I have specified both the schema-selection element as well as table-filter element, my performance is still very slow (> 15 minutes with every table addition).  Is it possible to give the user the option to enable caching of the database metadata?  In the case of reverse engineering existing tables, the schema will never change or change very little, and querying the database for them vs. a local cache is very inefficient.

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

[Hibernate-issues] [Hibernate-JIRA] Updated: (EJB-191) Incoherent usage of getResultList(), executeUpdate() or getSingleResult() regarding the DML/Select style should raise an IllegalStateException

[Emmanuel B. (JIRA) <no...@at...>]

     [ http://opensource.atlassian.com/projects/hibernate/browse/EJB-191?page=all ]

Emmanuel Bernard updated EJB-191:
---------------------------------

    Summary: Incoherent usage of getResultList(), executeUpdate() or getSingleResult() regarding the DML/Select style should raise an IllegalStateException  (was: Incoherent usage of getREsultList(), executeUpdate() or getSingleResult() regarding the DML/Select style should raise an IllegalStateException)

> Incoherent usage of getResultList(), executeUpdate() or getSingleResult() regarding the DML/Select style should raise an IllegalStateException
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
>          Key: EJB-191
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-191
>      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

[Hibernate-issues] [Hibernate-JIRA] Created: (EJB-191) Incoherent usage of getREsultList(), executeUpdate() or getSingleResult() regarding the DML/Select style should raise an IllegalStateException

[Emmanuel B. (JIRA) <no...@at...>]

Incoherent usage of getREsultList(), executeUpdate() or getSingleResult() regarding the DML/Select style should raise an IllegalStateException
----------------------------------------------------------------------------------------------------------------------------------------------

         Key: EJB-191
         URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-191
     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

[Hibernate-issues] [Hibernate-JIRA] Created: (HB-1559) portability of boolean properties in HQL WHERE clause

[Bill S. (JIRA) <no...@at...>]

portability of boolean properties in HQL WHERE clause
-----------------------------------------------------

         Key: HB-1559
         URL: http://opensource.atlassian.com/projects/hibernate/browse/HB-1559
     Project: Hibernate2
        Type: Improvement

    Versions: 2.1.8    
 Environment: postgresql vs. Oracle 
    Reporter: Bill Schneider


"from Foo foo where foo.booleanProperty"  

works in PostgreSQL because it has a native boolean column type, but breaks in Oracle.

The Hibernate docs say to use substitutions in Hibernate configuration, and "= true" literal:

<property name="hibernate.query.substitutions">true 1, false 0</property>
...
from eg.Cat cat where cat.alive = true

Suggested improvement: the former "where foo.booleanProperty" should be considered invalid HQL and break during HQL parsing on *all* platforms, rather than literally translating to SQL and breaking selectively on DBs without native booleans.
Always require explicit " = true".
And incorporate literal substitution (true=1 false=0) into the Dialect.



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

[Hibernate-issues] [Hibernate-JIRA] Updated: (HHH-1740) Build-time instrumentation breaks lazy="proxy"

[Frank G. (JIRA) <no...@at...>]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1740?page=all ]

Frank Grimes updated HHH-1740:
------------------------------

    Attachment: HHH-1740.diff

Attached is a diff of the files I modified under hibernate-3.2.0.cr2/test/org/hibernate/test/instrument to illustrate the problem.
Please let me know if you need anything further from me in order to reproduce the problem.
Thanks.

> Build-time instrumentation breaks lazy="proxy"
> ----------------------------------------------
>
>          Key: HHH-1740
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1740
>      Project: Hibernate3
>         Type: Bug

>   Components: core
>     Versions: 3.1.3, 3.2.0 cr1, 3.2.0.cr2
>     Reporter: Frank Grimes
>     Priority: Critical
>  Attachments: HHH-1740.diff
>
>
> I have a mapping that contains a many-to-one lazy="proxy".
> This alone works fine: I see $$EnhancerByCGLIB$$ as the type when I do a load
> Once I add a lazy property to the mapping and do build-time cglib enhancement, it breaks.
> Not only is the lazy property listed in $CGLIB_READ_WRITE_CALLBACK, but also my lazy="proxy" association. (i.e. no more proxy object)
> This works fine in hibernate-3.1.2.
> This was originally brought up here: http://forums.hibernate.org/viewtopic.php?t=958881
> Please let me know if more info or a test case is 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

[Hibernate-issues] [Hibernate-JIRA] Commented: (ANN-318) consider making validator framework truely independant of hibernate core

[Emmanuel B. (JIRA) <no...@at...>]

    [ http://opensource.atlassian.com/projects/hibernate/browse/ANN-318?page=comments#action_23256 ] 

Emmanuel Bernard commented on ANN-318:
--------------------------------------

I don't want maven. ant is just working fine and fast.
Technically speaking, Validator do not depends on the Hibernate annotations code. It depends on core and the reflection layer used in hibernate annotations.
Now the @Entity dependency comes from the reflection layer, but this probably can be easily solved.

Whether or not having one or several jars is a deployment issue that can be solved only after the previous ones are.

> consider making validator framework truely independant of hibernate core
> ------------------------------------------------------------------------
>
>          Key: ANN-318
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-318
>      Project: Hibernate Annotations
>         Type: Improvement

>   Components: validator
>     Versions: 3.1beta9
>     Reporter: Andreas Schildbach

>
>
> I'd like to use the validator framework, but without pulling hibernate in as a dependency.
> Currently, if I try to instantiate a ClassValidator, a org.hibernate.MappingException cannot be found.
> Consequently, the validator framework could also be independent of the rest of the annotations, and be distributed in its own jar.

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

[Hibernate-issues] [Hibernate-JIRA] Commented: (ANN-360) Many-To-Many relationship with attributes on relationship

[Peter M. (JIRA) <no...@at...>]

    [ http://opensource.atlassian.com/projects/hibernate/browse/ANN-360?page=comments#action_23255 ] 

Peter Muir commented on ANN-360:
--------------------------------

Also, I haved tested this with mappedBy="id.productId" as well as plain mappedBy="productId".  Neither work.

> 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

[Hibernate-issues] [Hibernate-JIRA] Updated: (ANN-360) Many-To-Many relationship with attributes on relationship

[Peter M. (JIRA) <no...@at...>]

     [ http://opensource.atlassian.com/projects/hibernate/browse/ANN-360?page=all ]

Peter Muir updated ANN-360:
---------------------------

    Attachment: manytomanywithattributes.zip

Attached is a runnable test.  It supports mapping via hibernate mapping file (for which the tests pass) and via annotations (for which the tests fail).  The correct semantics may not have been used for the annotation version (the annotations don't accept my mappedBy attribute) but the semantics (for the annotation version) have been kept as close as possible to those used for the hibernate mapping. If the hibernate mapping file can be mapped in HibernateAnnotations (3.2.0cr1) using different semantics then I apologise, this is not a bug!

> 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

[Hibernate-issues] [Hibernate-JIRA] Created: (ANN-360) Many-To-Many relationship with attributes on relationship

[Peter M. (JIRA) <no...@at...>]

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


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

[Hibernate-issues] [Hibernate-JIRA] Created: (EJB-190) Query.setParameter() should raise an IllegalArgumentException if the parameter does not exist

[Emmanuel B. (JIRA) <no...@at...>]

Query.setParameter() should raise an IllegalArgumentException if the parameter does not exist
---------------------------------------------------------------------------------------------

         Key: EJB-190
         URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-190
     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

[Hibernate-issues] [Hibernate-JIRA] Commented: (ANN-318) consider making validator framework truely independant of hibernate core

[Christian B. (JIRA) <no...@at...>]

    [ http://opensource.atlassian.com/projects/hibernate/browse/ANN-318?page=comments#action_23253 ] 

Christian Bauer commented on ANN-318:
-------------------------------------

No Maven.


> consider making validator framework truely independant of hibernate core
> ------------------------------------------------------------------------
>
>          Key: ANN-318
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-318
>      Project: Hibernate Annotations
>         Type: Improvement

>   Components: validator
>     Versions: 3.1beta9
>     Reporter: Andreas Schildbach

>
>
> I'd like to use the validator framework, but without pulling hibernate in as a dependency.
> Currently, if I try to instantiate a ClassValidator, a org.hibernate.MappingException cannot be found.
> Consequently, the validator framework could also be independent of the rest of the annotations, and be distributed in its own jar.

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

[Hibernate-issues] [Hibernate-JIRA] Commented: (ANN-318) consider making validator framework truely independant of hibernate core

[Geoffrey De S. (JIRA) <no...@at...>]

    [ http://opensource.atlassian.com/projects/hibernate/browse/ANN-318?page=comments#action_23252 ] 

Geoffrey De Smet commented on ANN-318:
--------------------------------------

Using the class validator also requires javax.persistence.Entity at runtime,
which is a more annoying issue then missing org.hibernate.MappingException
if you're building with Maven 2, because ejb3 isn't available on maven central repo (yet?).


For spring-richclient I am making an exception handler for hibernate validations,
so it doesn't need hibernate/ejb3.
(In my company project I am using hibernate to the fullest (and loving it btw)
so there the dependencies don't pose a prob.)

Do you think it's easy enough to do to seperate the validator from hibernate-annotations?
Are you already building with Maven 2?
If so, I 'd love to take a look as setting up won't take half a day, but can't promise I 'll succeed.
If not, maybe in time I can help you make a maven 2 proof of concept (like I did for spring-richclient)?


> consider making validator framework truely independant of hibernate core
> ------------------------------------------------------------------------
>
>          Key: ANN-318
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-318
>      Project: Hibernate Annotations
>         Type: Improvement

>   Components: validator
>     Versions: 3.1beta9
>     Reporter: Andreas Schildbach

>
>
> I'd like to use the validator framework, but without pulling hibernate in as a dependency.
> Currently, if I try to instantiate a ClassValidator, a org.hibernate.MappingException cannot be found.
> Consequently, the validator framework could also be independent of the rest of the annotations, and be distributed in its own jar.

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

[Hibernate-issues] [Hibernate-JIRA] Resolved: (ANN-359) @MappedSuperclass overriding fails on EJB3 DD

[Emmanuel B. (JIRA) <no...@at...>]

     [ http://opensource.atlassian.com/projects/hibernate/browse/ANN-359?page=all ]
     
Emmanuel Bernard resolved ANN-359:
----------------------------------

    Resolution: Fixed

> @MappedSuperclass overriding fails on EJB3 DD
> ---------------------------------------------
>
>          Key: ANN-359
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-359
>      Project: Hibernate Annotations
>         Type: Bug

>   Components: binder
>     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

[Hibernate-issues] [Hibernate-JIRA] Created: (ANN-359) @MappedSuperclass overriding fails on EJB3 DD

[Emmanuel B. (JIRA) <no...@at...>]

@MappedSuperclass overriding fails on EJB3 DD
---------------------------------------------

         Key: ANN-359
         URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-359
     Project: Hibernate Annotations
        Type: Bug

  Components: binder  
    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

[Hibernate-issues] [Hibernate-JIRA] Commented: (HHH-1810) Classic query parser inefficiency on WebLogic

[Emmanuel B. (JIRA) <no...@at...>]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1810?page=comments#action_23251 ] 

Emmanuel Bernard commented on HHH-1810:
---------------------------------------

I don't really understant why don't you use the new parser and put the right antlr in front of the WL classpath?
Or ask their engineers to fix their issue?

> Classic query parser inefficiency on WebLogic
> ---------------------------------------------
>
>          Key: HHH-1810
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1810
>      Project: Hibernate3
>         Type: Improvement

>   Components: query-hql
>  Environment: Hibernate 3.0.5 with HHH-525 patch
> WebLogic 8.1 SP4
> SQL Server 2000 SP3
>     Reporter: Hemanta Gupta
>     Priority: Minor
>  Attachments: QueryTranslatorImpl.java
>
>
> With around 1600 named queries in the system, SessionFactory.checkNamedQueries() takes around 5 1/2 min on WebLogic 8.1, as compared to < 1/2 min on JBoss 4.0.3. The classic query translator is being used, mainly because the new AST based translator has issues on WebLogic (http://hibernate.org/250.html#A24).
> The issue boils down to the classic query parser trying to load bad class names on a system with relatively inefficient classloading. The parser breaks down queries into tokens and then tries to resolve many of the tokens (even the obviously 'bad' ones like '=', '(', ')', 'AND', 'OR', etc) as Java classes by calling ReflectHelper.classForName() on the tokens. Because of the way the method is written, ClassLoader.loadClass() and then Class.forName() will both be called before it can be determined that a token doesn't resolve to a Java class. This overhead is really killing performance on WebLogic.
> I patched QueryTranslatorImpl.getEntityPersisterUsingImports(String) to skip tokens which can't resolve to Java classes (i.e are not Java identifiers or are HQL keywords). The file is attached. After applying this patch, the time taken by SessionFactory.checkNamedQueries() went down to around 20 sec on WebLogic. The patch isn't too beautiful or exhaustive, but it did the trick on our environment.
> Please also see the forum thread at http://forum.hibernate.org/viewtopic.php?t=943427

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