Re: [Hibernate] Printing entities on flush in debug mode ?

2005-05-18 Thread Max Rydahl Andersen
On Wed, 18 May 2005 23:51:09 +0200, Gavin King <[EMAIL PROTECTED]> wrote: Printer.toString() does *not* call toString() on the entity objects! Yes, found that out later - the issue was that the user had a getter that did something similar. /max -Original Message- From: [EMAIL PROTECTE

RE: [Hibernate] Printing entities on flush in debug mode ?

2005-05-18 Thread Gavin King
Printer.toString() does *not* call toString() on the entity objects! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Max Rydahl Andersen Sent: Wednesday, 18 May 2005 3:45 AM To: Hibernate devel Subject: [Hibernate] Printing entities on flush in debug mode

Re: [Hibernate] Printing entities on flush in debug mode ?

2005-05-18 Thread Max Rydahl Andersen
On Wed, 18 May 2005 10:44:47 +0200, Max Rydahl Andersen <[EMAIL PROTECTED]> wrote: Ah - users can just disable debug level for org.hibernate.pretty.Printer then it will not occur. sorry for the bandwith ;) /max Hi guys, Is the line new Printer( session.getFactory() ).toString( persistenceCo

[Hibernate] Printing entities on flush in debug mode ?

2005-05-18 Thread Max Rydahl Andersen
Hi guys, Is the line new Printer( session.getFactory() ).toString( persistenceContext.getEntitiesByKey().values().iterator(), session.getEntityMode() ); in AbstractFlushingEventListener really necessary ? It can/will cause ConcurrentModificationException if you e.g. have debug on and this "i