Comments on: Partitioning in Hibernate http://blog.xebia.com/2006/07/31/partitioning-in-hibernate/ Mon, 26 Jul 2010 20:40:47 +0200 http://wordpress.org/?v=2.8.4 hourly 1 By: Lovely Job http://blog.xebia.com/2006/07/31/partitioning-in-hibernate/comment-page-1/#comment-25968 Lovely Job Wed, 28 Nov 2007 11:40:21 +0000 http://blog.xebia.com/2006/07/31/partitioning-in-hibernate/#comment-25968 Hi Your article is good. Here I have a id could not be instatantiated problem. The database dialect which I use is MySQL. When I search google we could solve it by reverse enginnering procedure by creating hibernate.reveng.xml file and adding some jars.. Can you help me on this... I am a newbie in hibernate . I am a java coder. Hi

Your article is good. Here I have a id could not be instatantiated problem. The database dialect which I use is MySQL.

When I search google we could solve it by reverse enginnering procedure by creating hibernate.reveng.xml file and adding some jars..

Can you help me on this…

I am a newbie in hibernate . I am a java coder.

]]> By: Ganesh http://blog.xebia.com/2006/07/31/partitioning-in-hibernate/comment-page-1/#comment-5404 Ganesh Fri, 16 Mar 2007 10:29:46 +0000 http://blog.xebia.com/2006/07/31/partitioning-in-hibernate/#comment-5404 I have a HBM mapping whcih includes parent and child.Now while doing a search from the parent table using this HBM it always selects form the child table i need to restrict the child and select columns only form parent.Using inverse="true" is not solving the probelem I have a HBM mapping whcih includes parent and child.Now while doing a search from the parent table using this HBM it always selects form the child table i need to restrict the child and select columns only form parent.Using inverse=”true” is not solving the probelem

]]> By: jmarcum http://blog.xebia.com/2006/07/31/partitioning-in-hibernate/comment-page-1/#comment-317 jmarcum Tue, 29 Aug 2006 19:11:46 +0000 http://blog.xebia.com/2006/07/31/partitioning-in-hibernate/#comment-317 Thanks for the article, it solves the partitioning problem I was having. The bug you describe actually is a "feature" in hibernate. Some databases (not Oracle) allow you to compare sets in a where clause, like "where (id, name) = (1, 'jmarcum')". Because your id is composite, the only way for hibernate to limit by parent in that query is to use both the id and partitionValue. In order to make this query work in Oracle your hql would need to be something like "from Child c where c.parent.id.id = :id and c.parent.id.partitionValue = :partitionValue". See section 14.8 "Where Clause" in the hibernate manual about half a page down. http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#queryhql-where Thanks for the article, it solves the partitioning problem I was having. The bug you describe actually is a “feature” in hibernate. Some databases (not Oracle) allow you to compare sets in a where clause, like “where (id, name) = (1, ‘jmarcum’)”. Because your id is composite, the only way for hibernate to limit by parent in that query is to use both the id and partitionValue. In order to make this query work in Oracle your hql would need to be something like “from Child c where c.parent.id.id = :id and c.parent.id.partitionValue = :partitionValue”. See section 14.8 “Where Clause” in the hibernate manual about half a page down. http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#queryhql-where

]]>