RE: [Hibernate] Suggestion for better error reports...

[Gavin K. <Gav...@ex...>]

Do It! :)

> -----Original Message-----
> From: Max Rydahl Andersen [mailto:ma...@eo...]=20
> Sent: Friday, 6 December 2002 2:27 AM
> To: hib...@li...
> Subject: [Hibernate] Suggestion for better error reports...
>=20
>=20
> Hi!
>=20
> By "accident" I updated an object instance which id was=20
> associated with another loaded instance in the current=20
> instance and got the following error:
>=20
> "Another object was associated with this id (the object with=20
> the given id was already loaded)"
>=20
> That is all fine, but would it not be nice if the exception=20
> message contained some more information about this object ?=20
> Currently we have to enable trace to see which class and id=20
> that is related to the exception.
>=20
> With trace enabled you would get:
>  "updating eg.FooBar#42"
>=20
> This is actually a typical scenario for a couple of dozens=20
> exceptions thrown when saving, updating, etc.
>=20
> How about adding that vital information to the exception=20
> message without enabling the trace ?
>=20
> So we instead would get:
>=20
> "Another object was associated with this id (the object with=20
> the given id was already loaded) [eg.FooBar#42]"
>=20
> Any comments ?
>=20
> Otherwise I will send a patch for this change ?
>=20
> /max
>=20
>=20
>=20
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf=20
> _______________________________________________
> hibernate-devel mailing list hib...@li...
> https://lists.sourceforge.net/lists/listinfo/hibernate-devel
>=20


********** CAUTION - Disclaimer **********
This message may contain privileged and confidential
information. If you are not the intended recipient of this
message (or responsible for delivery of the message to
such person) you are hereby notified that any use,
dissemination, distribution or reproduction of this message
is prohibited. If you have received this message in error,
you should destroy it and kindly notify the sender by reply
e-mail. Please advise immediately if you or your employer
do not consent to Internet e-mail for messages of this kind.
Opinions, conclusions and other information in this
message that do not relate to the official business of
Expert Information Services Pty Ltd ("The Company")
shall be understood as neither given nor endorsed by it.

The Company advises that this e-mail and any attached
files should be scanned to detect viruses. The Company
accepts no liability for loss or damage (whether caused
by negligence or not) resulting from the use of any
attached files.
**EIS******** End of Disclaimer **********