I think thats a bad rule in general ;) Lack of specific exception types in ORM has been an issue quite a few times.
On Wed 13 Jun 2012 08:15:48 AM CDT, Sanne Grinovero wrote: > Ok, only for this specific case I created: > https://hibernate.onjira.com/browse/HSEARCH-1161 > > So we won't have a single exception any more, I guess more will come > as needed now that the "single type exception" rule is broken. > > Sanne > > On 13 June 2012 13:57, Hardy Ferentschik<ha...@hibernate.org> wrote: >> +1 and as Emmanuel is saying we should take it as it comes >> >> >> On Jun 13, 2012, at 2:49 PM, Emmanuel Bernard wrote: >> >>> +1 on a case by case basis. That can definitely help here. >>> >>> On 13 juin 2012, at 14:05, Sanne Grinovero wrote: >>> >>>> I'm wondering if we should specialize SearchException in some cases to >>>> make it easier for business logic to react correctly, like in the case >>>> of: >>>> >>>> https://bugzilla.redhat.com/show_bug.cgi?id=831569#c2 >>>> >>>> Sanne >>>> _______________________________________________ >>>> 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 -- st...@hibernate.org http://hibernate.org _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
