Re: [hibernate-dev] [HSearch] session.index / purge

[Emmanuel Bernard]

My concern is how we deal with non mapped subclasses. Not entirely  
sure that's the right  way to do it. But provided we don't deal today  
with this case, the exception is a good choice.


On  Jun 3, 2008, at 17:28, Sanne Grinovero wrote:

IMHO I vote for the Exception,
as phil59 said on the forum it is quite likely a "fairly common for  
newbie"
problem and it clearly is a mistake to either forget the @Indexed
or giving the wrong entity to index/purge.

A loud exception can save some hours of headache.
I couldn't think of some drawback, anyone?

2008/6/3 Emmanuel Bernard <[EMAIL PROTECTED]>:
When a non @Indexed entity is passed to session.index or  
session.purge, we
simply ignore it (even if the superclass is indexed).
Should we raise an exception instead?

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

_______________________________________________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev


_______________________________________________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev