I think it can be done as part of the new redesign.
On 13 November 2014 19:44, Steve Ebersole <steve(a)hibernate.org> wrote:
Andreas is working on some redesign of batching which should allow us
report such detailed information iirc. Andreas, what are your thoughts on
doing this in the new batching code?
On Tue, Nov 11, 2014 at 6:39 AM, <Sujit.Dhaygude(a)sungard.com> wrote:
> Hi ,
> we have a requirement to point a record for which the actual batch
> flush/commit has failed.
> Is there a generic way by which hibernate can be hooked up for exception
> scenario to pull back the actual entity for which
> DB/Hibernate Error has occurred .
> Most of the times we could see the hibernate is printing the error in
> which has entity ID but which is not consistent.
> Currently we are planning to use the Pre and Post (insert/Update/Delete)
> event handlers to retain the entities in Thread local
> and display those in case of error, but these listeners will intercept
> the DB operation irrespective of success/failure .
> I am looking for a solution which will not impact the overall application
> performance and only in case of exception we need the details of entity.
> hibernate-dev mailing list
hibernate-dev mailing list