Im approx +0 on this one :) Gavin, why was this done in the first place ? Seem to remember somewhere that the docs states:
Free from my mind: "Hibernate does not hide what's happening. e.g. SQLExceptions is propagated all the way up to the user." . /max ----- Original Message ----- From: "One Ovthafew" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, January 03, 2003 5:29 PM Subject: Re: [Hibernate] Suggestion: Encapsulate SQLException in HibernateException > I am happy to introduce a JDBCException that wraps any SQLExceptions > that occur. However, I don't have a strong view either way. So lets just > vote on this.... > > Gavin > > >> I was thinking about wrapping SQLException in HibernateException, so > that we don't need to worry about catch HibernateException and > SQLException. Since now the work is focused on some changes for > Hibernate 2, this could be the right time to do this kind of change. > This would simplify the error handling in the applications. << > > --------------------------------------------------------------------- > Never lose a fax again, receive faxes to your personal email account! > Visit http://www.mbox.com.au/fax > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > hibernate-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/hibernate-devel > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
