Comments on: Hibernate Lightweight Class Wrinkles http://blog.kischuk.com/2004/08/17/hibernate-lightweight-class-wrinkles/ Just another WordPress.com weblog Tue, 29 Nov 2011 10:51:23 +0000 hourly 1 http://wordpress.com/ By: Rob Kischuk http://blog.kischuk.com/2004/08/17/hibernate-lightweight-class-wrinkles/#comment-120 Tue, 17 Aug 2004 22:21:53 +0000 http://rkischuk.wordpress.com/2004/08/17/hibernate-lightweight-class-wrinkles/#comment-120 A reasonable suggestion. My answer is mostly political rather than technical. The data in question is actually already a view. So we would be creating 2 different views for this table. Recall that I said we have very little control over the schema. This includes view creation. So we’d have to beg the database people to create another view. Further, while we only need 1 field in the summary object now, we’ll almost certainly need a few more in the near future, so we’d rather not have to go back and ask them to keep changing it.

In the near term, in an environment where we could maintain the view ourself, your suggestion is good. In the short-mid term and beyond, Hibernate will address uniqueness per object class, so this will be a non-issue.

]]> By: Prashant Rane http://blog.kischuk.com/2004/08/17/hibernate-lightweight-class-wrinkles/#comment-119 Tue, 17 Aug 2004 21:01:37 +0000 http://rkischuk.wordpress.com/2004/08/17/hibernate-lightweight-class-wrinkles/#comment-119 How about creating a view on top of the table with columns selected for the lightweight version. That way the name would be much cleaner than just change in case.

]]>