Comments on: Hibernate: Why should I Force Discriminator? http://www.gmarwaha.com/blog/2009/08/26/hibernate-why-should-i-force-discriminator/ Ganesh\ Sat, 04 Feb 2012 00:52:17 +0000 hourly 1 http://wordpress.org/?v=3.3 By: Hibernate n’aime pas la discrimination | Excilys Labs http://www.gmarwaha.com/blog/2009/08/26/hibernate-why-should-i-force-discriminator/comment-page-1/#comment-206453 Hibernate n’aime pas la discrimination | Excilys Labs Fri, 30 Dec 2011 10:41:47 +0000 http://www.gmarwaha.com/blog/?p=100#comment-206453 [...] pas naturel de devoir forcer l’utilisation du discriminant. Certains ce sont déjà posés la question mais je n’ai pas un avis tranché à ce jour. Et vous, qu’en pensez vous ? VN:R_U [...] [...] pas naturel de devoir forcer l’utilisation du discriminant. Certains ce sont déjà posés la question mais je n’ai pas un avis tranché à ce jour. Et vous, qu’en pensez vous ? VN:R_U [...]

]]> By: Gunjan http://www.gmarwaha.com/blog/2009/08/26/hibernate-why-should-i-force-discriminator/comment-page-1/#comment-161017 Gunjan Tue, 06 Sep 2011 20:20:37 +0000 http://www.gmarwaha.com/blog/?p=100#comment-161017 Awesome! Thanks - solved my problem.. Awesome! Thanks – solved my problem..

]]> By: Louis Vuitton Handbags http://www.gmarwaha.com/blog/2009/08/26/hibernate-why-should-i-force-discriminator/comment-page-1/#comment-159894 Louis Vuitton Handbags Thu, 01 Sep 2011 07:53:39 +0000 http://www.gmarwaha.com/blog/?p=100#comment-159894 Very interesting many thanks, I presume your readers would likely want more reviews along these lines continue the great effort. Very interesting many thanks, I presume your readers would likely want more reviews along these lines continue the great effort.

]]> By: www.gmarwaha.com http://www.gmarwaha.com/blog/2009/08/26/hibernate-why-should-i-force-discriminator/comment-page-1/#comment-128859 www.gmarwaha.com Fri, 22 Apr 2011 14:23:49 +0000 http://www.gmarwaha.com/blog/?p=100#comment-128859 Hibernate why should i force discriminator.. Retweeted it :) Hibernate why should i force discriminator.. Retweeted it :)

]]> By: www.gmarwaha.com http://www.gmarwaha.com/blog/2009/08/26/hibernate-why-should-i-force-discriminator/comment-page-1/#comment-124049 www.gmarwaha.com Fri, 08 Apr 2011 05:46:18 +0000 http://www.gmarwaha.com/blog/?p=100#comment-124049 Hibernate why should i force discriminator.. Nice :) Hibernate why should i force discriminator.. Nice :)

]]> By: Abhiranjan http://www.gmarwaha.com/blog/2009/08/26/hibernate-why-should-i-force-discriminator/comment-page-1/#comment-89055 Abhiranjan Wed, 17 Nov 2010 22:47:01 +0000 http://www.gmarwaha.com/blog/?p=100#comment-89055 Hi Ganesh, Nice article. I'm facing a similar problem. While trying to implement the table per class inheritance using discriminator, I am using a column as the discriminator which is essentially a foreign key referring to a code table. I believe I'm doing the mapping, and the discriminator value correct, but when I try to save, it gives me an error meaning - cannot insert null in the discriminator column (foreign key column). Is it an issue with the discriminator column being foreign key too? Hi Ganesh,
Nice article. I’m facing a similar problem.
While trying to implement the table per class inheritance using discriminator, I am using a column as the discriminator which is essentially a foreign key referring to a code table.
I believe I’m doing the mapping, and the discriminator value correct, but when I try to save, it gives me an error meaning
- cannot insert null in the discriminator column (foreign key column). Is it an issue with the discriminator column being foreign key too?

]]> By: redoc http://www.gmarwaha.com/blog/2009/08/26/hibernate-why-should-i-force-discriminator/comment-page-1/#comment-84753 redoc Mon, 18 Oct 2010 19:19:32 +0000 http://www.gmarwaha.com/blog/?p=100#comment-84753 I got a similar exception with seeded data (through batch process) in db. Instead of discriminator 'USER', the discriminator value is 'User', so it was throwing exactly the same above exception. When I changed and updated it worked perfectly fine. So watch out for that possibility as well. I got a similar exception with seeded data (through batch process) in db. Instead of discriminator ‘USER’, the discriminator value is ‘User’, so it was throwing exactly the same above exception. When I changed and updated it worked perfectly fine. So watch out for that possibility as well.

]]> By: koltuk y?kama http://www.gmarwaha.com/blog/2009/08/26/hibernate-why-should-i-force-discriminator/comment-page-1/#comment-82466 koltuk y?kama Tue, 28 Sep 2010 22:36:06 +0000 http://www.gmarwaha.com/blog/?p=100#comment-82466 I put a where clause in the mappings and it worked pretty good. I put a where clause in the mappings and it worked pretty good.

]]> By: Agus http://www.gmarwaha.com/blog/2009/08/26/hibernate-why-should-i-force-discriminator/comment-page-1/#comment-81587 Agus Sun, 19 Sep 2010 13:58:58 +0000 http://www.gmarwaha.com/blog/?p=100#comment-81587 So many thanks for this post!!!! I was struggling with the same "feature" and getting mad. I consider this behavior a bug as it forces me to use a Hibernate-specific annotation (@ForceDiscriminator is not a JPA standard) and it seems the behavior is different when using XML configuration instead of annotations. Having said that, I must admit I'm generally satisfied with Hibernate as an ORM tool. Agus So many thanks for this post!!!!

I was struggling with the same “feature” and getting mad.

I consider this behavior a bug as it forces me to use a Hibernate-specific annotation (@ForceDiscriminator is not a JPA standard) and it seems the behavior is different when using XML configuration instead of annotations.

Having said that, I must admit I’m generally satisfied with Hibernate as an ORM tool.

Agus

]]> By: Ganeshji Marwaha http://www.gmarwaha.com/blog/2009/08/26/hibernate-why-should-i-force-discriminator/comment-page-1/#comment-80925 Ganeshji Marwaha Sun, 12 Sep 2010 18:35:24 +0000 http://www.gmarwaha.com/blog/?p=100#comment-80925 @Kalyan #27: Applying a "Where Clause" Filter is another solution to the same problem, but something I would try to avoid, because that way you are directly appending strings to the SQL query generated by Hibernate. In case of a simple "where" clause, it might not be a problem, but when that becomes a bit more than standard SQL, then you don't have portability anymore. I agree, portability is most often not necessary for medium to big applications, but still, u know what i mean. Another issue I see is - the "where" clause can possibly hold plain strings on the RHS without being used as a prepared statement. @Kalyan #27: Applying a “Where Clause” Filter is another solution to the same problem, but something I would try to avoid, because that way you are directly appending strings to the SQL query generated by Hibernate. In case of a simple “where” clause, it might not be a problem, but when that becomes a bit more than standard SQL, then you don’t have portability anymore. I agree, portability is most often not necessary for medium to big applications, but still, u know what i mean. Another issue I see is – the “where” clause can possibly hold plain strings on the RHS without being used as a prepared statement.

]]>